Test Case design techniques

Q1: Decision Table for form field validations

Testing scenarioFirst NameLast NameEmailPhone numberAppointment date/timeExpected Output
All fields are blank-----All fields are required
Incorrect emailValue-1Value-1incorrect emailxxxxxxxxxxxxx/xx/xxxx 12:30Please enter a valid email
Invalid phone numberValue-2Value-2correct emailinvalid numberxx/xx/xxxx 12:30Please enter a valid phone number
Appointment date not availableValue-3Value-3correct emailxxxxxxxxxxxxx/xx/xxxx 12:30Please choose another date/time
All fields are correct, schedule appointmentValue 4Value 4Value 4Value 4Value 4Appointment scheduled successfully

Q2: Mobile App testing

Test Scenario 1: User Roles and Account Management

Steps:

  1. User Creation:

    • Create a basic user account.

    • Create a premium user account.

    • Create an admin user account.

  2. User Access Control:

    • Log in with the basic user account and attempt to access premium and admin features.

    • Log in with the premium user account and attempt to access admin features.

    • Log in with the admin user account and access all features.

  3. Account Deletion:

    • Log in with each user role and delete the respective account.
  4. Password Complexity:

    • Attempt to create an account with a weak password and ensure it's rejected.

    • Create an account with a strong password and ensure it's accepted.

  5. Confirmation Email:

    • Check for the confirmation email upon successful account creation.

Expected Results:

  • Basic users should have limited access.

  • Premium users should have access to all features.

  • Admin users should have access to advanced settings and all actions.

  • Accounts should be deletable by respective users.

  • Weak passwords should be rejected, and strong passwords accepted.

  • Confirmation emails should be received.

Test Scenario 2: App Navigation and Performance

Steps:

  1. Navigate Through App:

    • Log in as each user role and navigate through the app.

    • Check various features, menus, and options.

  2. Performance Testing:

    • Perform actions within the app and monitor for any performance issues.

    • Check for smooth transitions between screens.

  3. Error Messages:

    • Attempt to perform unauthorized actions and check for appropriate error messages.

Expected Results:

  • Seamless navigation for all user roles.

  • No crashes or performance issues.

  • Appropriate error messages displayed for unauthorized actions.

Test Scenario 3: Error Handling

Steps:

  1. Unauthorized Action:

    • Log in with a basic user and attempt to access admin features.

    • Log in with a premium user and attempt an admin action.

    • Attempt actions with incorrect permissions.

  2. Invalid Input:

    • Submit forms with invalid data and check for appropriate error messages.

    • Ensure error messages are clear and user-friendly.

Expected Results:

  • App should display clear error messages for unauthorized actions.

  • Proper handling of invalid input with appropriate error messages.