A software testing enterprise-level practical project worth 5k, just to answer how you learn software testing!

How to learn software testing. Before answering this question, let me analyze what the entire testing process of a project in an enterprise is like. If you understand the testing process of the entire enterprise, you will know what the enterprise needs for testing. So you will understand how to learn to test.

 

1. Requirements:

When we receive a request from an enterprise, first of all, we generally intervene from the requirements, so we participate in the requirements review, clarification of requirements, and finally the implementation of the requirements. It is very important to clarify the requirements during the whole process. If the requirements are unclear, the final test results and test quality cannot be controlled.

2. After the requirements are clarified, we will start to make a test plan. The test plan must include people, time, tasks and detailed disassembly of tasks, rounds of project testing, etc. After the test plan is made, test cases are designed. After the test case design is completed, the test case review is carried out, and then our environment deployment, test execution, and test execution are divided into multiple rounds. In each round, we focus on testing those, and test The bugs that come out are submitted to bug management tools such as jira, and then the life cycle of the bug is tracked. (It is necessary to know the severity level definition of the bug in the process of submitting the bug)

In addition, our daily test needs to send our test daily report, notice, product manager, project manager, test supervisor, R&D supervisor and other project progress, whether the current test status is normal, the specific percentage of the progress, how many bugs, bugs Level distribution, whether there are currently blocked places. If there is a blockage, where is the blockage, who will solve it, whether there is a risk, how to control the risk, and so on.

3. We still need to use some tools during the testing process, but they are tools for packet capture analysis such as Charles and fiddler, or performance testing tools such as postman and jmeter, or we need to do automated testing during the process, so it will involve To UI automation testing, interface automation testing, performance testing, etc.

4. After the whole process of testing is completed, then we will go online. Before going online, we need some test reports. After the online is completed, we will review this iteration, analyze the good ones and the bad ones, and carry out the bad ones. Replay.

So through the whole process of project testing by the enterprise, then you have to know clearly:

1. What is software testing, the concept of software testing, the life cycle of software testing, and the entire testing process

2. Familiar with requirements review and requirements clarification process

3. Learn to make a test plan

4. Learn to write test cases and master common test case design methods

5. Learn to test execution, and use bug management tools (jira, Zen Tao, bugzilia, redmine, etc.) to submit bugs and track the bug life cycle

6. In the project, you must learn to write project daily reports, report daily progress, timely control risks, and do a good job of risk warning

7. In addition, it assists you in testing with higher efficiency and better quality, and you can use automation tools, performance tools, etc.

Linux log analysis, server deployment

mysql database connection, create data, delete data, abnormal data scenario creation and project combination

postman interface function test

Python+Appium App automated testing

Python+Selenium Web automated testing

Python+requests interface automated testing

Jmeter performance test

...

8. Proficiency in writing test reports

Familiar with the use of different project modes, you need to have real projects, such as front-end and back-end separation projects, micro-service projects, agile projects, exploratory methods, how to combine APP projects with projects, etc.

So actual combat is the most important thing. Without actual combat, everything is just talk on paper.

If you can't learn the actual combat of the project, it will be unreliable. Those who only study theory are unreliable, and those who don’t know how to play enterprises are unreliable, so do you think people who are not in the enterprise know the needs of the enterprise? Enterprise model? Business process?

Actual combat of software testing projects :

 

 

 

 

 

If you need actual project combat, you can click the small card below to get it for free! 

Guess you like

Origin blog.csdn.net/qq_48811377/article/details/131209088