Mu Jiang starts from home at around 9:00 every day and arrives at the company around 9:30. After arriving at the company, Mu Jiang first boils a pot of good tea with a health pot. Remember to drink plenty of water when he is busy at work, and then listen to the sound of tea making While writing the work plan for the day, the work plan mainly includes the work content, study plan and summary of the day.
The plan cannot be completed every day. After the work is over, mark and summarize according to the actual completed content, and at the same time write down the problems encountered on the day, which is convenient for tracking the next day. The advantage of writing a work plan is that you can check what you have done every day at any time. It is a fixed daily work content, and the daily work content of software testers will vary according to the actual situation of the project.
Today, Mujiang will analyze the basic work content of software testers in the testing stage, which can be divided into the following stages:
1. At the beginning of the project, it can also be the beginning of an iteration
At this time, every day is basically based on being familiar with the requirements of this project or this iteration of functional modules.
Method: Generally, it is to read the document, sometimes it is to read the document for a day, or to participate in different review meetings.
According to the different ways of understanding requirements of different people, Mujiang likes to use XMIND to sort out the requirements of test points, and Mujiang likes to use a pen to organize them no matter what he does.
This stage is mainly to understand the requirements, analyze the business process of the functional modules, and sort out the test points as much as possible. The product manager discusses and confirms. The method can be discussed in person or confirmed by email. It is recommended to confirm by email.
If the project process is complete, the product manager will generally start to organize the requirements review at this time. In layman’s terms, it means passing the requirements. In the past, the company used the SE to organize the requirements review, and then the developers organized the review of the Story. Currently, the developers sometimes organize , Different people organize the review content to be different, and the focus of the testers will also change accordingly.
2. Preliminary work content of the project
At this stage, software testers mainly write documents.
Because the scope of requirements and test points have been sorted out in the early stage, then at this time, these things are basically output, and the output document testers call it test cases.
Method: Generally, it is written in excel, and it is possible to write test cases for several days.
After the test case is written, the tester will organize the test case review, which can be organized in a formal meeting or sent to the development and product review in the form of email. If it is in the form of email, it must be tracked, because most Developers don't like to read emails, and instant messaging can be used to remind developers and product managers to review test cases.
At this stage, developers are generally coding, which is also a very busy time.
Test cases do not have to be written in excel. For example, most of the project test cases are written in XMIND now. Mujiang is used to writing in this way now, and writing in XMIND can diversify the thinking of testers.
Nowadays, many companies don’t like to write test cases. They feel that it takes too much time. It may also be due to tight projects. However, Mujiang thinks that there must be such a process before the test case is executed. At the same time, it is OK to execute according to the test points sorted out earlier, and it is not easy to cause missed tests. Even if the company does not require it, Mu Jiang will definitely do such a thing before the test. No matter whether the project time is tight or not, this can be regarded as a A habit.
3. Mid-term work content of the project
This stage is the hardest stage for software testers - the test execution stage.
How: Tests are executed differently depending on the type of test
During functional testing, execution testing is mainly to test software functions, interfaces, and software experience, etc.; during interface testing, the execution phase is to call various interfaces through tools, and test test points such as value passing, parameter retrieval, and return of various interfaces.
At this stage, not only testing, but also a very important thing is to submit BUG.
It can be roughly divided into: writing BUG on the defect management tool, discussing BUG with developers, reproducing BUG, and tracking the processing flow of BUG. There are a lot of things to do during this period, such as continuous testing, continuous communication with developers, and reproduction of bugs.
During the second and third rounds of testing, it is necessary to perform regression testing on the bugs submitted in the previous period.
Software testers not only need to have the ability to find bugs, but also need to have the ability to analyze and locate bugs. Locating bugs can be analyzed and located by querying databases, background logs, or viewing source codes.
4. Post-project work content
The main things testers do at this stage are to write test reports and project/iteration summaries.
After the execution test is completed, the tester needs to make a conclusion about the test, whether the test passed or failed. At this time, the software tester needs to give the test conclusion, but cannot tell the development in a simple sentence that the project test passed. , can be launched, or this project failed the test, there are still many bugs, and the software quality is at risk.
All things pay attention to the basis, so software testing also needs it. Testers need to provide the project team with the basis of test results. Therefore, the test report generally includes the execution of test cases, and analyzes the test situation from various dimensions to analyze defects and remaining defects.
After the project is tested, software testers can use the project interval to summarize the project, generally outputting business requirements, which is convenient for other testers to review.
The above is the analysis of the main work content of software testers according to the testing phase.
Finally: The complete software testing video learning tutorial below has been sorted out and uploaded. If you need it, you can get it for free [guaranteed 100% free]
These materials should be relatively complete for friends who do [software testing]. This kind of learning materials also accompanied me through the most difficult journey, and I hope it can help you too! Everything should be done as early as possible, especially in the technology industry, we must improve our technical skills.
