Test progress is a matter of great concern to the leadership. Testing students who control the project test progress will definitely allow the interviewer to score points for you.
In the daily testing process, it is essential to control the test progress and understand the factors that affect the test progress. So, what are the factors that affect the project test progress? How to solve it?
1. Test students’ own abilities
Some people are very capable at work, have unique skills, and are simply masters of bugs. Not only is the testing speed fast, but it is also of high quality. It can quickly find bugs and never miss a test. This unique skill requires more summary and accumulation. Quantitative changes lead to qualitative changes.
The solution : skills training, which can be organized internally or externally; develop employee learning plans and summarize and share them regularly; organize brainstorming and ask one or two testers to talk about a certain function they are responsible for (randomly The test ideas and test points extracted) were supplemented by others to make everyone aware of their own thinking limitations, open up their ideas, and improve the efficiency of subsequent test execution.
2. Test students’ proficiency in the project
For a project, if the test students have been following the test and are very familiar with the functions, then the test will be easy and the speed will naturally be very fast; if they are students who are temporarily arranged to test, they may have to ask questions while testing, and the speed may be slower. The progress is naturally a little slower.
The solution : Reasonably allocate the testing tasks of new test students. Functions with high business and logical complexity should account for a relatively small proportion; then give different arrangements according to personal circumstances. For example, those with good aesthetics can be assigned more UI&UE aspects. Testing tasks, careful and rigorous personnel can assign tasks in data reporting to pursue the maximum value of the testing team.
3. Test quality
As we all know, if the quality is very good, one round of testing can be completed; if the quality is poor and there are many bugs, it will take time to raise bugs, fix bugs, and verify bugs, which will affect the testing progress.
The solution : Improve developers' quality awareness, persuade development leaders to emphasize quality in meetings, and include it in developers' performance appraisals to make quality deeply rooted in developers' minds; introduce smoke testing, and the test team will provide smoke test cases. After passing the "development self-test + test verification", follow-up in-depth testing will be conducted (if the test verification fails, it will be included in the developer's performance appraisal).
4. Test environment stability
If the test environment remains unstable during the test process, sometimes available and sometimes unavailable, it will also seriously affect the test progress. For example, a project I recently took over for testing required calling a third-party interface for login. However, the login interface was very unstable. Sometimes I could not log in for an hour, which seriously affected the progress of the test. I consulted a classmate who had taken the test on this issue, and the explanation was that the project was special and unsolvable.
Solution : If the external interface (system) is unstable, you can use mocking and other means to bypass the third-party interface (system) and try to ensure the testing progress of the internal interface (system); when the external interface (system) is stable, seize the time to conduct centralized verification Use cases for mock replacement parts.
5. How quickly development students handle bugs
If the testing students expose all the bugs, but the development students have multiple projects at hand, and other projects have higher priorities, they must first support other projects before fixing the bugs, which will also affect the testing progress.
The solution : Accurately mark the priority of all bugs in the bug list, and reach an agreement with the project leader, product manager, and development leader, and then let the development students prioritize high-priority bugs; lower-priority bugs can be postponed Process it, or arrange it for other free development students to process.
6. Detailed level of product prototype documentation
If the product prototype document is very detailed and the detailed design is very thoughtful, then the testing process will be quick and you can just follow the logic on the prototype. This is the ideal situation.
However, it is normal to confirm while testing. If the document is too rough and the development students do not confirm with the product students during the development process and rely entirely on their own understanding, then the test students will repeat the uncertainties during the testing process. Check with the product and any unreasonable things will be treated as bugs. This is equivalent to doing a requirement twice, and the progress can be imagined.
Solution : Move testing to the left. After testers get the prototype (requirements), they analyze and sort it out in a timely manner. If they encounter vague, ambiguous, or missing areas, they sort them out in time and confirm with the product; after confirmation, list the possibilities for developers We will deal with the errors, and then take the time (based on the developer's convenience) to verify and confirm with the developers one by one. This will avoid problems as early as possible.
If the deal is done and urgent problems are encountered during the testing process, seek product confirmation directly in the discussion group (including product managers and developers). Non-urgent problems will be sorted together in units of days (such as 30 minutes before get off work every day) ) Find the product and confirm it with the developer.
The above six points are the six major factors that affect the progress of project testing. Once they are obtained, they are not only beneficial to interviews, but also helpful to the promotion of our daily testing work and even promotions and salary increases. A simple list is at your fingertips. Four benefits:
1. Conducive to evaluating test time;
2. Conducive to applying for testing resources from leaders;
3. In case of project delays, reasonable basis and response plan can be given;
4. Or when encountering these factors during the testing process, Being able to put forward risk and emergency plans in a timely manner will make your leaders think you are a mature and reliable test classmate.
Practical cases
Optical theory is useless. You must learn to follow along and practice it in order to apply what you have learned to practice. At this time, you can learn from some practical cases.
If it is helpful to you, please like and save it to give the author an encouragement. It also makes it easier for you to search quickly next time.
If you don’t understand, please consult the small card below. The blogger also hopes to learn and improve with like-minded testers.
At the appropriate age, choose the appropriate position and try to give full play to your own advantages.
My path to automated test development is inseparable from plans at each stage, because I like planning and summarizing.
Test development video tutorials and study notes collection portal! ! !