For this post I have decided to write about how to design tests. Testers design tests whether they are using Static or dynamic testing techniques. To design a test you need 3 things according to ISTQB test conditions, test cases and test procedures (Scripts). Each of these things are specified in their own documents created from information given by the developers and the tester's own interpretations of the provided info. Testing is also designed and executed with varying degrees of formality depending on the customer's or testing team's preferences.
The designing process usually begins with the testers looking through something that they can derive test info from which is also known as a test basis. A test basis can be many different things from an experienced user's knowledge, a business process, system requirements, specifications or the code. Through test basis we find test conditions or the things we could test, because test conditions could come from anything they are usually vague.
Unlike test conditions, test cases are more specific. Test cases will mean entering specific inputs into a system, and will also require some understanding of how the system works. This mean knowing what the system should do and therefore the correct behavior of the system which is also referred to as a Test Oracle. After choosing an input the tester needs to figure out what the expected result is and put it into the test case. Expected results are what appears on the screen in response to the input values as well of changes to data or states and consequences.
The next and last step of the process is to put the test cases into a way that makes sense and the steps needed to run the test. This is a test procedure or test script. These procedures are then put into an execution schedule to determine which procedures are run first and whom runs them.
There are also many different categories of design techniques that I will get into later.
No comments:
Post a Comment