Thoughts on automated software testing implementation

(1) test data and test script Separation

Personalized parameters and common parameters are stored in different files.

TC creates data flow parameters and data configuration parameters (VLAN, Mac, and traffic template.

(2) The execution sequence of the test script can be dynamically adjusted. The passing rate is high, simple scripts are executed first, and the passing rate is low. The execution of other scripts may affect the execution of the script.

(3) In order to avoid the impact of the original use cases on the New Use Cases of the new module, initialize the script for fault tolerance Processing (first check whether there is an error, and if the error is fixed and repaired, continue to execute; ).

After each test script is executed, add the test configuration to restore the initialization operation to reduce the impact of the previous script execution on subsequent script execution.

(4) The Script Execution priority first corresponds to the case priority.

(5) make proper planning before implementation of automation. For example, compile a test script for a function module, analyze the function module, and summarize the public interface functions of the use case of the module, the interface functions written in this way are more universal. An interface that is not written by a user is only applicable to his script. The possibility of others calling the script is not considered. Planning public interface functions, global parameters, module parameters, and script-level parameters will greatly reduce subsequent script maintenance costs.

(6) test case design. A good test case is the basis of the test script design. How is it good? Do not overwrite the Function Points for one test case. Otherwise, the analysis of the test results may be troublesome.

(7) track the implementation degree of automation, automate those use cases, and automate those use cases, which is very helpful for testing and execution, reduces or avoids the possibility of test failure leakage.

Thoughts on automated software testing implementation