Where is the way out for software testing?
Business + programming! !
As time goes by, automated testing is no longer an optional job, and more and more companies list automated testing as a must-have job in the process of product testing.
If you happen to have just entered a new company, the leader will ask you to carry out automated testing as soon as you come up. As a fledgling tester, in addition to being at a loss, you can only silently lament your lack of ability, and there will only be one after another. question:
A: As a manual test, how to create opportunities and an environment to solve the bottleneck of our own improvement? (So panic! I thought I had reached the pinnacle of manual testing, but unexpectedly I panicked...)
B: How to enter the team of automation testing talents in the shortest time? (I just thought about it, what if it comes true...)
C: How to implement automated testing? (As soon as the leader spoke, he cried and cried and was afraid...)
D: How to continue to improve and develop in the future? (The boss is not young anymore, he can't accomplish nothing...)
Faced with the above problems, how should we deal with them? How to solve it?
You might do something like this:
1. I bought several books on programming languages, so thick! Even if it’s hard to understand something, there are too many contents, how can I remember it?
2. After finally remembering some, I can write two or three programs. How to do automated testing?
3. It is finally possible to write some automated test scripts. What are the requirements of enterprises for automated test engineers? How can I meet the requirements of the interview?
4. What is the follow-up development of the automated testing position? Can it be kept fresh for a long time? …
Listen to the automated testing experience and development direction shared by 15-year senior test engineers , which may help you solve many confusions in your work!
01Where do I start if I want to engage in automation?
Many of us are unwilling to stay where we are, and hope that we can be engaged in automated testing, and hope that we can gain a firm foothold in every company and be recognized, but where should we start now? And there is not much time, how can I quickly improve my ability?
(Pick-up notes: clarify the improvement goals, investment resources, improvement methods and the results achieved.)
Scenario 1. Go to work as soon as possible:
1. First, focus on the assessment points of the interview, determine the direction of an automated test, determine a project, and then carry out some actual projects according to the process and technical requirements of the automated test
2. Summarize and sort out work problems and automated test results
3. Prepare and sort out common interview questions to quickly meet the interview requirements
4. Not everything will be fine after work. No matter whether the company provides automated testing positions and jobs, we must use our spare time to invest at least 1-2 hours in automated testing projects every day.
5. After half a year, you must be able to undertake automated testing projects
Option 2. At least have a certain ability to automate testing, and then start looking for a competitive job:
1. Take at least one month's time and use the actual project as the background
2. Completely walk through the entire automated testing project from beginning to end
3. Be able to independently complete the automated testing work in a certain direction (web automation/interface automation/performance automation/mobile automation)
4. Ability to write independent automated test scripts
5. Ability to design automated test frameworks
Option 3. Fully equipped with automated testing capabilities and able to choose good jobs
In the promotion mode of Scheme 2, it has the independent working ability of four automated testing directions.
No matter which solution you choose, the most important thing is to have a certain amount of work experience in automated testing projects. This is the most basic requirement, because the standard for enterprise employment is not that we have learned or seen automation, but that we need to do automated testing ourselves. This standard must be met! )
02Follow the following steps to improve automation capabilities
The test boss gave us a very good planning direction, but relying on our own ability and resource reserves, we don’t know where to start just looking for projects, and we have never done automated testing work, how to do it? how to do it You can't do it on your own!
There is often a very large gap between ideal and reality, but as long as there are effective methods, the distance can be quickly shortened.
(Post-it note: To quickly improve automated testing capabilities, you can follow the steps below:
1. Find a project
It can be a project that I have done before, or it can be an open source project.
2. Clarify the direction of automated testing
It is recommended to start with web automation/performance automation/App automation. Because interface automation projects rarely find open source complete ones.
3. Clarify the automated testing workflow.
In general, if there are no special circumstances, the automated testing workflow is as follows:
① Precondition: Manual testing is basically completed, and the corresponding bugs are basically fixed
②The product demand or business process is basically stable, and the product has a long-term operation plan, not just for a period of time
③ Clarify the work goals to be achieved by automated testing.
Generally speaking:
√UI-based automated testing (web/app automated testing) is to maximize the efficiency and coverage of regression testing;
√Automated performance testing is mainly aimed at systems with a large amount of user visits or data volumes, to test the response speed and stability of the system;
√ Interface automation testing is mainly to improve the efficiency and quality of regression testing. The difference from UI automation testing is that interface automation testing is not affected by business process changes and UI changes. As long as the interface call parameters and return values do not change, the stability of the script is relatively strong.
4. Determine the scope of automated testing.
Generally speaking, content with high frequency of use and stable business requirements is included in the scope of automated testing first, and content with low frequency of use or frequent changes in requirements can be temporarily excluded from the list of automated testing scopes.
5. Design and develop independent automated test scripts.
The design and implementation process is as follows:
① Carry out version design, and gradually complete script development from simple to complex. The version design principles are as follows:
First test the data with a set of constants, quickly run through the script, and remove grammatical technical obstacles
Then replace the constant data with a set of variable data to prepare for script parameterization
Then use the list/dictionary type to input multiple sets of test data and perform a small amount of parameterization
If you want to greatly improve the test data coverage of scripts, use files to store test data and optimize
Optimized for validation of script's expected results
Scripting automated test reports
② Class diagram design for different versions
③Design the flow chart of each method according to the class diagram (steps 2 and 3 can be omitted after the scripting technology is proficient. When you are a beginner, you must design first, and then write the code after sorting out the ideas. Remember!)
④According to the class diagram and flow chart design, the script is implemented in different versions
⑤ Write comments first and then write the script program, debug and run while writing, do not run after writing everything, remember
⑥After discovering the problem, use debugging technology to quickly locate the problem, and then analyze and fix the bug. )
03Automation experience, share with you
That's right, you can only jump out of the old thinking mode and consider the solution to the problem with a new thinking. When the time is right, it is necessary to "gold-plate" yourself, learn and master more new skills, and create more opportunities for yourself! Finally, share the following test experience to encourage everyone:
1. No matter what industry you are in, within a few years after graduation, you must first lay a good foundation, especially technical work. This is crucial no matter whether you take the technical route or the management route in the future.
2. Hard work (professional ability) and soft power (emotional intelligence) are both important.
3. Be good at recording, analyzing and summarizing. For testing, it is similar to the summary of the root cause of classic bugs, the way to reproduce them, the methods to avoid missing tests, and suggestions for improvement.
4. See the big from the small. When a bug occurs, don't just limit yourself to this bug, but think more about the cause of the problem. Is there a problem with the process? Or other reasons? Is it possible to optimize the process to avoid such problems in the future? In this way, solving a problem is equivalent to solving a class of problems. So think a lot and make suggestions.
5. While you are still young, make reasonable use of your spare time to recharge. The time a person gets off work determines his height; how a person uses his free time determines how far he can go.
Python full-stack automated testing learning route
1. Essential Python programming content for automated testing
2. Basic content of Web UI automated testing
3. Web UI automated testing content
4. Basic content of APP UI automation testing
5. Practical content of APP UI automation testing
6. Basic content of API interface automated testing
7. Practical content of API interface automated testing
8. CI/CD continuous integration special technology
9. Practical technology of automated testing framework
I believe that those who see this, whether they are novices or seniors, have a general understanding of automated testing. I hope this article can help newcomers to better understand the software testing industry, and I also hope that this article can also help seniors who have several years of testing experience to make their career positioning, determine the future development direction, and do a good job of technical precipitation .
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you! Partners can click the small card below to receive