initial stage
The primary stage needs to master four aspects:
First, the basic knowledge of software testing, the writing method and testing process of test cases.
Second, master Zen, svn and other necessary tools, as well as defect definition and test plan writing methods.
Thirdly, the ways, methods and protocols of web testing and app testing.
Fourth, the interface tests the operation and use of postman tool, and the front-end basic knowledge h5 and css.
intermediate stage
There are six aspects to master in the intermediate stage, and the use of some tools is involved from the intermediate stage.
Firstly, the environment construction of qtp automation tools.
Second, the environment construction of loadrunner performance tools
Third, the environment construction and interface stress test of jmeter performance tools
Fourthly, jmeter script enhancement and app/web performance testing.
V. Operation and use of the fiddler package grabbing tool and jenkins automatic deployment tool.
Six, mysql database, sql statements
later period
The advanced stage is in the opposite order, with some analysis and opinions, as follows:
First, the ability of business analysis
1. Analyze the overall business process.
Without knowing the business of the whole company, there is no way to test it.
2. Analyze the measured business data
What data do you need to understand the whole business? What do you need from users? Which ones are provided by yourself? What can be false data? What must be true data? Which library can I use when adding data?
Only by understanding the database architecture of the whole software can we know which data comes from which table and header, what is its logic and whether there is any connection.
3. Analyze the system architecture in the test.
What language was it developed in? What server are you using? What kind of environment do you need to test? What is the overall test environment like?
If it is missing, you need to build an environment and architecture. Generally, after going to a new company, the structure is set up. Get to know it and get familiar with what kind of structure these old employees have published and done before.
4. Analyze and test the business module.
What modules does the whole software have, such as home page, registration page, login page, member page, product details page, coupon page and so on?
Understand how many modules need to be tested, the relationship between each module, and then how to divide the work.
5. Analyze the resources needed for testing.
I need several computers, several mobile phones, and what kind of system and model do I need for mobile phones.
For example, to test the performance of a website, the computer configuration can not meet the standard of testing 5000 concurrent users. Either upgrade the computer hardware configuration, or combine multiple computers, and how many computers are needed to combine multiple computers, all of which need to be planned in advance.
6. Analyze and test the completion target
What are my performance goals? What is my functional goal? What is the online standard I want to achieve? Performance goals, such as when I want to reach 5000 concurrent users, the cpu utilization rate should not be higher than 70%, the memory utilization rate should not be higher than 60%, and the response time should not exceed 5 seconds. For example, the whole business process runs smoothly, all branch processes are fine, all interfaces can be called each other, the overall ui interface is fine, and compatibility is fine.