Announcement

Collapse
No announcement yet.

Joip

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Joip

    Test ID1.
    Choose_Your_Plan_Selection
    Steps:
    1. Go to the main page - https://mobile.joip.com/signup/Plans.aspx
    2. On Main page, select “Product” – “Application”
    3. On Main page, select “Subscription” – “Monthly”

    Expected result: main page should display the call rates for above plan
    Actual result: main page displays the call rates for above plan

    Pass

    Test ID2.
    Choose_Your_Plan_Selection
    Steps:
    1. Go to the main page - https://mobile.joip.com/signup/Plans.aspx
    2. On Main page, select “Product” – “Application”
    3. On Main page, select “Subscription” – “3 months”

    Expected result: main page should display the call rates for above plan
    Actual result: main page displays the call rates for above plan

    Pass
    Test ID3.
    Choose_Your_Plan_Selection
    Steps:
    1. Go to the main page - https://mobile.joip.com/signup/Plans.aspx
    2. On Main page, select “Product” – “Application”
    3. On Main page, select “Subscription” – “6 months”

    Expected result: main page should display the call rates for above plan
    Actual result: main page displays the call rates for above plan

    Pass
    Test ID4.
    Choose_Your_Plan_Selection
    Steps:
    1. Go to the main page - https://mobile.joip.com/signup/Plans.aspx
    2. On Main page, select “Product” – “Application”
    3. On Main page, select “Subscription” – “Annual”

    Expected result: main page should display the call rates for above plan
    Actual result: main page displays the call rates for above plan

    Pass
    Test ID5.
    Choose_Your_Plan_Selection
    Steps:
    1. Go to the main page - https://mobile.joip.com/signup/Plans.aspx
    2. On Main page, select “Product” – “Home phone”
    3. On Main page, select “Subscription” – “Monthly”

    Expected result: main page should display the call rates for above plan
    Actual result: main page displays the call rates for above plan

    Pass
    Test ID6.
    Choose_Your_Plan_Selection
    Steps:
    1. Go to the main page - https://mobile.joip.com/signup/Plans.aspx
    2. On Main page, select “Product” – “Home phone”
    3. On Main page, select “Subscription” – “3 months”

    Expected result: main page should display the call rates for above plan
    Actual result: main page displays the call rates for above plan

    Pass
    Test ID7.
    Choose_Your_Plan_Selection
    Steps:
    1. Go to the main page - https://mobile.joip.com/signup/Plans.aspx
    2. On Main page, select “Product” – “Home phone”
    3. On Main page, select “Subscription” – “6 months”

    Expected result: main page should display the call rates for above plan
    Actual result: main page displays the call rates for above plan

    Pass
    Test ID8.
    Choose_Your_Plan_Selection
    Steps:
    1. Go to the main page - https://mobile.joip.com/signup/Plans.aspx
    2. On Main page, select “Product” – “Home phone”
    3. On Main page, select “Subscription” – “Annual”

    Expected result: main page should display the call rates for above plan
    Actual result: main page displays the call rates for above plan

    Pass

  • #2
    First we look at what is a main objective of a presented web page. It appears to be choosing of a phone plan. We have 2 products, 4 subscriptions and 4 plans.Base on that we can calculate:
    2*4*4=32 test suites

    Then we can break it down into test cases:

    -Application + Monthly + PAY AS YOU GO plan = 6 test cases

    Test case 1:
    Description: Sign up for a plan
    Instructions:
    1.Open tested URL : https://mobile.joip.com/signup/Plans.aspx
    2.Check Application
    3.Check Monthly
    4.Push "Sign up" button from the "Pay as you go" plan
    Expected result: user is redirected to the "Sign up" window

    Test case 2:
    Description: "Pay as you go" is linked to the "Sign up" page
    Instructions:
    1.Open tested URL : https://mobile.joip.com/signup/Plans.aspx
    2.Check Application
    3.Check Monthly
    4.Push "Pay as you go" hyperlink
    Expected result: user is redirected to the "Sign up" window

    Test case 3:
    Description: see the rates
    Instructions:
    1.Open tested URL : https://mobile.joip.com/signup/Plans.aspx
    2.Check Application
    3.Check Monthly
    4.Push on "Low cost per minutes rates"
    Expected result: user is redirected to the "Rates" window

    Test case 4:
    Description: Info icon works
    Instructions:
    1.Open tested URL : https://mobile.joip.com/signup/Plans.aspx
    2.Check Application
    3.Check Monthly
    4.Push on Info icon
    Expected result: user is redirected to the informational window

    Test case 5:
    Description: Addition info about the plan is presented
    Instructions:
    1.Open tested URL : https://mobile.joip.com/signup/Plans.aspx
    2.Check Application
    3.Check Monthly
    Expected result: at the bottom of "Pay as you go" plan additional info "Free joip..." is ncluded

    Test case 6:
    Description: plan rate is shown
    Instructions:
    1.Open tested URL : https://mobile.joip.com/signup/Plans.aspx
    2.Check Application
    3.Check Monthly
    Expected result: under the "Pay as you go" hyperlink "$2.99/mo." text is shown


    -Application + Monthly + NORTH AMERICA plan = 6 test cases
    -Application + Monthly + WORLD UNLIMITED plan = 7 test cases
    -Application + Monthly + LATIN AMERICA plan = 6 test cases

    and so on... We'll have approximately 200 test cases(32 test suits * 6-7 test cases)
    Last edited by Alex Sanya; 09-24-2017, 05:39 PM. Reason: added more test cases

    Comment


    • #3
      ASSUMPTION: I assume that the purpose of this exercise is to demonstrate one's ability to make a test plan ("How would you test that?"), rather than to make specific test cases. The following work has been performed under this assumption:

      #1: GENERAL. I suppose that we can conduct three types of test of this web application:
      #1.1: Functionality testing to make sure that all:
      #1.1.1.: all required features are present as per the product documentation and technical specification; and
      #1.1.2.: all features operate as expected under the foregoing product documentation;
      #1.2: Security testing to make sure that the web-application is safe for the end user to use; and
      #1.3: GUI and Usability to make sure that the application is user-friendly, compliant with the GUI guidelines, usability and accessibility requirement, and does not contain typos and other errors.

      #2. FUNCTIONALITY TESTING. I believe that we can divide the functionality testing into the following areas:
      #2.1: Requirements check-list (a test suit to make sure that all requirements are met);
      #2.2.: SIGN UP SECTION TESTING
      #2.2.1.: Verify that the system will not allow the user to sign up before all required fields are filled out;
      #2.2.2.: Verify that the system will not accept invalid e-mail address:
      #2.2.2.1.: Verify that the system will not accept an e-mail address without the "@" sign;
      #2.2.2.2.: Verify that the system will not accept an e-mail address without the ".[smth]" ending;
      #2.2.2.3.: Verify that the system will require a confirmation of an e-mail by sending a confirmation letter to the e-mail address, entered by the user;
      #2.2.3.: Verify that the system will not allow the user to use invalid characters in first name:
      #2.2.3.1.: special characters;
      #2.2.3.2.: digits;
      #2.2.4.: Verify that the system will not allow the user to use invalid characters in last name:
      #2.2.4.1.: special characters;
      #2.2.4.2.: digits;
      #2.2.5.: verify that the system will not allow the user to sign up with an invalid password:
      #2.2.5.1.: which contains 5 digits;
      #2.2.5.2.: which contains 3 digits;
      #2.2.5.3.: which contains 3 digits and a letter;
      #2.2.5.4.: which contains 3 digits and a special character;
      #2.2.6.: verify that the system will allow the user to sign up using a valid password (4 digits);
      #2.2.7.: verify that the system will not allow the user to enter a wrong telephone number:
      #2.2.7.1.: containing a string of digits and a special character;
      #2.2.7.2.: containing a string of digits and a letter;
      #2.2.7.3.: not compliant with NANP (for a US or Canadian telephone number);
      #2.2.8. verify that the system will allow the user to sign up, using the valid telephone number.
      #2.3. LOG IN SECTION
      #2.3.1.: Verify that the system will allow the user to login, using valid login and password;
      #2.3.2.: Verify that the system will not allow the user to login, using incorrect login (one character missing). An error message "No such user" shall be displayed;
      #2.3.3.: Verify that the system will not allow the user to login, using correct login and incorrect password (one character replaced). An error message "Incorrect password" shall be displayed.
      #2.3.4.: Verify that the system will log out the user when pressing the "backspace" key or the "return" button;
      #2.4. PRODUCT SELECTION
      #2.4.1.: Verify that the user can select both products offered in combination with any of the subscription options and plans offered;
      #2.4.2.: Verify that the user can select the four subscriptions offered in combination with any product and plan offered;
      #2.4.3.: Verify that the user can select the offered plans in combination with any subscription option and product offered
      (TOTAL of 32 test cases in this test suite);
      #2.5. PAYMENT
      #2.5.1.: Verify that the user can make a payment as per his selection using a valid credit card;
      #2.5.2.: verify that the user cannot make the payment using an invalid card:
      #2.5.2.1.: with invalid card number;
      #2.5.2.2.: with invalid cardholder's name;
      #2.5.2.3.: with invalid validity term ("valid through");
      #2.5.2.4.: with invalid security number.
      #2.6. Verify that all links:
      #2.6.1.: are active; and
      #2.6.2.: redirect the user correctly;
      #2.7. Verify that all buttons:
      #2.7.1.: are active when they are expected to be active; and
      #2.7.2.: behave as expected.

      #3. SECURITY
      #3.1.: Verify that the system will mask the password and input by bullets ("***");
      #3.2.: Verify that the user's personal data is securely stored and there is not risk of its leakage;
      #3.3.: Verify that the user's credit card data is securely stored and there is no risk of its leakage;
      #3.5.: Verify that the payment is done through a secure theft-proof tunnel.

      #4: GUI and Usability
      #4.1.: Verify that the web-application does not have typos, grammatical mistakes;
      #4.2.: Verify that the web-application is compliant with the GUI and usability guidelines and check-lists;
      #4.3.: Verify that the web-application is compliant with the prevailing accessibility requirements and standards.
      Last edited by MaxAlexC; 09-25-2017, 01:58 PM.

      Comment


      • #4
        JOIP Mobile App Testing

        Test cases:
        TOTAL 64 TEST CASES FOR "SIGN UP" + 8 TEST CASES FOR "LOW COST PER MINUTES RATE

        ID: 1
        Description:
        Sign up for Application/Monthly "Pay as you go" plan

        Instruction:
        1. Go to home page https://mobile.joip.com/signup/plans.aspx
        2. Check "Application" in Select Product section
        3. Check "Monthly" in Select Subscription section
        4. Push "Sign up" button in "Pay as you go" dialog box

        Expected Result:
        User is redirected to the "Sign up" page

        ID: 2
        Description:
        Sign up for Application/Monthly "North America" plan

        Instruction:
        1. Go to home page https://mobile.joip.com/signup/plans.aspx
        2. Check "Application" in Select Product section
        3. Check "Monthly" in Select Subscription section
        4. Push "Sign up" button in "North America" dialog box

        Expected Result:
        User is redirected to the "Sign up" page

        ID: 3
        Description:
        Sign up for Application/Monthly "World Unlimited"

        Instruction:
        1. Go to home page https://mobile.joip.com/signup/plans.aspx
        2. Check "Application" in Select Product section
        3. Check "Monthly" in Select Subscription section
        4. Push "Sign up" button in "World Unlimited" dialog box

        Expected Result:
        User is redirected to the "Sign up" page

        ID: 4
        Description:
        Sign up for Application/Monthly "Latin America"

        Instruction:
        1. Go to home page https://mobile.joip.com/signup/plans.aspx
        2. Check "Application" in Select Product section
        3. Check "Monthly" in Select Subscription section
        4. Push "Sign up" button in "Latin America" dialog box

        Expected Result:
        User is redirected to the "Sign up" page

        ID: 5
        Description:
        Sign up for Application/Monthly through the link "Pay as you go"

        Instruction:
        1. Go to home page https://mobile.joip.com/signup/plans.aspx
        2. Check "Application" in Select Product section
        3. Check "Monthly" in Select Subscription section
        4. Click the link "Pay as you go" in the dialog box

        Expected Result:
        User is redirected to the "Sign up" page

        ID: 6
        Description:
        Sign up for Application/Monthly through the link "North America"

        Instruction:
        1. Go to home page https://mobile.joip.com/signup/plans.aspx
        2. Check "Application" in Select Product section
        3. Check "Monthly" in Select Subscription section
        4. Click the link "North America" in the dialog box

        Expected Result:
        User is redirected to the "Sign up" page

        ID: 7
        Description:
        Sign up for Application/Monthly through the link "World Unlimited"

        Instruction:
        1. Go to home page https://mobile.joip.com/signup/plans.aspx
        2. Check "Application" in Select Product section
        3. Check "Monthly" in Select Subscription section
        4. Click the link "World Unlimited" in the dialog box

        Expected Result:
        User is redirected to the "Sign up" page

        D: 8
        Description:
        Sign up for Application/Monthly through the link "Latin America"

        Instruction:
        1. Go to home page https://mobile.joip.com/signup/plans.aspx
        2. Check "Application" in Select Product section
        3. Check "Monthly" in Select Subscription section
        4. Click the link "Latin America" in the dialog box

        Expected Result:
        User is redirected to the "Sign up" page

        ID: 9
        Description:
        "Low cost per minutes rates" is linked to check rates page

        Instruction:
        1. Go to home page https://mobile.joip.com/signup/plans.aspx
        2. Check "Application" in Select Product section
        3. Check "Monthly" in Select Subscription section
        4. Click the link "Low cost per minutes rates" in the "Pay as you go" dialog box

        Expected Result:
        User is redirected to the "Check Rates" page.
        Four dialog boxes with rates are displayed

        Actual Result:
        User is redirected to the "Check Rates" page.
        Four dialog boxes are displayed without any rates.
        The links "Pay as you go", "North America", "World Unlimited", "Latin America" are not activ

        APPLICATION/3 MONTHS - 9 TEST CASES
        APPLICATION/6 MONTHS - 9 TEST CASES
        APPLICATION/ANNUAL - 9 TEST CASES
        HOME PHONE/MONTHLY - 9 TEST CASES
        HOME PHONE/3 MONTHS - 9 TEST CASES
        HOME PHONE/6 MONTHS - 9 TEST CASES
        HOME PHONE/ANNUAL - 9 TEST CASES
        Last edited by Nataly; 09-25-2017, 02:34 PM.

        Comment


        • #5
          1. Verify that User can select a “Product”
          2. Verify that User can select a “Subscription”
          3. Verify that Plans are displayed as expected with the selected combination of “Product” and “Subscription” (total 8 combinations)
          4. Verify that User can signup for each plan using valid credentials and successfully buy the selected plan
          5. Verify that description of a plan is displayed as expected when User pushes “i” symbol next to the plan name
          6. Verify that when User pushes “Check Rates” on the bottom right of the page, information on rates is displayed as expected
          7. Verify that when User pushes “Compare Deals” on the bottom right of the page, information on deal comparison is displayed as expected
          8. Check that User can navigate the website using site menus in the header
          9. Check that correct information is displayed when User selects a section in the informational footer

          Comment


          • #6
            (answering the question: "How would you test this?") https://mobile.joip.com/signup/Default.aspx

            The first thing I would do is I would ask if there are any requirements to test. If I would be answered that there are no requirements, I would assume them.
            If the requirements are:

            1. The JOIP application allows to purchase phone service packages
            2. The application provides with video, voice and IM services
            3. Only one account needed to use the services
            4. The cost of the services is the same no matter where you are located
            5. The JOIP application provides high quality connection

            I think no matter what we test, we do positive testing first (we make sure that if we act as a user the application will produce expected results. We do not start negative testing until positive is done).

            Comment


            • #7
              How would you test this? - https://mobile.joip.com/signup/Default.aspx

              1. I ask for requirements firs (if I have it - following them)
              2. First I start with positive testing, after work on negative testing
              3. I start from fictionality testing ( it is more important to have a happy customer and successful business)

              If no requirement:

              I analyzing the web-page. Joip is company provides communication services - SERVICES

              test data: two valid logins and passwords
              valid information for credit card


              Requirements:
              #1. User can choose a plan
              #2. User can use shopping cart (button BAY)
              #3. User can fill all required field on registration with "no-problem"
              - Make sure all required field behave like required field (availability asterisk, error message)
              - Make sure data retained in database
              - Testing values in lists boxes
              - User can use default button
              #4. User receive email with correct retaining data after registration
              #5. User can log in with valid login and password
              #6. User's password is safe
              - password is not saved on required field after log out
              - password can't be "cut" or "copy"
              - password do not safe on requared field after push button "show the previous page" and come back by pushing button "show the next page". (I use iOS - here is the buttons)
              #7. User can pay for services
              - User can fill all required field on registration with "no-problen"
              - Make sure all required field behave like required field (availability asterisk, error message)
              - Make sure data retained in database
              - Testing values in lists boxes
              - User can use default button
              #7. User receive confirmation letter of payment with correct data
              #8. User can connect with costumer support
              #9. Make sure chackboxes have a reasonable initial values
              #10. Make sure capacity and valid on text boxes is correct

              after fictionality testing (positive and negative) I move to GUI testing (it is a LOT of bugs!!!)

              Comment


              • #8
                First, we assume the requirements if we don't have them:
                1. The application allows user to choose the plan in 3 steps with 2 criteria :
                a. Selection of product
                b. Selection of subscription
                c. Selection of the plan according to previous selection
                2. After choosing the plan and pushing the button “Sign Up” the user is redirected to the “Sign Up page”
                a. After filling out the required fields the user is redirected to the next “Sign up” step
                • First name text field accepts letters only
                • Last name text field accepts letters only
                • Email address is supposed to have “@” symbol
                • Registered phone number list box has all countries in alphabetical order
                • The phone number field accepts 10 digits only
                • The password consists of 4 digits only
                • The password is shown in bullets
                • Entered data in “Confirm password” field matches the info entered in “Choose Password” field
                • The password cannot be copied and pasted
                • The password cannot be cut and pasted
                • One of 3 security questions is chosen
                • The answer for Security question is provided
                • All required fields are filled out
                • The user is able to see what fields are required
                b. Button “Next” becomes enabled as soon as user enters valid data and redirects the user to the next page
                3. After entering valid information the user is able to confirm entered info and make a payment (unable to see what are the next steps due to the websites hanging)
                a. First name contains letters only
                b. Last name contains letters only
                c. The billing address entered correctly:
                • Building Number accepts digits only
                • Street Address accepts digits, letters and some special characters (- , .) and no more than 30 characters
                • Zip code accepts only 5 digits
                d. The card number accepts only 16 digits
                e. The expiration date is in format mm/yy
                • No more than 12 months
                • The year entered cannot be less than current year
                • Data entered cannot be expired
                And so on and so on.
                Second, we do test cases based on the requirements.
                Third, we verify all elements of web-application are compliant with GUI guidelines (the application is user-friendly, there are no typos and other errors, there is a consistency among all elements and etc.)

                At first we focus on positive testing and then only move to negative testing

                Comment


                • #9
                  JOIP VOIP SERVICE We have two kinds of products: "APPLICATION" and "HOME PHONE".

                  Four different plans: "Pay as you go", "North America", "World unlimited", "Latin America"

                  Also we have four different periods of subscription: "MONTHLY", "3 Months - 15% discount", "6 Months - 20% discount", "Annual - 25% discount"

                  I would test this application in that way:

                  Two products, four periodes of subscription and four plans give us 32 combinations of plans with the different prices and descriptions, or in other words we have 32 TEST SUITES here.

                  First of all, I'd create some kind of test matrix in wich I recalculate all discounts and savings to make sure they were calculated correctly for each test suite.

                  1.JPG

                  Let's look on TEST SUITE №28 and how many test cases we can include in it:

                  TS28 (Application_6Months_LatinAmerika)

                  Preconditions: radio buttons "Application" and "6 Months" are selected.

                  2.JPG

                  Test cases for "Latin America":

                  1. Verify that new page (with correct information) opens when user pushes the button "i" top right corner next to plan name and provided information about this plan is correct.
                  2. Verify that name of the selected plan is correct - // Latin America //
                  3. Verify that hyperlink "Latin America" leads to the registration form and transmit correct value into this form - // Latin America - $167.50/ 6mo. //3.JPG
                  4. Verify that displayed cost of plan is correct - // $167.50 //
                  5. Verify that displayed amount of months is correct - // 6 mo. //
                  6. Verify that displayed amount of savings is correct - // Save $42.44 //
                  7. Verify that displayed discription of plan is correct - // 1000 minutes
                  per month to Latin America.//
                  8. Verify that information in pop-up window, when you hover on "Latin america" string provides correct information about countries. - //4.jpg
                  9. Verify that additional information about the plan is displayed correctly - // Mexico mobile included! //
                  10. Verify that button "Sign UP" leads to the registration form and transmit correct value to into it - // Latin America - $167.50/ 6mo. // 3.JPG

                  So 32 test suites with at least 10 test cases give us 320 test cases...to write


                  Then I'd start to test functinalityt of registration form and so on.
                  Last edited by Eugeny; 09-26-2017, 01:51 PM.

                  Comment


                  • #10
                    How would you test that? https://mobile.joip.com/signup/Plans.aspx

                    As there are no specifications provided for this web application, most of the specifications will need to be assumed. Assuming that this application needs to functions a sign up application, test cases will be written and then executed in an effort to ensure all the require fields work.

                    Depending on the amount of time designated for testing this web application, one may need to divide work into equivalence classes. This would mean each field would only be tested by creating the minimal number of test cases, most likely 2 for each boundary (once these become known), and a central one.

                    There would need to be test cases written for the different selections available in the main body of the page, as well as the header and the footer. All text fields should be tested to endure specified boundaries are observed. Ensuring radio check boxes, drop down menus, and click boxes function correctly will be imperative during the testing process.

                    Comment


                    • #11
                      As I don't have any requirments
                      I would start with creating a check list and then started exploratory testing, and perform functionality (positive and negative) testing for "SIGNUP" page. I would perform GUI testing as well, to check functionality of all radio-buttons, buttons, Folder Tabs, links. I would also test compatibility with other browsers.

                      Comment


                      • #12
                        To test the given web page, I will start with assuming the requirements, if none are provided.

                        Requirements:
                        1. User is able to select Product.
                        2. User is able to select Subscription.
                        2. User is able to successfully sign up for one of the 4 plans.
                        3. User is able to check the "Low cost per minutes rates" .
                        4. User is able to check "60 countries" list.
                        5. User is able to click on "1000 minutes per month to Latin America" link.


                        After, we proceed with testcases for each requirement.

                        Test Case ID: 1
                        1. Go to https://mobile.joip.com/signup/Plans.aspx
                        2. In "Step 1: Select Product" select Application.

                        Expected Results: User can see the prices and details for Application Products.
                        Actual Results: Pass/Fail

                        Test Case ID: 2
                        1. Go to https://mobile.joip.com/signup/Plans.aspx
                        2. In "Step 1: Select Product" select Home Phone.

                        Expected Results: User can see the prices and details for Home Phone Products.
                        Actual Results: Pass/Fail

                        Test Case ID: 3
                        1. Go to https://mobile.joip.com/signup/Plans.aspx
                        2. In "Step 2: Select Subscription" select Monthly.

                        Expected Results: User can see the prices and details for Monthly Subscription.
                        Actual Results: Pass/Fail

                        We continue to make test cases for each combination of Application/3-Months, Application/ 6-Months, Application/Annual, Home Phone/Monthly, Home Phone/3-Months, Home Phone/6-Months, Home Phone/Annual.

                        Test Case ID: 10
                        1. Go to https://mobile.joip.com/signup/Plans.aspx
                        2. Select desired product combination.
                        3. Push "Sign Up" button.

                        Expected Results: User is taken to Sign Up page to create an account.
                        Actual Results: Pass/Fail.

                        After finishing with the Functionality testing, I will proceed with GUI.

                        Comment


                        • #13
                          1. First I would running Exploratory Testing to familiarize with the application
                          - Usability testing
                          - GUI
                          2. Than start functional testing from Home page
                          - test sign in (happy path)
                          - sign in negative testing
                          3. Run functional testing of " Prices"
                          -"Signup" menu
                          - create the account (happy pass)
                          -test "email adress" field
                          - test "password" field
                          -test "confirm password field"
                          -test "registered phone number field"

                          Comment


                          • #14
                            https://mobile.joip.com/signup/Plans.aspx?

                            I would ask for requirements - if no requirements are specified :


                            1.Exploratory and GUI testing :
                            •Test if the JOIP signup/plans web page is functional - can actually be reached on the internet; hard refresh the browser.
                            •Get familiar with the web page and read "About Us" section .
                            - Verify correct spelling .
                            •Main web page components are present .
                            - Header and footer are in place.
                            - Website logo is displayed.
                            - Sign up for different VoIP plans section is displayed.
                            - "*" signs are explained in the footer area.
                            •Default values are in place when needed .
                            - Radio buttons ("Application" and "Monthly") have a default value .
                            •No aesthetic issues .
                            •Consistent controls:
                            - "Blue question mark" (located in "select product section" ) symbols provides user with detailed information when hover over them .
                            - Cursor changes into hand pointer when hover over action buttons .

                            2.Positive functional testing :
                            •Buttons and links on the page should be functional - redirecting a user to another page or otherwise;in our case the right top red "Buy" button is unresponsive - not redirecting users to a new page or display any error message when selected .

                            3. Test under different test environments :
                            •Verify that up to date and older operating systems and browsers (Windows, Mac, Linux / IE/Edge, Safari, Chrome and Firefox) are able to display the page properly .
                            •Test web page on mobile devices - touch screen friendly (?) .

                            4. Test the security of the page :
                            - User is connected to a secure connection : "https://" and the security symbol is displayed by internet browser .
                            Last edited by chips90; 09-26-2017, 05:38 PM. Reason: Adding stuff

                            Comment


                            • #15
                              I would test 32 plans for their functionality (around 6 functions for each plan: information, region, price, links, sign-up). So I would come up with 192 or so test cases

                              Comment

                              Working...
                              X