August 26, 2010

Identify the Expected Results

SONGYUAN, CHINA - MAY 8:  Farmers plant rice s...
Image by Getty Images via Daylife
The tester should know what he is testing for and expected output for the given input. Until and unless the aim of his testing is not known, there is no use of the testing done. Because the tester may not succeed in distinguishing the real error and normal workflow. First he needs to analyze what is the expected output for the scenario he is testing.
Example: Consider software used to provide the user with an interface to search for the employee name in the organization given some of the inputs like the first name or last name or his id etc. For such a scenario, the tester should identify the expected output for any combination of input values. If the input provided does not result in any data and shows a message ”Error not data found”. The tester should not misinterpret this as an error, because this might be as per requirement when no data is found. Instead for a given input, the message shown is “ 404- File not found”, the tester should identify it as an error not a requirement. Thus he should be able to distinguish between an error and normal workflow.

About the Author


Author & Editor

Has laoreet percipitur ad. Vide interesset in mei, no his legimus verterem. Et nostrum imperdiet appellantur usu, mnesarchum referrentur id vim.

Post a Comment

Iwebslog Blog © 2015 - Designed by