In the IT industry, in most cases, the test is back-to-back, so what exactly did the test do? How can the test be avoided? Please listen to me and explain it to everyone.
First of all, we have to understand how different people achieve quality in the entire software development process.
For a better description, we will quantify the product.
1. Generally speaking, the source is of course the customer. Customers put forward their own demands (maybe it is just a psychological expectation). At this time, we think that the customer’s expectation for the product is 100.
2. Then we will meet the customer's requirements and product personnel. After a long period of investigation and communication, they have made basic requirements and product prototypes. At this point, the actual value of demand and product prototype is 90. This is already a very high score. But it should be noted that the needs and products will not be recognized. They will definitely say that what I have made is 100 or even more than 100, so as to demonstrate their professionalism.
3. Then, the designers began to do architecture design, outline design, and detailed design according to requirements and product prototypes, and the design score made at this time was 80. Similarly, design will never admit this fact. They will definitely say that what they have made is 100. Then in order to reach 100 verbally, the designer must "recognize" that the demand and the product made is 100, otherwise it will not make sense .
4. After the design is completed, it is the turn of the development students to play. The development students finally made the software after arduous and excellent operations such as overturning the wall and moving bricks. At this time, generally speaking, the quality of the software is likely to be far less than 80. The value is hidden, so let’s make it equal to 60 (passing line). But similarly, development will not be recognized, and development will definitely say that the software made by brother is 100 in quality.
5. The final test is here, what exactly is the test going to do? Testing is to detect and develop the final delivered software through various technical means to determine how the quality of the software is? Then the result of the test is closely related to the technical level of the test itself.
Test result = actual result + error interval.
Error interval (Y) = a * test ability (x) + b
a=-1, the value of b depends on the difference between the expected maximum value and the actual minimum value of the quality.
The formula is not perfect, but simply describes the relationship between test capability and error.
So what does this represent? It means that the greater the tester's testing ability, the smaller the error interval.
So why is the test always unpopular? Do you always have to go back?
Because in most cases, the ability of the test itself determines that errors always exist. The worse the ability, the greater the error. This will result in a product with a score of only 60, you give it 80 points, and then it goes online. That means there are a lot of bugs that have not been tested. In the end, everyone will say, what's the matter with you? Why are so many bugs not found?
So how can the test not be backed up? It is to work hard to improve one's abilities.
First of all, how can the error interval of 80 to 60 be reduced? It is not possible to do simple black box testing. A good understanding of development is required here. So at this time, testing may start to learn to develop, and I can also do things that development can do.
Secondly, let's just think that you can find out the error of 60-80, but then you will be scolded when you give it to the customer. Why? Because what the customer needs is 100, but you only give him 80. At this time, the design will pop out for testing. What's the matter with you, haven't I found any flaws in my design? Why didn't you find such an obvious defect?
Okay, well, my testing ability is not enough, I will learn architecture design, and then I will test.
Finally, when you have worked so hard to find the error (bug) between 80-90. Demand and product-level problems have broken out again. Is there a solution? Yes, it is to test students to continue to study, learn the knowledge of needs and products.
It can be seen from this: the test is to take the least money and worry about the most. To do a good job in testing, you must understand testing, development, architecture design, and product requirements. Otherwise, the test can only be backed, backed, backed up. . .
In the technology industry, you must improve your technical skills and enrich your practical experience in automation projects. This will be very helpful for your career planning in the next few years and the depth of your test technology mastery.
Send a sentence:
The appearance of the world depends on the gaze you stare at it. Your own value depends on your pursuit and mentality. All good wishes are not possessed in waiting, but in struggle.
I am a test lady in the workplace! Just finished the automated testing tutorial, I will share it again. Testers who are interested in python automated testing, web automation, interface automation, mobile terminal automation, interview experience exchange, etc., can follow the WeChat public account:[Sad Spicy Strips], Obtain the interview information of the software test engineer from Dachang! My learning exchange group: 902061117 group has technical experts to communicate and share together~
If the article is helpful to you, please reach out to make a fortune and give me a like. Thank you for your support. Your likes are my motivation for continuous updating.
Recommended reading:
What kind of person is suitable for software testing?
Talking about starting from a small company to a big factory, what did I do right?
Want to switch to software testing? Come and see if you are suitable
From self-study to work in software testing, how should software testing learning be carried out?