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.
I believe that many students who are new to automation and performance testing feel that performance testing and automated testing are similar. When I first came into contact with it, I thought it was similar. The difference is: to automate a user and run again, performance testing requires concurrency, and various designs are required. Scenes. Slowly I did more and found that the difference between the two is quite big.
Common points:
Automated interface testing and performance testing are similar in the way of processing scripts, especially when testing with tools such as JMeter and LR, such as testing HTTP protocol requests, you only need to simulate sending get or post requests, and interface scripts are easy to transfer Into a performance test script. But for web applications, automated testing and interface testing are quite different. Let's talk about the specific differences below.
difference:
1. Different test angles
The starting point of automated testing and performance testing is different, that is, the ultimate goal is different. Automated testing is based on functional testing. Cases are also derived from functional testing. They are usually used as regression testing. The actual test is business and function.
Performance testing considers the performance of a single interface, sometimes not too much consideration of the overall business failure, just consider the performance of the interface that needs to be pressure tested, such as processed tps, average response time, and number of concurrent users supported. Of course, performance testing will also focus on the testing of the entire process.
For example, there is a small partner who does performance testing to do interface testing. For the order operation of a certain product, the interface test is done to check whether the order is normal or not. The interface test script he wrote is the same as the performance test script. , There is only one interface for placing orders. Before placing an order, some product queries and account queries are not done, which is inconsistent in business.
2. Use different frameworks
If interface automation testing and performance testing are somewhat similar in script processing, as far as Web testing is concerned, the two are quite different. First of all, the framework used is different. Web automation testing uses Selenium Webdriver, which simulates clicking on the elements of the page, and performance testing is to record scripts and send requests. One is mainly to focus on page elements, what the backend does is completely black box; one needs to pay attention to which requests are sent, whether it is post or get, what parameters are passed, some knowledge of the backend still needs to be understood, a bit like gray box.
3. Different skills to master
Automated testing focuses on development and requires relatively high development language. If you just configure a ready-made framework for automated testing, the requirements are not high.
There are a lot of knowledge to know about performance testing, such as scripting language (C or java, etc.), operating system (Linux, commonly used monitoring commands, analysis thread when problems occur), database (query statements, table associations, indexes, Oracle AWR reports) ); If it is an advanced performance test, it is also necessary to understand the knowledge of architecture.
In general, automated testing is biased towards development, but you must have a thinking about testing; performance testing requires a lot of knowledge points, and truly advanced performance testing is about the same as a development architect.
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?