Now there is a demand for a complete description as follows:
There is now a client PC command-line tool, which can receive three command line parameters, where the first two numbers, the last one is the operator, the operator only supports the function subtraction, multiplication and division, the tool is put before operators use two numbers to do the operation, and then outputs the operation result.
Two formats were used to write test cases shown below (with the Example section):
The first style is completely original usage following the brain image, belonging to hierarchical progressive, behind the front tier hierarchy are preconditions need for all the levels of each branch all combined together, it is complete with an embodiment .
The second style, elements are classified according to the way different types of elements of each layer are the same, down to the last one is a complete use case, the previous level just to make clear classification, in order to put back a large Example lump end use will be more structured display.
Relatively speaking, I recommend the second style.
We need, on the one hand it is reasonable resolution, such as a first layer in the second format, we divided into three according to the input, output and input order, subsequent continue pressing parameters, the second parameter and the third argument this way finer division, so clarity is still pretty clear.
Examples of such a format, when making use case assessment, can easily and needs one correspondence, can quickly identify needs coverage.
On the other hand, this format use cases, for example with the actors is relatively friendly, executives can focus on the last node use cases, according to the specified policy enforcement on the line, if it is the first form, you need to look at every time from scratch to the end, it is prone to error.
See: https: //www.testwo.com/blog/8340