followers view all
following view all
|youradisnothere is not in any groups|
|Software development, .NET|
Why do developers need test cases?
Testing plan, test design, test coverage, bug report are all notions that make up a list of expressions used by testing specialists for describing this or that task. But such notion as test case is more common and is known to more people, even to those who understand little in programming.
Test case is a document which describes the order of actions, conditions and parameters required for analyzing the quality of the system under test and its components. Test case includes four main components: name, pre-condition, steps and expected result. Under pre-condition (or preliminary steps) we understand description of the conditions which are not related to the testing process itself, but should be carried out anyway. For example, in order to check the quality of some element you need to register in a system. Steps are the sequence of actions which leads to the expected result. This is the structure of test case.
What is an ideal test scenario?
First of all, test cases should be clearly presented, which increases the chances that some possible defect will be detected. Secondly, while they should be really detailed, there should be no excessive information. Thirdly, test cases should be independent from each other so that they don’t interconnect. Otherwise, if you change, add new information or delete one test case, there may be problems with the connected test cases.
Who writes a test case?
Test cases creation is a pretty difficult process which requires certain knowledge and deep understanding of the project needs. As a rule, the main people responsible for test cases are testing and QA specialists, but this is not always so. But, with appropriate knowledge to set priorities and see the future architecture of the project, test cases can be written by different specialists. But when we speak about testing specialists, they should test software in the first turn, even with the help of specialized software.
As a conclusion, I’d like to add that mobile app testing is also structured clear process. In order for specialists not to be distracted all test cases should follow one pattern.
|share||like 5||report||88 views|