Many people don’t know what the testing position does, not to mention others, I don’t know either, so I took this question to consult my teacher. The teacher has also done testing in the company for many years before, and now I want to work hours She chose to be a lecturer because she was more free online. She told me her work experience.
When I entered the interview at the first company, the test supervisor asked me questions, and the relevant answers were a bit vague, but from this question, I can roughly understand that the test supervisor is examining my testing thinking.
First of all, what are the aspects of the quality of this cup? That is, what are the commonly called needs? For example, the explicit demand should first be a cup, not a bottle, jar, etc. The purpose is to drink water; what about the implicit demand? That is more general, such as size, height, volume, manufacturing materials, temperature tolerance range, and other details such as color, rounded corners, etc.
Secondly, how to accurately obtain and express these needs, that is, how much relevant index data is. If you want to know the size, height, and volume, you must use related measuring tools, such as rulers and compasses. To know the temperature tolerance range, a thermometer, etc. may be used.
During the completion of the test work, the original requirements (including implicit requirements) must be clearly understood before the test design and execution, and then there must be a corresponding test plan, what types of tests need to be performed, and what test tools to use, etc.
I am very grateful to the test supervisor for his guidance on my testing work, not only in specific skills training, but also in other tasks for guiding my thinking in testing.
After entering the company after the interview, the initial testing work is mainly functional testing.
In the next year, I really came into contact with the actual production process of project development and delivery. In short, the work tasks are endless, and there are always countless requirements to be developed and tested. Bugs are tracked. How to maintain a clear position in the middle is very important. The test supervisor emphasized a few points to me:
1. The basis of the test and the baseline of requirements must be clear, and early participation is required;
2. The test must have a plan and a use case design, and cannot be carried out at will;
3. To track bugs, you must have your own opinions and principles;
4. To grasp the test results, there must be result analysis.
The launch of the project requires a combination of your above testing process and a summary report based on the current situation, and even the project manager should listen to your opinions. Your role is not only testing, but also quality assurance.
Of course, the above situation is just a little bit of the problems encountered in the test, such as a grain of sand in the desert (how did this child get here), but it also made me realize that the test is independent and important.
In the later project testing work, while practicing the ideological principles passed by the test supervisor, I also learned about relevant testing books, tools, and skills, and combined with work to carry out related practices, gradually my testing ability became stronger and stronger.
This is some summary of my entry into the company. Friends who are studying automated testing strongly recommend this video.
[A full 200 episodes] A collection of super-detailed advanced tutorials for python automated testing, a real simulation of actual enterprise projects