Comparison of Change Management Systems

that errors occur because of testers. Even
questions like this may appear: "When
testers will stop to find bugs?!". Of course,
the defects do not arise because of the
testers. Precisely the contrary, testing
helps to improve the quality of software,
but some people forget this, and begin to
utter unpleasant words to tester, to write
angry emails, reject defects, etc.
Now let’s try to look at this situation
from the other side. Most testers feel
themselves just inferior people in the
team. Wages of programmers usually
higher. If the software works well, the
developers receive the award, because
it is implemented. And if a product works
poorly, the blame can be at testers,
because they had inspected or tested not
enough well.
Add to this discontented programmers
who constantly reject defects, provide
functionality at the last moment, and there
is no enough time for full inspection, the
desire to remain true to profession of a
tester is approaching to zero.
But software development process
requires both developers and testers,
and it is important that they have good
working relations. To do this, of course,
some efforts should be made.
Testers, to live peacefully with
the programmers, need to learn
understanding, and seek an individual
approach. But besides this, tester must
have a certain set of qualities to be
respected by colleagues:
• Attention, because problem can arise
not only due to the fact that the code has
errors inside, but because tester does
something incorrectly.
• Observation, as it is necessary to notice
the slightest flaws in the program.
• Pedantry, as it is necessary to conduct
any test carefully and not once.
• Assiduity, as it is necessary to find
a mistake, try to discover its cause,
describe, and then double-check.
• Tact, as indication of the error must be as
gently as possible, specify only the facts
and not give any personal assessment.
• Persistence, as it is often necessary
to defend the rightness, to prove the
existence of the defect (but "not to bend
the stick" is important, too).
• Creative thinking that would come up
with new tests.
• Communication skills, because of the
need to collaborate within the testing
team, in addition to communicate with the
developers, authorities, and sometimes
directly with customers.
• Desire to learn, because you need to know
as much as possible about the product,
the technology of its development, as well
as to explore new means of testing.
Also the search for faults in the system
requires curiosity, professional pessimism
and experience which is based on an
intuitive search for errors.
As a testing professionals we can
give a few tips to all testers, especially
youngest:
• Note that you and developer perceive
the software in various ways: programmer
usually focuses on a specific module
(functions, parts), but you can imagine
the entire system (as interacting
components).
• Your attitude should be critical, in order
to find as many mistakes as possible.
• Describing defects, try to gently, step by
step explain how to reproduce the bug
(if bug is not reproduced regularly, make
sure you mentioned it).
• Insist on providing you with all possible
documentation, as this will increase the
efficiency of your work.
• Do not think of yourself as of worse or
better than other team members.
• Work with great responsibility.
• Do not demand too much, i.e. if you do
not have computer of the last generation,
then work with what you have, but keep
in mind the possible problems when
planning the test.
• Focus on the software product, rather
than the individual programmer, manager,
analytics, etc.
• Do not forget that developers are
person with their advantages and
disadvantages.
• Remember that developer usually is
committed to create a software that
works in general. Incorrect operation of
small functions, misspelling, etc. for him
is not errors. In this case, try calmly and
convincingly prove that it is still lack and
developer needs to fix it.
But not only the tester must exert efforts
and establish normal relations with
developers. For developers it is desirable
to keep in mind the following facts:
• The task of a tester is to find a mistake,
testers think critically. But it does not mean
to hurt you, it's the characteristic that is
essential for creating quality software
product.
• Labor of tester is complicated too, it
is intellectual activity, which deserves
respect. Tester wants the project to be
successful, and not trying to point out your
Software Testing
shortcomings. Tester is trying to address
the problem from the point of view of the
user.
• Before giving tasks and modules for
testing, you should check them yourself,
at least superficially - it will shorten the
development time of the product as a
whole. You will demonstrate yourself as
a competent specialist, and possibly your
relationship with testers will improve.
• For the success of the team, it is
preferable in a timely manner to correct
defects and to put them into the database
with relevant information. Errors may
block other functional verification, as well
as correcting some defects may lead to
others.
• If troubles, ridicule, accusations, etc., are
expected for error reports, then people
may not notice errors or do not make
record on them (if the report is wrong, just
tell testers how best to execute it, and not
scold them).
• Tester sometimes can make mistakes,
like all people. Do not judge them for it
too seriously.
In relations between testers and
developers, there is another person who
controls the entire process - manager.
Managers must do their best too to avoid
conflicts within the team.
Hope that these recommendations will
be helpful. Above all, love your work and
colleagues, and remember that you are a
team member working on a common goal
– qualitative successful project.
1. ISTQB Standard glossary of terms
used in Software Testing.
2. ISTQB Certified Tester. Foundation
Level Syllabus.
3. Software Test [2009], http://s-test.
narod.ru/Testing/tester.htm
4. About developers [2009], http://
babruisk.com/uncategorized/proprogrammistov/12434
5. How tester must interact with developer?
What are their relations? [2009], http://
content.mail.ru/arch/27675/2270268.html
6. Software tester in search of defects
[2009], http://work.com.ua/articles/
subject/295/
7. Work of tester – grey working days
[2009], http://www.it4business.ru/lib/183/
8. Who is tester [2009], http://www.
software-testing.ru/library/around-testing/
job/85-who-is-tester
9. Veltsman Oleg, Litovchenko Evgenia,
“Constantly indicating mistakes to
colleagues, testers make enemies”
[2009], http://www.europa-personal.ru/
profesii225.htm
73