Decision table technique condition list

Task 1

Q1. Decision table test for doctor appointment form filling fields.

		TC1	TC2	TC3	TC4	TC5	TC6	TC7
Condition 1	Enter First name	Valid	Invalid/blank	Valid	Valid	Valid	Valid	Invalid
Condition 2	Enter Last name	Valid	Valid	Invalid/blank	Valid	Valid	Valid	Invalid
Condition 3	Enter Email	Valid	Valid	Valid	Invalid	Valid	Valid	Invalid
Condition 4	Enter Phone no.	Valid	Valid	Valid	Valid	Invalid	Valid	Invalid
Condition 5	choose Appointment date	Valid	Valid	Valid	Valid	Valid	Invalid	Invalid

Action 1	Appointment scheduled	Executed
Action 2	Display message "All filds are required"		Executed	Executed				Executed
Action 3	Message show "Please enter valid email"				Excuted
Action 4	Message show "Please enter valid phone number"					Executed
Action 5	Message show "Please choose another date"						Executed

QA 2 - Test steps for Mobile application testing

Scenario 1

Basic user

1-Open application

2-Login to the application

3-start sending/receiving messages

4-Basic user should not able to give feature access to himself

4- Logout to the application

Expected Result: Basic user have only limited feature access he should not able to access authorized features.

1-Premium user -start application

2-Login to the application

3-Use paid services in application

4-Logout to the application

Expected Result: Premium user have all feature access in application except admin(setting) rights.

1-Admin -start application

2-Login to the application

3-Create new user

4-Mange settings for particular user

5-Logout to the application

Expected Result: Admin user have all action rights including setting.

Scenario 2

Basic user

1-Login to application

2-test Create account

Expected result: Basic user should not be able to create account.

premium user

1-Login to application

2-test Create account

Expected result: Premium user should not have access to create account.

Admin user

1-Login to application

2-Admin user - Create account

3-password complexity check

4-Receive confirmation email upon account creation

5-Delete account access test 6-Logout from application

Expected result: Admin user should be able to perform any action in application

Scenario 3

Basic user

1-Login to application

2-Navigate from app pages or features without any crashes

3-Verify that error message is displaying on usage of unauthorized feature which is access is not be given

4-Logout from app.

Expected result: Error message should be display when unauthorized feature usage.

premium user

1-Login to application

2-Navigate from app pages or features without any crashes

3-Verify that all the feature access is given to the premium user

4-Logout from app.

Expected result: Error message should be display when unauthorized feature usage.

Admin user

1-Login to application

2-Navigate from app pages or features without any crashes

3-Verify that all the feature access and setting actions.

4-Logout from app.

Expected result: Admin user should be able to navigate and edit, modify user etc.

Test case design technique

Subscribe to my newsletter

Rameshwar Mitkari

Rameshwar Mitkari