Software testing, while one of the most important tasks to do in a development project is often misunderstood and mistreated by everyone from programmers and managers to testers.
Wikipedia calls evidence of "empirical research conducted to provide stakeholders with information on the quality of the product or service on the basis of evidence about the context in which it seeks to exploit."
This definition, like most who try to make the software into a science, is nonsense. The definition of the evidence that buys and tries to instill in others is that the test is done to find bugs in a piece of software before the user does.
When a project adheres to the empirical ideology that creates a host of problems. The first is that developers write sloppy code, and somehow feel that some testing is done by other tools used imperfect premium and fantasy to dissect their product and provide statistics to the men who create graphics to better inform said yes or whether the program works or not.
These are the kinds of developers who do not write unit tests because they think that somehow absolved of their responsibility to test in the way of throwing garbage in the street because they think it is the work of public servants to clean up after them.
"Hey buddy, I'm a developer, I write code, his work is proof of that, haw, haw.
When this division was created, with the fiefdom of managers creating happy tiger (ugh) teams "of the testers of the system begins the battle, the testers are pitted against developers arrogant and in your brand, Bang, the race is to find and report bugs.
Testers bang on the system from all angles, find the dialog boxes cannot change the size to be, which cannot be, and dark conditions in the mines in which the product works curiously, ending each day with a huge smile after raising the number of record against product defects.
Before knowing that there are defects gazillion made against a product that may not have anything wrong with it anyway.
The director who oversees the project, now the numbers show default graphics drawn with red lines showing a steady expansion of y-axis "Holy Gee, boy, project number, it appears that the project is in flames. Let's put water on it, stopping encoding functions, because we must correct flaws."
The Curse of the developers and shot because they have to fix alleged defects instead of writing the new feature, the testers to clap with joy to raise more false defects, e-mail wars arise about who controls the priority and severity, and the project entire generation was lost.
This is because the initial premise that empirical evidence is concerned. It is not, never was and never will be.
The first step is to make automated testing tools outside testers, but only consumed by way of a child was fascinated by the websites with the penguins or dogs that can talk to each other.
Tell your tester’s role is to find faults before users make, and tell them to talk with users and discard any that have envy of non-programmers.
Tell programmers should write unit tests that run as part of the build process and a test is not like a career not compile - the function is incomplete.
Finally, tell the administrators to reverse and stop using empirical sense to evaluate the health of your project and go to talk with users, listening to opinions, and maybe a little more and look over the edge of your cubicle. Its function is to facilitate, not to govern, and any free time they have between sending emails, booking meetings, or writing minutes, could be used to test products on your computer and is designed as a user and can help to find flaws and defects. In the process could even really know at what supposedly is in charge.
0 comments:
Post a Comment