Test Case Design Techniques

Decision Table :

The App has three Different user roles like Basic user, Premium user and Admin user and these are the following test scenarios to execute :-

Scenario 1: User Roles and Access

Test Objective: To verify that different user like (Basic, Premium, Admin) have appropriate access to features.

Test Steps:

• Log in as a basic user.
• Verify that basic user have only limited features are accessible.
• Log out and repeat the continue same process to Premium and Admin user.
• Verify that Premium users have all access and Admin users can process Advanced settings.

Expected Results:

1. Basic user should only be able to access limited features. Premium user should have access to all features.
2. Admin user should have all features and advanced settings.

Scenario 2: Account Creation and Deletion

Test Objective: To verify that users can create and delete their accounts successfully.

Test Steps:

• Get into the Account creation Page.
• Enter all valid information, including a password that meets required standards.
• And Submit the form and verify successful account creation.
• Log in to the Newly created account.
• And Delete the Account and verify successful deletion.

Expected Results:

1. Account creation should succeed with Valid Information and with a strong password.
2. After Create, the User should get the Email Confirmation message.
3. After Account create User should be able to Login the app.
4. Account deletion should delete the User Account.

Scenario 3: App Navigation and Error Handling

Test Objective: To Verify that users can navigate the app without crashes, performance issues, and receive expected error messages.

Test Steps:

• Log in with different user roles.
• Navigate through various app sections and features.
• Attempt actions that users are not authorized to perform.
• Check for performance issues and crashes during navigation and action attempts.

Expected Results:

1. App navigation should be without crashes.
2. Performance issues should be low or avoid.
3. Users attempting unauthorized actions should receive error messages.