Test case details

Writing test cases is an important part of software testing activities carried out before the actual test execution begins. Therefore, we must be clear-eyed understanding of the requirements in the preparation of test cases. The degree of success depends primarily on the implementation phase of testing the quality of the preparation of test cases, but also on the degree of understanding of the requirements. In theory, it should be placed to avoid unnecessary or unwanted details in the test case, but put in the necessary and important details but will play an important role.

It has the advantage that the desired details of the test:

Good test cases can reduce the dependence on testers

Imagine such a situation, people writing test cases are not available in full or in part, test execution phase of the test execution phase. In this case, if the test case is independent of the nature and contains all the relevant details the successful completion of the test required to perform the test, then it is easy for testers to participate in the implementation of other activities. In addition, when the other team members directly involved in the implementation stage, can help you write a good test case, so as to reduce dependence on primary testers.

Good to see much easier to write test cases

In an ideal test environment, all test cases must be reviewed by the stakeholders, in order to prevent the omission of the final test appearance. If you write a test case in simple language without skipping any steps, they will be easy to understand and provide feedback.

Detailed test cases contribute to the development of reproducible defects

If a test case failed and caused the defect, then write good test cases and defect ID link could also help developers reproduce the defect and find out where the problem lies. This will shorten the time to solve the BUG, thus speeding up the overall test speed.

Good test cases can be used as training resources

If there is not enough training materials to train new team members and make them faster entry, then with the appropriate details of the test case will help new testers to easily navigate the application and obtain the information required. This again reduces the burden on senior testers can train new members receive training on a minor theme of the application being tested.

Good test case should include details of:

Accurate test name - the name of the test case should not be too long, it will be briefly defined and the use of test cases
Test ID - should assign a unique ID to the test test case
Prerequisite - if the test case before starting any prerequisites are met, it should be mentioned
Test Procedure - shall prepare a clear test procedures, because these steps are similar to command testers need to follow. For what needs to be done, it should be clearly followed.
Test Data - If there are any specific test data should be provided as input to the application. It may be used for boundary value analysis, it may also be used to test whether certain calculations done by the application correctly.
Expected Results - After completion of the test procedure and test data provide a desired, or expected value should be clear how the application should respond to the application.
Actual results - The net effect is observed when performing the test step behavior. This should be recorded and compared with the expected results.
The end result - based on actual results are consistent with the expected results, test procedures should be marked as Pass / Fail
Defect ID - If a test step fails, the defect should be made for defects and flaws noted in the test step ID. This is helpful for tracking defects.
Note - If any subsequent test items used in a particular step, you can enter comments
Demand ID - where applicable, the test should step / case placed demand ID, which also helps to ensure that test cases covering all needs.

More conducive to automation

If some or most parts of the application need to be automated, with details of the test will be very useful. Automated teams often shared between different organizations in the test team. Therefore, the manual system tester different, automated testers no in-depth understanding of the application being tested. Therefore, they need to be the guide, or must pass enough detail to them, so that they can successfully create automation scripts. Writing good test cases help guide automated testers, and save a lot of time and communication costs.

Test cases can be used as evidence

Test cases not only in written test execution phase as a guide, but also the purpose of long-term services. One of the most important purpose is to serve as evidence of testing testers. If the defects encountered in a production environment or higher test environment, it also helps to retroactive defects. Testers can also find out the real cause of product defects.

Although the details have to write test cases appropriate number has many long-term benefits, but in some cases, too much detailed information is placed in a test case might adversely affect, for example:

Time-critical situation

In the actual test, not all cases are ideal. Thus, there may be a case in which the tester is not enough time to record the test particle size. Probably because of time constraints. In this case, once you understand the requirements, testers must be implemented immediately. Because only in the implementation process will be found defective.

Temporary or one-time test

If you must make a one-time or temporary test test with minimal budget, the main emphasis should be placed on the test execution.

It is important not to lose unnecessary attention to detail

Test cases have unnecessary detail tend to lose focus on the main objectives of the test case. No matter how detailed the information entered in the test cases, test cases should be the main goal is always associated.

to sum up

Write test cases behavior should be a balance of the activities, and should bear in mind the important point, for example, can write test cases the time required to reuse test cases, stakeholder expectations and other available documents and projects.

Solemnly declare : The article first appeared in public No. "FunTester", prohibit third parties (except Tencent cloud) reproduce, publish.