My opinion on the design of software test case

Test friends I believe that everyone is more worried about a problem that is how to design a high-efficiency, efficient use and can also be detailed to record the various functional points of the test cases. Now each product from the design is very complex, iterative update fast, the verification time is short, especially during the activity, the update is faster and more frequent, these do not say, plus PM and development is a lot of time is also a mess, How to use test cases in all the confusion to guide the daily testing work is a big problem. Use cases as a map to guide our testing work, without this document we have no way to refine the work, nor to develop new staff.    

I found a way out of the work. This is a data distribution-oriented design test case. We all know that databases are the most central part of all software. Before coding the database to design the first, the rest is to process the data and services, the importance of visible data. So we can think of each function point and each field as a single piece of data that is recorded on our test cases.

So how do we design it? There are three types of methods:

1, with a high repetition rate of the function point , take out as a separate plate, and then use the module for the plate for use case writing. What is the function point of high repetition rate ? This is where the function points will appear in many places, for example: comments. What is the use of modules for the plate? Take the same app client example, for example: With the group tour and the Free line product Details page These two modules have comments, then we can set the comment as a separate plate, will follow the group tour and free line as its subordinate module. Of course, the comments themselves will have other modules appear, such as: Comment Details page, comment list page and so on.

2, can control the overall function point, take out as a separate plate. What is the function point that can control the global? When this feature point is selected, the data displayed elsewhere will change. For example, in the same app on the group tour/free line of these two function points, when one of the function points, the data on the page will correspond with the group tour/free line, showing the group tour/free line products.

3. Set the main page of the part you want to test independently as a plate. This doesn't have to be explained too much.

What are the benefits of this design? That is, no matter how the page changes, as long as the function point of this data processing is good, you can use the fastest speed to insert the update point accurately into the test case.

Sometimes we can't blame pm or the development of the work, because they also have their own part of the busy, we have to do is to reflect on our own work, regardless of external factors or conditions, as long as our workflow and document design scientific and reasonable we are not afraid of any impact.

Http://www.ly.com

My opinion on the design of software test case