[Tool] Should the test case contain all the details?

Should the test case contain all the details?

If the test case is too detailed, it cannot meet the requirements of system changes. If the writing is too rough, the operability is not strong and it is too casual. So how to design test cases?

I suggest: Focus on "test ideas" instead of "Operation steps ";

 

As a test case designer, we need to think about how to understand the basic stream and alternative stream? How can I thoroughly analyze and find all the paths to be overwritten and the features to be checked? Then, we use easy-to-understand natural language to clearly describe how we will perform the test.

 

There are two ways to write traditional case documents:

1) Fill in the operation step list: after analyzing the basic stream and alternative stream, he can clearly describe your test ideas;

2) Fill in the test matrix: Suitable for storing test data, especially those that require a correct value manually;

Note: The debate over the two methods on the Internet leads everyone to the two extremes: either A or B.

Correct a misunderstanding: the debate on working methods is essentially not the same as the debate on tools. If different methods have their own advantages, we can use different methods to combine the advantages.

The test case document has been divided into two parts:

1) It describes the procedure that the test case Executor should follow;

2) part of the test data to be used in the operation;

The reason for this is that in our actual work, especially during functional testing, we often use the same operation process and different test data. With the above method, you do not need to re-Describe the operation process repeated in multiple use cases, but you can focus more on the design and preparation of test data.

 

Use Case Management Cost considerations: test requirements do not correspond to test cases in a one-to-one manner, because a test requirement may not explicitly correspond to a valid function (in fact, the test requirement itself is not necessarily the same as the software requirement and use case. ). What we pay attention to in our test cases should be an effective function. But don't worry. In this case, it will not increase the cost of managing test requirements and test cases, some of the testing tools available on the market are dedicated to maintaining the relationship between software requirements and test cases, they also provide powerful view functions, allowing you to easily view the coverage of test cases for test requirements.

[Tool] Should the test case contain all the details?