Software test cases in my eyes

in a general software company, design and write Test Use Cases has been a very important basic for testers work .

However, many software testing practitioners or other departments will always feel that test cases are not necessary to write. We can think of a software development process:

Product personnel to determine user needs, product personnel, developers, testers, UE personnel, such as review, developer design and development (test design and write use cases, developer submissions, testers follow the requirements and use cases to perform test-on-line release.

I think that test cases are required to be written. However, many software testing practitioners consider the writing of test cases to be useless, because there is often a great deal of discrepancy between test cases when performing tests. In fact, the cause of this phenomenon, I think the main is in the needs of the review phase is not done, development, product,UE to the needs of the understanding of different, resulting in the subsequent demand changes, and even may be the demand itself is not very perfect, As a result, the requirements are constantly being changed during the development process.

But for these reasons, we can all control them in an acceptable range, and of course, this is mainly the content of the requirements review stage. Personally, even if the requirements review process is perfect, there will be little demand change. When writing test cases, in order to make use cases more coverage, or often find some missing requirements, timely communication, improve efficiency. Thus, the process of writing use cases is more helpful for testers to understand requirements.

Test cases are like scripts or baton, so writing test cases is necessary. But in a lot of internet companies, the basic agile development, product iterations are very frequent, so that testers to execute the test time is very short, not to mention the time to write test cases, at this time, we can simplify the test case testing point.

However, when it comes to complex processes, it can be described in more detail with test cases as much as possible.

It's also possible to get developers to talk about how development is implemented before writing test cases and preparing to perform tests. This makes it easy to grasp the points of attention in the test andRecordembodied in the use case. For exampleadevelopment used to do it in some wayafeature, there is aBug, and nowbdevelopment is implemented in the same way, it is very likely that the previousBugThis is going to happen again.

Use case review is also very necessary, especially some very experienced software testing old drivers, can quickly help to point out the missing points of use cases, to help testers open ideas, as much as possible to cover the user scene, it is worth noting that the use case review encountered uncertain, should be immediately recorded, after the end of timely find relevant personnel to confirm, Avoid guessing.

Software test cases in my eyes