Hi its the Social Media Girl for OPSPL. Well I hadn't posted anything in the OPSPL Diaries for sometime now. Maybe I wasn't inspired enough, but as I was going through a few random blogs I came across one that was called "The breed of Testers" by Minion. Hence thought of posting a Part 2 for the same. This time its from Online -- Goa. Enjoy :)
THE COMEDIAN
The Comedian regularly carries a cheerful approach to
testing. They are grinding away at work to do a good job, yet they are also here to have a touch of fun. The Comedian is an amusing sort of fella who
will always have a joke and a laugh even when every one else is worried about deadlines. In
the wake of pulling a 14 hour shift the Comedian is still in top form. I
mean joke wise at any rate. The Comedian frequently makes awesomely funny test data
and artifacts. The Comedian's defect reports, in spite of the fact that they
are fairly accurate, have been known to make designers cry with laughter. Now
and again however, the Comedian can seem to fail to offer the professionalism
and maturity to move through the testing ranks and be regarded with respect by
different departments. The Comedian's principle objective is to have a fabulous
time at work and make the working environment a fun place. Despite the reality that
they can sometimes be pretty annoying, particularly after the 100th practical joke
including elastic creepy crawlies and a camera, you can't deny their
methodology to work is very refreshing.
THE MAGICIAN
Very often called Forrest Gump as they generally have all
the earmarks of being in the right place at the right time. They try to test an
application that has already been tried vigorously and quickly discover a
masterpiece or a masterproblem. Each bit of programming they touch, they
discover a deformity in it almost immediately. Each tester sometime or another
has a short however otherworldly spell as the Magician yet a few testers have
the ability to do it at all time. Its only a problem when the Magician ill-uses
their powers through the following ways:
1. They get pompous and hold showing off sessions. This can
prompt hate and constant irritation.
2. They utilize their magician skills to cover up
coding defects and vanish all evidence of poor execution. The truth soon
comes out.
3. They transform their team into farm animals. Despite the
fact that its funny, it is frequently seen as misusing power.
4. Wearing preposterous magician outfits and pointy caps.
Neither man nor woman nor the farm animals likes extravagant dress. It's on
occasion like this when the Magician is stripped off of their energy and downgraded to
that of human tester.
A Magician is never late either. They arrive exactly when they intend to.
Furthermore in spite of the fact that most of us have to accept that we have minimal control over if we can turn into a magician or not there are a few steps all testers could be doing to take a shot at being the Magician. They are:
Furthermore in spite of the fact that most of us have to accept that we have minimal control over if we can turn into a magician or not there are a few steps all testers could be doing to take a shot at being the Magician. They are:
1. Read everything you can about the subject
2. Have an yearning to study
3. Practice, practice, practice And assuming that you go
about doing this, then one day perhaps you too could turn into a magician.
THE NITPICKER
The Nitpicker takes more time to test than generally most
testers, they are known to raise a tremendous amount of imperfections of which
just 1% are certified bugs. The Nitpicker raises hell for everything that isn't
archived, regardless of the fact that it works and makes sense. They utilize
the medium of defects to make conversations with whatever is left of the team.
They frequently raise numerous examples of one bug, regularly with the sole
point of raising their bug count. They sit down to test, cross reference each
bit of documentation and make flawlessly definite bug reports. On the plus side,
they are amazingly careful. The Nitpicker is not responsive to change however.
The Nitpicker needs everything to be recorded and each change to be carefully
written down. Any discussion that happens needs a signed paper follow up of all
agreed details. Change controls unnerve the Nitpicker. Missing documentation is
a Nitpickers most certified bad dream. The Nitpicker regularly invests a great
deal of time handling cross reference reports and networks that on the surface
appear functional yet wind up using more time and money. The Nitpicker accepts
a standard set of metrics ought to be applied to all test projects. The
Nitpicker adores Best Practices. Frequently the Nitpicker keeps tabs on the
things that don't make a difference and constantly frets until the farm animals
get back. Working with a Nitpicker is a test. They require a consistent flow of
documentation as well as frequently decline to begin work until the
documentation is triplicated under the false conviction that testing can't
begin until a agreed date. They require quietness, time and paperwork and this
frequently is just too much for the rest of the testers to handle.
