Test case design techniques

Q1.You are testing a form that allows users to schedule appointments with a doctor. The form has the following fields: first name, last name, email, phone number, and appointment date/time. Some more inputs:

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"

4.If the appointment date/time is not available, it should display "Please choose another date/time"

5.If all fields are correct and the appointment is available, we should schedule the appointment successfully.

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

Image attached

Q2.Suppose you are a software tester and you are assigned to test a new mobile app that has just been developed. The app has three different user roles: basic user, premium user, and admin user. You have been given the following three test scenarios to execute:

1.Basic users can only access limited features of the app, while premium users can access all features. Admin users have access to advanced settings and can perform all actions.

2.Users should be able to create and delete their accounts successfully. Passwords must meet the required complexity standards and users should receive a confirmation email upon successful account creation.

3.Users should be able to navigate through the app seamlessly without any crashes or performance issues. The app should also display appropriate error messages when a user attempts to perform an action they are not authorized to perform.

For each of the test scenarios, describe the steps you would take to test them and the expected results.

Steps:

Test Scenario 1: Account sign up

1.Account Creation:

- Basic User:Attempt to create an account with a password that meets complexity standards.

- Premium User: Attempt to create an account with a password that meets complexity standards.

- Admin User:Attempt to create an account with a password that meets complexity standards.

- Verify that each user type can successfully create an account.

- Verify that incorrect password complexity requirements are properly rejected with appropriate error messages.

2.Account log in:

- Basic User: Log in and attempt to delete their own account.

- Premium User: Log in and attempt to delete their own account.

- Admin User: Log in and attempt to delete their own account.

- Verify that each user type can successfully delete their own account.

- Verify that users cannot delete accounts they are not authorized to delete.

3.Confirmation Email:

- After successful account creation for each user type, check the registered email accounts.

- Verify that a confirmation email has been sent promptly and contains the necessary details.

Expected Results:

- Users of all types should be able to create and delete their accounts without issues.

- Password complexity requirements should be enforced correctly.

- Confirmation emails should be sent promptly upon successful account creation.

Test Scenario 2: App Navigation and Performance

1.Basic User Navigation:

- Log in as a basic user and navigate through all accessible features.

- Test various user interactions.

- Ensure navigation is smooth without delays or unexpected crashes.

2.Premium User Navigation:

- Log in as a premium user and verify access to all app features.

- Test premium-specific features thoroughly.

- Check for smooth navigation and performance under load.

3.Admin User Navigation:

- Log in as an admin user and access advanced settings and actions.

- Test administrative features

- Verify that admin-specific features work as intended and are accessible only to admins.

4.Authorization Error Handling:

- Attempt to perform actions that each user type is not authorized to perform.

- Verify that appropriate error messages are displayed.

Expected Results:

- All user types should be able to navigate through their respective sections without issues.

- App should handle various interactions smoothly without crashes.