Test Case Design Techniques

R venkateshR venkatesh
2 min read

Q1: Decision Table for Appointment Scheduling

A decision table helps us check different input scenarios and their expected outcomes.

ConditionCase 1Case 2Case 3Case 4Case 5
Are all fields filled?NoYesYesYesYes
Is the email valid?-NoYesYesYes
Is the phone number valid?--NoYesYes
Is the appointment slot available?---NoYes
Expected OutputAll fields are requiredPlease enter a valid emailPlease enter a valid phone numberPlease choose another date/timeAppointment successfully scheduled

Q2: Testing a Mobile App

Below are the different testing scenarios and steps to follow:

Scenario 1: Checking User Access

Steps:

  1. Log in as a Basic User and try to access premium features.

  2. Verify that access is restricted.

  3. Log in as a Premium User and check if all features are available.

  4. Log in as an Admin and confirm that admin settings are accessible.

  5. Try performing an unauthorized action and check if an error message appears.

Expected Result:

  • Basic users should only access limited features.

  • Premium users should have full access.

  • Admins should be able to manage settings and users.


Scenario 2: Creating/signup and Deleting Accounts

Steps:

  1. Open the app and go to the Sign-up page.

  2. Enter a username, email, and a weak password (e.g., "12345").

  3. Check that the app rejects weak passwords.

  4. Enter a strong password (e.g., "Guvi@12345") and sign up.

  5. Verify that a confirmation email is sent.

  6. Log in and delete the account.

  7. Try logging in again to ensure the account was deleted successfully.

Expected Result:

  • Weak passwords should be rejected.

  • Users should receive a confirmation email after registration.

  • Deleted accounts should not be accessible.


Scenario 3: Navigation & Error Handling

Steps:

  1. Log in as different users (Basic, Premium, Admin).

  2. Navigate through different sections of the app.

  3. Try performing actions that are not allowed for your role.

  4. Test how the app behaves under different network conditions (Wi-Fi, mobile data, offline mode).

  5. Rapidly switch between screens to check for crashes or slowdowns.

Expected Result:

  • Unauthorized actions should show appropriate error messages.

  • The app should work smoothly without crashes.

  • Navigation should be fast and responsive under all conditions.


0
Subscribe to my newsletter

Read articles from R venkatesh directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

R venkatesh
R venkatesh