Testing and development of this opposition fate ah
If friends feel contempt for testing practitioners ah, please turn off this page, prejudice does not look good with the ~
Life is like a journey, not everyone sees the same landscape, the world, life and values is different. Do not try to change others, because your point of view in his world and no examples or examples of the results in his world, you end up with the opposite.
Ten years ago looked a software testing books, which have a theory:
-------------------------------
A software defect found Composition: 8: [2 = (2: 8)]
8: 2, defects found divided into 10, where 80% is found in the development stage UT, 2 flows into the test phase.
2 = (2: 8), this test phase 2 to be seen as a 10 percent, 2 percent of which are found in the testing phase, 80% is released after customers discovered.
-------------------------------
At the time of this theory is to pop the nose, but now eight years for practitioners to test me, this special What truth too, too true.
Even more will function, safety, performance, automation, at most, to strengthen the second ratio to 5: 5.
So there must be total 10 to 1 to 1.6 to defect flow production environment, and the fact that the defect is always found in the software release after complaints of customers.
The next will not throw this proposition to solve. Certainly there are some great God might have a solution, but it is definitely unique. This world is not Jarvis.
Work for so many years, observed many, many, cough - that is, come into contact with all the development, of which only two can do this 8 UT own code to find flaws finish. May be its own level is not high enough, the reach of more outstanding development chiefs.
This two colleagues talk about it (I was actually those who want to Tucao, but Zaoxin, or talk about positive energy),
Seven years ago, just to work, I was also a developer, to write front-end MFC, C / S project, now do the test, ashamed! Ashamed! The colleague had just come out military jobs, work super careful. He then received a large amount of code needs two weeks, it took seven days to flow charts, timing diagrams, detailed design, pseudo-code and other documents have achieved, followed by three days to finish the code. Code three days to get strong, right? However, a more powerful here, watching him write Gtest, one day the Gtest all his functions full finish, and then one by one test, all the scenes ran the mass participation, test and correct before submission, at my side the whole watching him live (dead time want to make their own, did not sit so close to infect his excellent). Test really did find a few problems. This artisan spirit, how to say! Now there should be, but are present in the manufacturers estimate. The second year I worked with my colleagues on three sides HW into it.
Another trivial point, in an outsourcing company, has been transferred at this time I tested for a long time, the colleague took seven days the amount of code of living, the first day of detailed set things right (and later learned that there are detailed design test cases ), the code number for five days, two days later, has been writing his own script interface testing, functional testing make up the environment, not sparing even the UI test, test until the seventh day turn to me. Multiple Data submitted through seven stages, seven layers of the role of the audit, released last large flow of information, through a one-time smoke (most recent project is a set of all the development including project managers have asked me smoke test What do you mean, uh ~) no extra words three days test, a total of three rounds of testing capabilities, violence testing, security testing, made a total of 14 defects, tut ~, has been stable on the line. Finish this demand he resigned on the grounds that he understands that not around a person, not a friend. In fact it, is to get a big offer, know everything know everything, hey ~
The two met in life thanks to colleagues, friends and craftsmen.
Having a good, ah, let me talk about those right, alas ~ ~ Zaoxin
Over the past year, carrying more than 10 defects per day, brain supplement product demand, the development of various scenarios to teach the process to go their own to grab the interface analysis, to provide parameters to develop the scene and had to study a variety of safety scenarios, measure the number of low-level security issues, then the software functions after line, get deserted them, and every day the emergency repair. Can cause such a situation, of course, there is no stage to speak of the matter UT, design documentation is valid and something delicious it?
It is this trend, fast food, fast food oriented, no one wanted to spend time on themselves as some of the boring and useless things. UT will be in some level of myth, legend, and it is my level is too low.
Last idea: now that the UT developers practitioner not to do stage 8 which then {8: [2 = (2: 8)]} = 10, so that 10 to full voltage at test phase, the test phase only found the defect is 20 to 50 percent, and 5 to 8 as a flow production.
You can imagine, there is no strict UT development stage, a software release in theory (years of experience tells me that in fact need to be replaced) is there is a huge risk. Online users will pay to testers.
Developers will say: 'Yeah UT test can also be'?
Of course, this is right, there are test UT workers. However, workers are divided into test function, performance, automation, the UT (white box), security interfaces direction. Currently the industry, 90% are functional, automated testing practitioners. And most fast food is white. How can developers require testing UT common it?