What Is an Audit Cycle?
The test cycle refers to the entire testing process from the establishment of the test project plan to the submission of the BUG, including the software project test plan, test requirements analysis, test case design, test case execution, and BUG submission.
The design development process for testing is as complex and daunting as the application being built. If you fail to start as early as possible, testing may be inadequate, or you may need to attach a long test and error correction schedule to the development schedule, which would be contrary to the original intention of iterative development. In addition, test planning and design activities can reveal faults and defects in application definitions. The sooner these issues are resolved, the less impact it will have on the overall timeline. The problems found in the evaluation process can be solved in this iteration or left to be solved in the next iteration. Evaluating the completeness of the iteration by verifying the requirements that have been implemented is one of the main tasks of the evaluation. There is always some kind of "demand creep" between iterations, and you need to be aware of it and be able to manage it.
How tests are performed depends on a number of factors: your application area, budget, company strategy and risk tolerance, and staff. How much you invest in testing depends on how you assess quality and risk in your environment.
Test concept name | aims | range | Everyone | Should continuous integration | tool | Remark |
unit test | Verify that the source code unit works correctly | class | Developer | Yes | JUnit | Should generate 100% code coverage report |
function test | Code-oriented, testing features with sample data within components | class | Developer | Yes | JUnit | Should mock dependent interfaces |
Integration Testing | Depend on a certain environment for some path coverage tests | components | Developer | Optional | JWebUnit TestNG | If testing is fast and environment dependencies can be easily installed automatically, can be included in continuous integration |
Smoke test | Ensuring critical functions are running | application | Developer | no | JWebUnit TestNG | Run the code before submitting it to testers, which is equivalent to integration testing for web-app modules |
Regression Testing | Look for regression bugs, that is, bugs that only appeared on new releases. | application | Testers | no | Selenium | Re-run tests run by previous versions |
Completeness test | Focus on bug fixes and new features | application | Testers | no | Selenium | Add new test cases for new features |
System test | Test the entire system for functional requirements specification (FRS), system requirements specification (SRS) | application platform | Testers | no | Selenium | May include more tests, like usability tests |
Platform test | Runs on different hardware and software platforms | application platform | Testers | no | Selenium | |
Performance Testing | Eliminate bottlenecks by collecting application data | application platform | Developer | no | JMon, ab, httperf, JMeter | |
Load test | Exposing non-surface bugs to ensure performance | application platform | team | no | ab, siege httpref | Load testing is sometimes called large data testing, or endurance testing |
pressure test | Try to destroy the system by running out of resources or deleting resources | application platform | Testers | no | ab, httpref | Also called rejection test or recovery test |
User verification test | A final verification of required business functions and correct system functions is performed in a real-world environment | application platform | client | no | Client decides | Rejection test or recovery test |
[1]
