Need to write software test cases?

Write required?Software Test CasesSoftware Testing

1,What is a test case?What is the purpose?

The test case describes the steps and guidance for testing a function module or business module. A good test case can make the system completely unfamiliar.Tester, Can be tested according to the use case. Purpose: discover system problems through case execution. Ensure that the projectQuality.

2,Write Test CasesBasis

The test case should be written according to the business of the system.RequirementDocumentation, functional requirements documentation, detailed product design documentation, and other guidanceDevelopmentTangible or intangible materials of the developer program. However, it should not be written based on the developed program. Because the purpose of use cases is to check whether the program meets the customer's needs.

3. When can I start writing use cases?

Because the use case is written based on the requirement document, and the use case is used to check the program, the preparation of the use case should be after the requirements are confirmed, during the development process as needed, testers should compile test cases as needed. After the program is developed, the tester can test the system based on the test case.

4. Advantages and Disadvantages of writing Use Cases

Benefits

1) The testing quality of the system can be controlled through the quality of control cases. Instead of focusing on the testing staff's abilities, mood, and other unstable factors ......

2) ensure the quality of each version is stable. Each release version should pass test cases to ensure the necessary functions are stable.

3) With the use case, you can use Automation Based on the use case.Test Tool(For exampleQtpTo improve the test efficiency.

Disadvantages

1) It takes longer to write test cases than to perform one or more tests. If a project only needs to be fully tested for less than five times and the time is tight, it is best not to write test cases.

2) When requirements change frequently, the test cases change frequently.

5. Do not write for test cases

1) if the project quality awareness is not controlled through the control case quality

2) If the project requirements are not clearly defined, the requirements are frequently changed, and there are no relevant requirements documents.

3) if the number of recursive tests for a project is small

4) if the tester is still accustomed to random testing, the system is not tested based on the test cases.

5) if the test case is just a delivery document ......

6) if the test case is based on the system that has been built, rather than based on the requirements ......

Article from the collar test software testing network http://www.ltesting.net/