Several guidelines for automated testing:
Instead of coding test cases, they can be called automated tests. This is a gimmick that many companies now claim to be AT.
The AT code has many requirements.
The first is that your coverage should be wide enough. The automation of single-digit cases is completely meaningless.
The second is that your case must be reusable: the software changes every day. If your case changes with the software every day, then your case is completely unqualified.
The third is that the scale of the test should be large enough: either it takes a long time (more cases or stress tests), or there are more products to test. In this way, the advantages of automated testing can be reflected.
Several guidelines for test automation:
The first is to reduce the labor cost of all testing departments except for the tool development department. This is one of the ultimate goals pursued by test automation. ,
The second is to improve the quality of testing, not only the quality of test execution, but also the statistical quality of the test, the quality of data backtracking, and so on. These quality improvements can help test teams revise their test methods, instead of laying energy on endless data collection and analysis every day.
The third is to grab time. After a certain task is automated, the time is either shorter than the manual time, or it can be carried out in 16 hours of non-work. Free up engineers or project managers by letting the computer OT method.
Three starting points for automation:
The three starting points of automation are actually the same as the three principles. See which need is more urgent:
-
Cost: Automation does not necessarily revolve around test execution, but can also include test preparation, log extraction, data analysis, etc. List all the work related to the test one by one, and then find the repetitive parts that can be coded, evaluate the existing work costs and automation costs, find the most profitable work blocks and code them sequentially.
-
Quality: Similar to cost, only the difference between the existing quality status and the required quality of the work block needs to be evaluated during the evaluation, find the module with the most differences, and automate all the poor quality modules one by one.
-
Time: Same as the above two points, you need to find all the steps and work blocks related to the test, and automate the part of the critical path that is the slowest and most time-consuming.
The above are some video resources I collected, which helped me a lot in this process. If you don't want to experience the feeling that you can't find the information during self-study, no one answers your questions, and insists on giving up after a few days, you can join our deduction group [313782132], which has various software testing resources and technical discussions.
Of course, there are interviews. Interviews are generally divided into technical and hr interviews. In terms of format, there are few group faces. A small number of companies may have an intersection, but in general, the technical aspect is basically an inspection of your professional and technical level. , then hr surface mainly to see the person's overall quality and family situation character does not meet company requirements, in general, technology, then as long as through the technical hr surface is basically no problem (there are a few companies hr face will brush a lot of people)
we Mainly speaking on the technical side, the technical side is mainly to examine the professional technical knowledge and level. The above are also selected interview questions I have compiled.
Come on, test man! If you need to improve your plan, do it. It's better to be on the road than to wait and see at the beginning. There must be a law, and then there will be success.
If the resources are good, give a recommendation~