Performance testing-continuous testing and performance test construction (22)

What is continuous testing?

Continuous testing is defined as: The process of performing automated testing within a software delivery pipeline with the goal of obtaining immediate feedback on the business risks of pre-release software.
To complete continuous testing, we still need to go back to the definition, which has three keywords: software delivery pipeline, automated testing, and instant feedback.
First of all, continuous testing requires a complete pipeline, which represents the CI/CD process. Continuous testing needs to be incorporated into the overall process of information system development.
Secondly, in order to ensure immediate risk feedback, testing activities need to be carried out at various stages of the pipeline, including static code scanning, unit testing, integration testing, single interface function testing, business function testing, UI testing, performance testing, etc.
Finally, in order to prevent the test execution at each stage from affecting the overall delivery time, it is necessary to replace repeated manual operations as much as possible through automated technical means, improve testing efficiency, and ensure test quality.
Note that the above-mentioned automation technology does not only refer to functional test automation in the traditional sense, but refers to the testing technology that can be used in each testing stage to reduce manual duplication of labor and form a platform-based test through the combination of specifications, technologies and tools. Capabilities, such as static code scanning platform, interface automation platform, UI automation platform, full-link stress testing platform, etc.

Continuously test value

Building continuous testing can bring the following value to enterprises.
1) Better user experience.
2) Smaller repair costs
3) More stable system

continuous integration

It generally means that after development engineers modify and submit the code, through standardized build operations and unit testing, if there are no exceptions, the changed code will be merged into the main process.
The commonly used testing method during the continuous integration phase is unit testing. In order to ensure the effectiveness of unit tests, coverage indicators are generally measured to guide the design and execution of unit tests.

Guess you like

Origin blog.csdn.net/seanyang_/article/details/132917108