Hello everyone, today I want to share a few problems encountered Number List in my work, and these problems have exposed many new problems. Let us find a solution together.
Because I have done testing for two years, even after changing jobs, I will often pay attention to testing-related matters. At the same time, my work experience in testing has provided a lot of help for my follow-up work, and the value of my team and testers It is also far beyond the functional test itself, so when encountering the following problem, there will be a lot to say.
Today's article is long, but it is a summary of actual combat, please read it patiently.
01 Some common problems
The first category: I chatted with a friend who was doing testing some time ago. He complained to me about the embarrassing situation of testing this position, such as lack of right to speak within the team, often being "disgusted" by developers, and often unwilling to change the proposed bug development, or even Being spit on the back, etc., these may be common problems in testing work. Then asked me if I could transfer the requirements or products, and would it be better after the transfer.
The second category: some so-called "minor errors" encountered in the project:
The development is often insufficiently prepared during the launch process, and the launch package is omitted;
The database update field is missing, and the configuration file is still using the test address;
The "baffle" added during the test was put into production without removing it;
Insufficient preparations for production verification, and the verification environment is blocked.
I believe that many project teams will encounter these problems more or less. The online task that could be completed in 2 hours was stunned in the middle of the night.
These problems may appear to be details or attitude problems, just like what we used to say when we were in school, "I was sloppy and didn't check carefully." That's how I consoled myself back then.
But looking at it now, behind every small problem, there are problems in team management, process system, work awareness or work attitude. If you want to solve these problems, only treating the symptoms will not be able to cure them, but may also expose other more serious problems. The so-called "treating the symptoms but not the root cause", "it is better to raise the soup to stop the boiling than to draw wages from the bottom of the pot".