Tester’s

common
mistakes in
software
testing
IVAN GEORGE
MOLNAR BIANCA CRISTINA
LEȘOVSCHI ALEXANDRA
 Agenda
Introduction
1. Lack of communication
2. Lack of proper planning
3. Criticising developers
4. Try to fix the bug yourself
5. Using the same test data - pesticide paradox
6. Neglecting paperwork
7. Stop learning
8. Be afraid of asking questions
9. Not thinking as the end user
Conclusion
Bibliography
Introduction
Testing errors are different from errors
that occur during development and
user handling. These are errors that
occur during the software testing life
cycle. Mainly errors that occur during
test planning, execution,
documentation, and reporting are
known as testing errors.
1. Lack of communication
One of the most important skill a Tester should
posses is the ability to communicate effectively.
It is important to communicate not only to gather
information but also to analyze possible issues
and their solutions.
Testers must communicate regularly with
developers, project managers, and business
analysts, to ensure that everyone is aligned on
the testing objectives and progress.
If a tester isn’t aware of this, they’ll be in
trouble pretty quick.
 2. Lack of proper planning
The most common error made by testers is a
lack of proper planning.

Everything is near-perfect, if not perfect when

everything is planned.

Unplanned testing creates the fear of a fraudulent application,

which occurs in 99 percent of real-world scenarios..

As a result, testers must design their testing

strategy from the scratch.
 3. Criticising developers
A constructive way of giving feedback and a positive
communication can make the difference in a tester-developer
relation.

Try to spot also the good work a developer is doing, not only the
bugs or problems found in his/her code.

Add positivity into your testing !!!

 4. Try to fix the bug yourself
le of Don’t m
l ru k. islead t
n ta or he deve
am e rs w loper b
u nd o pe wrong y giving
f e l assump him
a nd dev tions.
a sic the
ab d o
is y to
This on ’t tr
: d
sting
te

f the As a te
e s o ster yo
ca us it u need
o ot xin g exact to be
e r d fi inform precis
d th an ation t e and
fin in g o the d give
b to ugg evelop
is jo eb ers.
It’s h byd
b lem
pro
5. Using the same
test data -
Pesticide Paradox
Executing our testing scenarios using the
same test date might lead us to the
pesticide paradox. Repeating over and over
the same test cases with the same test data
will no longer find new bugs.
6. Neglecting Paperwork
Writing test case specifications, plans, scenarios, analysis,
reports, and updating information in existing documents is
undoubtedly a tedious task. But it has to be done.
At some point you’ll be tempted to speed up these
processes by skipping a section or two. But it will
inevitably lead to chaos. Detailed and up-to-date
documentation is compulsory for an efficient QA process.
 7. Stop learning
Software testing is an ever-growing and fast-
changing field, and every single day you will face
new challenges at work. As a QA professional, you
have to learn new things and improve your skills
continuously. Being closed off to learning will not
help you at work.
8. Be afraid of asking
questions
Sometimes new testers don’t want to pester their
colleagues with too many questions, so they try
and find solutions to problems on their own. While
this is great and it improves problem solving skills,
it’s not always a good option.
A good rule of thumb is, if you cannot find an
answer to the problem within half an hour, look
for help. It’s perfectly acceptable to ask
questions!
 9. Not thinking as
the end-user
Testing the application from the user's
perspective is crucial for delivering a seamless
user experience. Not testing the application from
the user's perspective can result in missing critical
issues that can impact the user's experience.
Testers should ensure that the application is
tested for usability, accessibility, and user
experience.
 Conclusion
As a tester, avoiding these common mistakes can improve the
effectiveness of the testing process and ensure that the application
meets the desired quality standard. By defining clear test objectives,
testing the application from the user’s perspective, collaborating with
development team and documenting test results, you can deliver quality
software.
 Bibliography
1. https://www.tricentis.com/blog/10-common-mistakes-testers-make

2. https://medium.com/testing-land/14-most-common-mistakes-a-tester-makes-bce72ff95228

3. https://brainhub.eu/library/software-testers-mistakes

4. https://www.globalapptesting.com/blog/5-critical-mistakes-to-avoid-in-your-qa-testing-process

5. https://www.linkedin.com/pulse/testing-mistakes-avoid-what-do-tester-sumit-bansal/

6. https://www.careerist.com/insights/10-mistakes-every-new-qa-tester-will-make-and-how-to-avoid-them

7. https://sapizon.com/blog/some-common-mistakes-a-tester-makes/
THANK
YOU