When it comes to the relationship between testing and development, you will definitely think of a word "enemy". Developers produce both code and bugs. Developers will inevitably produce bugs, so testers must exist to check out as many bugs as possible before software delivery to ensure that the quality of software delivered to customers is better. One produces bugs and the other picks bugs, which seem to be opposites.
It's always easy for tests to quarrel if they take a sloppy approach to their work. Therefore, the following scenario is repeated every day in different companies.
test:
Let the test reproduce every time a bug is raised, the description is so clear, can't you operate it yourself?
If there is a bug, just say that your local is good, whether the version is wrong, users will not do this.
When a bug occurs, let the test clear the data, restart the phone, and the bug will disappear in a few clicks, pit...
development:
Such a small bug needs to be developed and corrected, the impact is not big, and it is time-consuming and labor-intensive. Does the test understand project management and estimate risks?
It took time to investigate, but it turned out to be an invalid bug. Did the test clarify the requirements? What a waste of time.
It's obviously a P3 bug, report me to P1, as for?
The test is always digging into the cause and solution of the bug, but the test does not understand the code and is too lazy to explain.
……
Testing and development often cause disagreements because of different responsibilities at work.
Some advice for testing and development:
Participate in the review of software requirements documents together, and have a clear understanding of the functions to be realized by the program. If you have any questions about the requirements, you must raise them in time.
After reaching a consensus on the requirements, the software developers write the program strictly according to the description in the software requirements document. If there is any difficulty in program implementation, they should bring it up for discussion. Software testers verify the functions of the program strictly according to the description of the requirements. If the program implementation does not match the requirements, they should contact the software developers in time to solve the problem together.
If the development time is tight and manpower is insufficient, testers can help to set up the test environment. After the program is written, the developer can immediately perform unit testing and integration testing.
Although they perform their duties and may be in different departments, everyone has the same goal: to make high-quality software products that satisfy customers. Developers and testers must work together for this goal.
And as a tester, you need to master the skills:
1) Programming language
At least one computer language must be mastered, whether it is a simple programming language, or other scripting languages, such as python and so on.
2) database
At least one kind of database DBA must be mastered, familiar with the operation of SQL, proficient in using JOIN to query, and know the usage of HAVING. Testers must be proficient in database operations.
3) Operating system
Familiar with system installation, configuration, management, familiar with common Linux command line operations, etc.
4) Solid software testing theory
Theory comes from practice. If you master more theoretical knowledge and use more methods when designing test cases, the coverage rate of test cases will be higher and bugs will be easier to find.
5) Try to analyze the problem yourself
After finding the problem, try to find the cause by yourself, first determine the non-environmental factors, such as checking whether the configuration is correct, whether there is a problem with the network, etc., and then after determining the non-environmental factors, save and record the system prompt information;
If there is a log function, then first look for some information based on the log, and provide as much information as possible to the developer of the places you have checked and the analysis information you have done, instead of just throwing the error log or error message to the developer for analysis Never mind.
6) Learn more about knowledge other than projects
Doing testing requires extensive coverage. Unlike development, testing must be able to accept any type of project, because testing is a methodology, and methodology is not limited by a certain product or field.
Finally: In order to give back to the die-hard fans, I have compiled a complete software testing video learning tutorial for you. If you need it, you can get it for free【保证100%免费】
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. I hope it can help you too!
How to obtain the full set of information:
