This content outlines twelve distinct ways software testers should think differently to excel in their role, emphasizing critical thinking, thoroughness, and continuous learning for both freshers and experienced professionals.
Mind Map
Click to expand
Click to explore the full interactive mind map • Zoom, pan, and navigate
hey guys welcome to the testing academy
my name is pramod and in this video we
are going to learn about the 12 ways
software testers think differently from
others all right so let's get started [Music]
[Music]
first of all guys this videos especially
for the people who are qa fresher
because you have to think uh different
okay if you want to become a great
software tester then you have to think
different and even if you have
experience i would suggest you to have a
look around this uh 12 tips that i am
basically presenting you in front of you
which has basically helped me a lot uh
to basically become a good i would say
to software tester all right so let's go
one by one
first of all right the first one the
first tip is guys uh allah is basically
every ability to listen okay so what
exactly it means so suppose uh you are
into a
meeting okay and here in the in that
meeting you are with uh stakeholders or
ui ux designers or product managers they
are giving you some of the requirements
okay these are the requirements these uh
so developer will make it and this is
how you have to test it so this is the
product there so what i have seen is if
you are good at listening then
almost 70 percent of the time you will
able to catch bugs because you are able
to understand what exactly they are
saying and you will able to understand
the requirement and you will be able to
correctly map that requirement to the
test cases so that's really really
important for you guys to listen
so i would suggest don't if you have any
doubt or anything or a concern note it
down somewhere in your notepad but don't
ask immediately because whenever you ask
immediately sometimes uh you basically
uh are not able to listen properly but i
have seen so you can what you can do is
listen them clearly and then ask the
question and always i would suggest 70
percent of the time you should listen to
the requirement because they are clear
of because they have made this
requirement right and you can always
cross check and when you have listened
enough then definitely you can basically
give them a proper counter argument okay
so this is really important guys pay
attention to listening okay uh
yeah make sure you watch this video at
1.5 x for better viewing purpose okay so
let's move on to the tip number two
which is basically don't assume this is
a really really bad thing that i have
speed especially related to the freshers
as well as uh any experience qa okay so
i have told you this example many times
so uh when i was testing e-commerce
website in one of the project okay and
uh there we assume that this button was
okay i mean it was
because of the requirement but we have
assumed right this is the probably the
worst thing a software tester can do
don't assume anything if you have a
doubt you can raise a concern to the
stakeholder or a pm that okay i don't
know what is it please let me know this
is the correct way don't assume anything
and that that bug that that button right
uh basically uh due to that button we
had some revenue losses also because
that was not working and people were not
uh people were thinking that this
website is not credible because the
button is not working right so pay
attention to that
tip number two is basically
i have told you many time please have a
learning attitude okay even right now
i'm taking courses okay so i have uh i
generally take courses related to how to
improve uh scalability reliability
docker and other things right so
even with 10 years of experience still i
am taking the courses to learn something
new so make sure you don't stop your
learning if you're a manual tester go
with the automation if your apa tester
go with the advanced api testing uh do
it with frameworks and other things okay
so make sure you do that
all right
tip number four
let me know guys if you are if these
tips are helping for you i know it's a
little theoretical concept but this
thing uh will help you a lot and this
whatever i'm
basically discussing with you right
nobody is right now on the market
discussing this and you will learn after
certain period but uh by making your
mistakes so i am giving you those tips
with my mistakes so it's always
it's basically i mean many wise people
say that right learn from other mistakes
so these are my mistakes and these are
the tips that i'm giving you
uh tip number five uh tip number four is
basically always ask why why and how
basically what you are doing why we are
doing this you can ask the state
question with these stakeholders ui
designers and pm why we are doing things
why we are basically creating this
feature because when you are clear with
the why you are basically no you are
basically working as a user and quality
assurance or a qa is nothing but a user
who is using the app extensively that's
it okay you will get more clarity over
the topic so that's why where it is
really important okay
so tip number five let's move on to tip
number five which is logics uh you have
to basically think about extremely
logical i'll give you one scenario okay
so for example somebody has given you a
login page and they basically told you
to give them a test cases generally what
i have seen is ninety percent of people
tell me give you that okay i'll go with
the invalid cases i will go the valid
cases and that's it but what about the
cases where there's no internet
what happens if there is an api request
fails what happens if there's a wrong
headers are coming what happens if
submit button uh is giving you some
error or it's not working in some browse
different browsers right so those things
you need to take care this is actually
called as critical thinking or a logical
thinking so you have to improve it and
how you will improve it i would suggest
you to do some sudoku right where your
mind is basically working a lot okay so
these activities generally help and for
me uh mostly playing games also helps
okay so this is another thing all right
let's move on to the tip number six guys
basically uh you can use uh this
technique which is called as risk of
failure always ask your stakeholder pm
whoever or a developer what happens if
this is failing if it doesn't work what
will happen so you will know what is the
end case for this i mean nothing is
worth not working what will happen to
this right so you by using this
technique you will be able to find more
important test cases which may uh which
probably you are going to miss so make
sure you that uh tip number five is
basically think like this that you have
to break the
functionality okay whenever you think
about these uh what will happen is uh
think about as a user perspective how i
can break this scenario for example
suppose i'm working in a managed banking
management and i'm transferring some
money right but if i spa
what if i have spent all my money then
i'm transferring all these breaking
changes or breaking test cases you have
to keep on doing it okay i know it's a
little theoretical but trust me it will
help you a lot all right let's move on
to the tip number nine which is
basically observe people observe the
developer observe their prs observe
their logical thinkings so one of the
technique which has helped me a lot is
basically observing the pull request or
a code written by developers basically i
i basically generally what i do is uh
uh
i'll get the pr from the developers i
grow i'll just go through it all of them
and i'll see what are the logic they
have applied and what where it can go
wrong and there i have prepared my test
cases and trust me that i have found
many many important bugs due to that so
make sure you try uh give it a try also
this okay so tip number 10 is basically
they break down everything so yes a
great software tester they break down
everything they basically go multiply
modules and prepare the test cases and
do that okay tip number 11 is document
everything guys
in startup in mnc people will say you
don't create the test plan don't create
test strategies don't create test cases
no there's no requirement but whenever
there is a work people will ask you this
document so make sure you are creating
test plan test cases and bug report all
the videos are available this mind web
is also available in the description you
can download it and watch this video two
videos of how why it is mandatory to
create it as plan and how to write an
effective burg report which is a really
important skill for a software tester
okay even as a pressure tip 11 tip 12
which is a bonus for you is basically i
think this is a repetitive but you got
the point right they break down
everything in breakdown everything i'll
just add one one more line what you mean
by breakdown everything is you whenever
you have requirements right make sure
with one requirement you create certain
number of test cases and attach them
okay so that you will have a proper
mapping of which requirement i have
covered how many number of test cases
and this will help you to present to
stakeholders as well as pm all right so
i hope this tips will help you a lot and
uh these are my 12 ways to software
testing thing differently thanks a lot
for watching and please make sure guys
please subscribe to the video uh so that
i can create lots of awesome videos like
Click on any text or timestamp to jump to that moment in the video
Share:
Most transcripts ready in under 5 seconds
One-Click Copy125+ LanguagesSearch ContentJump to Timestamps
Paste YouTube URL
Enter any YouTube video link to get the full transcript
Transcript Extraction Form
Most transcripts ready in under 5 seconds
Get Our Chrome Extension
Get transcripts instantly without leaving YouTube. Install our Chrome extension for one-click access to any video's transcript directly on the watch page.
