Creation of Test Cases

Question 1

Why should scenarios be specific?

Answer 1

• The author has to be strict at getting at which angle the functionality will be tested
• You cannot assume the users will have any prior knowledge of the app

Question 2

What is a test case?

Answer 2

A complete step by step set of instructions on how to conduct a test around a specific element of the application

Question 3

What do test cases include?

Answer 3

• Test case title
• Test case ID
• Pre-requisite
• Test steps
• Actual result
• Pass/fail
• Comments
• Expected result

Question 4

What is the difference between Expected result and Actual result?

Answer 4

Expected result is the result we wanted based on client expectations. Actual result is the exact app behavior based on our actions

Question 5

What should be done if Actual result is different from Expected result?

Answer 5

Repeat test steps 3 times, and if it persists, log a bug

Question 6

Describe RTM

Answer 6

• Requirement Traceability Matrix
• Document that maps between test cases and requirements
• Validates the test coverage for the project
• Identifies any gaps between RD and test cases
• Each parallel team will have its own RTM

Question 7

Describe TCR

Answer 7

• Test Closure Report
• Summarizes what every QA has done towards the SDLC process
• Includes status of all test cases, status of all the bugs, lift of any outstanding bugs, and list of any untested requirements

Question 8

What is the only document that needs to be QA approved and why?

Answer 8

TCR, because we are handing it to the client directly