Table of contents
1. Some problems in the development of automated testing in the whole project
2. The road to the combination of automated testing and projects
3. Project system construction of automated test platform
Foreword:
An automated testing platform is a key component of implementing automated testing, which can help testing teams improve testing efficiency, speed up feedback cycles, and ensure the quality of software delivery. However, integrating automated testing with projects is a challenging task.
1. Some problems in the development of automated testing in the whole project
In the previous year, I summarized and communicated face-to-face with the technical team leaders of each product and maintenance testing group, and summed up several problems and some of their ideas in automated testing in project testing.
1. The product testing team believes that the efficiency of automated test development is too slow. When a new product starts to be tested, it starts to develop automated test scripts, which cannot keep up with the progress of the test project. It is possible that the iteration of the version is over, and the automated test scripts have not stabilized. not on.
2. The maintenance test group applied automated routine tests to the maintenance test project before. It spent a lot of energy to develop a large number of modules, but later found that most of these modules were not applied during the version iteration process, and the development The focus is often on those very basic functional modules.
3. The product test group and the maintenance test group did not cooperate before, and the business test scripts developed by each group did not know each other, which also led to repeated development to a large extent, and the developed scripts did not have good migration, which indirectly caused It reduces the waste of automated testing resources.
4. The automated test measurement is not quantified enough. Although the automated test index measurement was done at the end of the year, a lot of data was created by the testers, and the data is not quantified enough, so it is not too convincing. effect is not prominent enough.
2. The road to the combination of automated testing and projects
In view of the above problems, how to improve and summarize some points
1. The way to truly integrate automated testing into the test project is to start thinking about automated testing in the early stage of the project, instead of waiting until the project or after the project, so as to ensure that automated testing can be quickly applied to the test project. The method is as follows: (Of course, it should be noted that the previous versions of product testing are not recommended to apply automated testing)
1) Analyze the test project cycle and select the modules that require automated testing
2) Add automated testing consideration and review in the early stage of the project
3) Before the start of the project, start to write a keyword-driven test plan based on the test points for the new module, and generate a keyword interface library. Here, it is particularly important to specify that the test case also needs to be specified in the keyword-driven test plan. Ratios and parts that require manual testing.
4) When the test case is completed, assemble and develop business scripts based on the test case
5) While the product interface is determined, write the keyword interface implementation library, and pass the debugging
6) Automation begins to be applied to the project, deployed on the test system, real-time statistics and tracking
7) After the project is completed, measure and analyze the automated test items in the project (single module coverage, product feature coverage, product CBB rate)
8) Add the completed modules of the project to the routine test environment as needed
2. Prefer lack rather than abuse, fine work and iterative style. Formulate an automated test module strategy, and analyze whether this module is prioritized for automation in several dimensions, CBB>basic functions>product features
3. Establish a unified management automated test function module library. Each test group can view the modules and application product lines that have been covered by automated tests through this system library, and it is based on keyword test-driven development, unified standards, and good migration. The modules developed by the product test group in the project can be quickly migrated to the maintenance test group.
4. CBB, unified standard, unified measurement, manual test cases and automated test cases are all based on a module test point standard, which is convenient for refinement and statistics.
3. Project system construction of automated test platform
Based on the above ideas, the automated test platform has been implemented as follows:
1. Add a project management mechanism to the test platform, and establish and run automated test tasks based on the project.
2. Module management mechanism, automated test tasks run based on models.
3. Master-slave mechanism, each slave corresponds to the corresponding test module.
4. The result analysis and report management mechanism can view the automated test indicators based on the product line and project dimensions, which is convenient for staged analysis.
As someone who has been here, I also hope that everyone will avoid some detours
Here I will share with you some necessities of the way forward in automated testing, hoping to help you.
(WEB automated testing, app automated testing, interface automated testing, continuous integration, automated test development, big factory interview questions, resume templates, etc.)
I believe it can make you better progress!
Click on the small card below
