Shulou(Shulou.com)06/02 Report--

A test case is a specific set of input data, operations, or various environmental settings and expected results provided to the system under test for the implementation of the test.

Test cases control the execution process of software testing, which is the further instantiation of each test project.

Benefits of test cases:

1. Organization: writing test cases is beneficial to the organization of testing.

2. Functional coverage: test cases can ensure that functions are not left out.

3. Repeatability: the same tests must be repeated many times during the project to find new software and ensure that old defects are fixed.

4. Tracking: the test plan can be tracked through the design of test cases.

5. Test confirmation: through the test cases, we can effectively supervise the test process, evaluate the test accurately and effectively, and have a quantitative result on whether the test is completed or not.

Content of test case: project name, program version, function module name, test purpose, preset result, use case number, related use case description, input data, expected results, actual results, test report, etc.

Update and maintain test cases:

1. No matter how well the tester designs the test case before starting to execute the test case design, as the test goes on, the requirements and design may change, and the function of the system will also change, so it is necessary to design new test cases.

2. For rare project documents, test cases must be developed at every stage of the development process. In order to adapt to this development, test cases must be added or deleted.

3. When executing the test, the tester will learn the relevant knowledge about the system and design new test cases. 、

4. Test cases can be maintained by configuration management system.

The basic capabilities of the software:

1. The software should be able to accept input

2. Software should be able to produce acceptable output when accepting input.

3. The software can store input values or computing structures internally in the form of one or more data structures.

4. The software can use the input and stored data for calculation.

Principles for designing test cases:

1. Obtain valid test data,

2. Act like an inexperienced user.

3. Look again where software defects have been found

4. Rely on experience, intuition and premonition

Key points to note in installation testing:

1. Pay attention to different installation combinations

2. After the installation exits, make sure that the application can start and run normally

3. View registry information

4. The unloading process is also important.

5. For Cmax S architecture, you can install the client first and then the server to test whether there will be any problems.

6. Test on at least one laptop

7. Test the impact of installing this system on other applications.

Interface testing-the standard of an excellent interface:

1. Comply with standards and specifications

2. Intuition

3. Consistency

4. Practical,

5. Flexibility

6. Comfort

7. Correctness

Principles for selecting test methods:

1. Boundary value analysis method must be used in any case.

2. Supplement some test cases with the method of equivalent class division

3. Append some test cases by error inference.

4. If the function description of the program contains the combination of input conditions, the causality diagram method should be chosen at the beginning.

5. If a function of the program is suitable for automatic testing, automatic testing and random testing can be used.

6. The software that obtains the requirement specification can adopt the method of test outline.

7. The method of state diagram can be used for process software.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.