Test case Design techniques
NIKHIL KUMARWhat is the difference between Waterfall and Agile methodologies in SDLC
Agile follows an incremental approach, while waterfall follows a sequential design process.
The agile methodology is known for flexibility while waterfall adopts a structured software development.
In agile methodology we can change any time requirement but Requirement change and not allowed in waterfall method.
The agile methodology less time consumption but waterfall method its taking more time.
Agile allow to deliver the project part by part but waterfall only deliver at the end of the entire project
In Agile methodology we can test in development phase but Waterfall once the process start it does not reverse until it is finished.
You are testing a form the 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
| Feature to be tested | Test case | |
| First name | 1.Check if the first name is mandatory. | |
| 2.Check if the first name field uses only alphabets. | ||
| 3.If we enter number and special character field shows an error message.4. If filed is left blank field shows an error message. | ||
| Last Name | 1.Check if the last name is mandatory. | |
| 2.Check if the last name field uses only alphabets. | ||
| 3.If we enter number and special character field shows an error message.4. If filed is left blank field shows an error message. |
| Email address | 1. Check for valid email address should be accepted . | |
| 2. Check for invalid email address should not be accepted . | ||
| 3. If Email filed is left blank field shows an error message | ||
| 4. Enter email matches the format | ||
| 5. Check email space length. | ||
| 6. See if the duplicate email if we provide | ||
| Phone Number | 1. Check for valid/invalid phone number. | |
| 2. Check the spaces and for its maximum length. | ||
| 3. See if the phone number is duplicate/already existing | ||
| 4. Check valid number only allowed | ||
| 5. Check field allows numbers only. | ||
| 6. See if the phone number field shows an error message for alphabets and special characters entry. |
| appointment date/time | 1. Check for valid/invalid date and time | |
| 2. Check If date and time filed is left blank field shows an error message | ||
| 3. Past date should not be accept | ||
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 users roles: basic user, premium user, and admin user. You have been the following three test scenario to execute
Scenario 1: User Roles and Access Permissions
Steps to Test:
1. Login Testing:
Create user accounts for each role (Basic, Premium, and Admin).
Verify that Basic users can access limited features. They can login own login credential. They can user access few features based upon role. Example-In mobile app they can login own login with credential and they can see some module open and closed they cant edit or other record they can add own records and they can edit own record other record they don't have access and other they cant perform other details.
Verify that Premium users can access all features. premium user can access all login credential they can see other person record also, they have permission all features.
Verify that Admin users have access to advanced settings and all functions.-Admin user can do any thing they have access all advanced features and setting permission
2. Role Authorization Testing:
Log in with each role and attempt to access features that are not allowed for that role.
Verify that unauthorized actions are blocked, and the app displays appropriate error messages.
3. Boundary Testing:
Verify that access control same credential with different platform, they should not access different parts of the app
Expected Results:
Basic users should only access limited features.
Premium users should access all features.
Admin users should have access to advanced settings and all functions.
Unauthorized actions should be blocked with appropriate error messages.
Scenario 2: Account Creation and Password Management
Steps to Test:
1. Account Creation Testing:
Create new accounts with various usernames and passwords, including both valid and invalid formats.
Verify that users can successfully create accounts with valid details.
password should be standard format.
Verify that users receive a confirmation email while cresting account.
2. Account Deletion Testing:
Login with different credential and try to delete accounts.
If try to dealt account with valid user and credential, verification should be asked
Expected Results:
Users should be able to create accounts with valid information and correct password .
Users should receive confirmation emails while creating account.
Account deletion should work for authorized users.
Scenario 3: App Navigation and Performance
Steps to Test:
1. Navigation Testing:
Navigate through the app using different user roles.
Test all major functions and features of the app based on role based on role permission
Verify that users can move one module to other module without getting anu issue.
2. Performance Testing:
Test the app’s with connectivity and without connectivity .Verify load time and response time while doing testing. Verify that the app doesn’t crash during testing.
Expected Results:
Users should be able to navigate through the app without crashes or performance issues.
App load times and response time should be work
Error and Validation message should be displayed while login with wrong user abd password.
Subscribe to my newsletter
Read articles from NIKHIL KUMAR directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by