Test case techniques

·

6 min read

you are testing a form that allows users to schedule appoinments with a doctor . the form has the following fields : first name , last name , email , phone number and appoinment date / time . some more inputs are below ;

  1. If any field is blank we should display " All fields are required " .

  2. if the email is invalid , we should display " please enter a valid email" . 3)if the phone number is invalid, we should display " please enter a valid phone number ".

  3. if the appointment date/time is not available , it should display " please choose another date/time".

  4. if all fields are correct and the appoinment is available , we should schedule the appoinment successfully.

for these requirements write down the correct list of conditions in form of decision table.

Answers are below :

To create a decision table for testing the appointment scheduling form based on the provided requirements, we can define different conditions and their corresponding actions. Here's a decision table for the given scenario:

Conditions:

ConditionDescription
First Name is blankFirst Name field is left empty
Last Name is blankLast Name field is left empty
Email is invalidEmail format is invalid
Phone Number is invalidPhone Number format is invalid
Appointment Date/Time not availableThe selected date/time is not available
All fields are correctAll fields are filled correctly and appointment is available

Actions:

User ActionDescription
Display "All fields are required"Displayed when any of the fields is blank
Display "Please enter a valid email"Displayed when the email format is invalid
Display "Please enter a valid phone number"Displayed when the phone number format is invalid
Display "Please choose another date/time"Displayed when the appointment date/time is not available
Schedule appointment successfullyAppointment is scheduled successfully when all fields are correct and the appointment is available

Decision Table:

ConditionAction
First Name is blankDisplay "All fields are required"
Last Name is blankDisplay "All fields are required"
Email is invalidDisplay "Please enter a valid email"
Phone Number is invalidDisplay "Please enter a valid phone number"
Appointment Date/Time not availableDisplay "Please choose another date/time"
All fields are correctSchedule appointment successfully

This decision table helps you systematically test the appointment scheduling form under various conditions to ensure it functions correctly according to the specified requirements.

2) You are a software tester and you are assigned to test a new mobile app that has just been developed . this app has three diffrent user roles : basic user, premium user , admin user . you have been given the following 3 test scenarios to execute ,Basic users can only access limited features of the app, while remium users can access all features . admin users have access to advances settungs and can perform all actions*user should be able to create and deleter their accounts successfully. passwords must meet the required complexity standards and users should receive a confirmation email upon succesful account creation.*users should be able to navigate through the app seamlessly without any crashes or perfomance issues. the app should also display appropriate error messages when a user attempts an action they are not authorized to perform. fr each of the test scenarios , describe the steps you would take to test them and the expected results

Test Scenario 1: User Roles and Access

Test Case 1.1: Basic User Access

  • Preconditions:

    • User is logged in as a basic user.
  • Test Steps:

    1. Attempt to access each feature in the app.
  • Expected Results:

    • For basic user:

      • Should have access to limited features only.

      • Should not have access to advanced settings or admin actions.

  • Actual Results:

    • Verify that the basic user can access only the limited features.

    • Verify that advanced settings and admin actions are not accessible for the basic user.

Test Case 1.2: Premium User Access

  • Preconditions:

    • User is logged in as a premium user.
  • Test Steps:

    1. Attempt to access each feature in the app.
  • Expected Results:

    • For premium user:

      • Should have access to all features in the app.

      • Should not have access to admin actions or advanced settings.

  • Actual Results:

    • Verify that the premium user can access all features.

    • Verify that admin actions and advanced settings are not accessible for the premium user.

Test Case 1.3: Admin User Access

  • Preconditions:

    • User is logged in as an admin user.
  • Test Steps:

    1. Attempt to access each feature in the app.
  • Expected Results:

    • For admin user:

      • Should have access to all features, including advanced settings and admin actions.
  • Actual Results:

    • Verify that the admin user can access all features, including advanced settings and admin actions.

Test Scenario 2: Account Creation and Deletion

Test Case 2.1: Successful Account Creation

  • Preconditions:

    • User is on the registration page.
  • Test Steps:

    1. Enter valid registration information.

    2. Click on the registration button.

  • Expected Results:

    • User account is created successfully.

    • User receives a confirmation email.

  • Actual Results:

    • Verify that the user account is created.

    • Verify that a confirmation email is sent to the user.

Test Case 2.2: Account Deletion

  • Preconditions:

    • User is logged into their account.
  • Test Steps:

    1. Navigate to the account deletion section.

    2. Follow the steps to delete the account.

  • Expected Results:

    • User account is deleted successfully.
  • Actual Results:

    • Verify that the user account is deleted.

Test Scenario 3: App Navigation and Error Handling

Test Case 3.1: Seamless App Navigation

  • Preconditions:

    • User is logged in.
  • Test Steps:

    1. Navigate through different sections and features of the app.
  • Expected Results:

    • User should be able to navigate seamlessly without any crashes or performance issues.
  • Actual Results:

    • Verify that the app navigation is smooth without crashes or performance issues.

Test Case 3.2: Error Handling

  • Preconditions:

    • User attempts an action they are not authorized to perform.
  • Test Steps:

    1. Try to perform an unauthorized action.
  • Expected Results:

    • App should display an appropriate error message indicating the action is not authorized.
  • Actual Results:

    • Verify that the app displays the expected error message when an unauthorized action is attempted.

These test cases cover the three test scenarios and provide a structured approach to testing the mobile app with the different user roles and account management functionalities.