Summary
I have a side job (free, but the point is fate, after all, I don’t have enough time), and I happen to be instructing some graduated programmers to find jobs. I found that the difference in ability is reflected in the hard work acquired, and the gap in professional development is formed in cognition. At the same time, the latest software testing resources (video tutorials, PDF documents, interview questions) in the last two months are also organized.
Friends who need this information can add my public account [Sad Spicy Bar] to receive it.
In the past few years in the industry, there have been many interviews. In my impression, the interviewers asked the most about performance and automation.
In fact, asking this question is very interesting, because I have encountered two situations in my career.
The first situation is that you say you will not, and then the company wants you, you go to work with joy, thinking that you can finally learn to automate with Daniel.
Then I found out after entering the job, I rub? These testers are all a little bit, including the interview with me?
The second situation is that you say you will, the company wants you, you go to work with joy, thinking that you finally meet a perfect testing team, and finally get rid of a little bit.
Then onboarding found that I rub? The project time is so tight, write a woolen automation, and then you start a little bit.
My name is Pippi and I am a software testing engineer. The above experience is my real experience.
Of course, in addition to the above two situations, there are many other situations. Let's think about it, why do interviewers ask about automation and performance?
The author believes that there are three situations:
The first is to directly judge your technical ability;
The second is to give salary according to your technical ability;
The third is to consider team building.
So why do you automate, but still let you do a little bit? The author believes that the most important reason is time.
For a small project, it takes about 30-35 days from the initiation to the end of the test. During this period, testers need to look at the requirements documents, make suggestions for improvement based on the requirements documents, and write test cases based on the requirements documents or product prototypes or UI design.
The time left for testing is often only about a week. The first day of manual testing can often run through all the smoke, but for automation engineers, automation use case design has just begun (note that I said UI automation is not interface automation). During the period of writing use cases, page elements remain unchanged Fortunately, once there is a change, no matter how good your package is, there is still code that needs to be changed.
So in terms of time cost and work efficiency, manual testing is definitely the first choice.
After the project stabilizes, your ear will ring, Xiao Zhang, he hasn't been busy lately, do you think you want to automate it? Then you start to write automated test cases.
In the author's opinion, writing automation use cases is more convenient at this time. the reason is simple:
The first is that there are basically no bugs in the project, which makes it easy to write assertions (assertions are similar to the expected results in manual testing);
Second, you have written all the use cases when you are doing manual testing. As long as you write the manual test cases carefully enough, the automated test cases can be implemented based on manual testing.
The completion of automation use cases can be said to be a borrowing from the iteration of product functions. If it is not to add new functions but to optimize the previous functions...
Hahahaha, when I didn't say it, I changed the original function after several product iterations.
Of course, if new features are added, your time can be used to do two things during each iteration of the smoke test;
One is to use automated scripts to verify whether the previous functions will have problems due to the new code integration;
The second is to manually test new functions.
Rough calculations, assuming that iterates every half a month, each iteration requires 5 rounds of testing, and a manual regression takes 5 hours. It is finally determined that in one year, automation will save you 600 hours, which is 75 working days, and also It saves the trouble of testing old functions and errors caused by fatigue.
We still return to the above question, why do interviewers ask about automation and performance? Automation has been talked about. Let's talk about performance testing.
According to a survey of some software testing practitioners in 2016, 80% of people are engaged in manual functional testing, 31% are engaged in performance testing, and 27% are engaged in automated testing and interface testing. (The reason why it doesn't add up to 100% should be due to multiple jobs) The proportion of performance testing staff is higher than that of automation!
We can analyze the reason, the essence of automation is still black box testing! Because all operations are basically to simulate user behavior, although it is possible to simulate multiple users through scripts, it is far from meeting the requirements of performance testing.
Because UI automation increases page rendering time, your company's bandwidth and server bandwidth are also uncertain factors.
If Taobao, Tmall, Jingdong, 12306, etc. lack performance tests, it may be a disaster for most humans. I rub? I finally waited until Double 11, you told me that the mall page could not be opened...
Speaking of functional testing, UI automation testing, and performance testing, I have to say one more thing here, interface automation testing.
Interface automation and UI automation design are basically the same, so I won't go into details. Generally speaking, interface automation precedes functional testing and UI automation testing. Doing a good job of interface automation will save a lot of time for functional testing. In general small enterprises, interface automation testing can basically meet the requirements of performance testing.
Having said that, perhaps we can make a summary. Manual testing meets the functional quality of the project, automated testing improves the iteration speed of the project, and performance testing is to satisfy the user experience at the same time.
Speaking of this, maybe many people are already impatient, because most people know it. I also thought about not writing these, but the reason I wrote these is to pave the way for the future.
I want to organize some series based on what I have learned, such as the realization of UI automation, the realization of interface automation, and the realization of performance testing in some scenarios.
I will write these series with a beginner as a starting point. Of course, there is a lot of this knowledge on the Internet, and I may not write it better than them, but I will write it carefully, which can be regarded as a summary of what I have learned.
I will write these series as soon as possible, because winter is coming soon, freezing hands...
In the end, if you have a chance to watch Li Zhi's 334, please help me say, I love to force brother.
Finally: benefits
In the technology industry, you must improve your technical skills and enrich your practical experience in automation projects. This will be very helpful for your career planning in the next few years and the depth of your testing technology.
In the interview season of Golden 9th and Silver 10th, job-hopping season, organizing interview questions has become my habit for many years! The following is my collection and sorting in recent years, the whole is organized around [software testing], the main content includes: python automation test exclusive video, Python automation details, a full set of interview questions and other knowledge content.
Don't be ashamed of getting an 8k salary, don't be complacent just because you get a salary of more than 20k, don't be complacent just because you get a 30-45 salary. Life is not to earn that little salary, what you need is to open a career.
May you and I meet and you will find something! Welcome to follow the WeChat public account: [Sad Spicy Article] Receive a 216-page software test engineer interview book for free. And the corresponding video learning tutorials are free to share!
Good article recommendation:
Talking about starting from a small company to a big factory, what did I do right?
Does it make sense for ordinary people to learn Python automation?