SOFTWARE TESTING
TEST PLAN AND TEST CASE DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
We cannot automate the user inputs.
|
|
|
It may be difficult to determine if the test has passed or failed.
|
|
|
It may be difficult to repeat the test.
|
|
|
We cannot run the test.
|
Detailed explanation-1: -It may be difficult to determine if the test has passed or failed. Expected Result is the component of the test cases, it is the predefined value of the output. It is used to identify the test cases are pass or fail on the basis of comparing actual results with the expected result. Therefore, Option C is correct.
Detailed explanation-2: -Expected Result is an ideal result that the tester should get after the test case is performed. It’s usually documented together with the test case. It’s usually compared with actual result, and if the actual result differs from the expected one, the difference is documented and called a bug.
Detailed explanation-3: -Test cases define how to test a system, software or an application. A test case is a singular set of actions or instructions for a tester to perform that validates a specific aspect of a product or application functionality. If the test fails, the result might be a software defect that the organization can triage.
Detailed explanation-4: -Do Ad-hoc testing. Do usability testing. Do sanity testing. Do a risk based analysis to prioritize.