0:01 hey guys welcome to the testing academy
0:03 my name is pramod and in this video we
0:05 are going to learn about the 12 ways
0:07 software testers think differently from
0:10 others all right so let's get started [Music]
0:14 [Music]
0:16 first of all guys this videos especially
0:17 for the people who are qa fresher
0:20 because you have to think uh different
0:22 okay if you want to become a great
0:24 software tester then you have to think
0:25 different and even if you have
0:27 experience i would suggest you to have a
0:29 look around this uh 12 tips that i am
0:32 basically presenting you in front of you
0:35 which has basically helped me a lot uh
0:38 to basically become a good i would say
0:40 to software tester all right so let's go
0:41 one by one
0:43 first of all right the first one the
0:46 first tip is guys uh allah is basically
0:49 every ability to listen okay so what
0:52 exactly it means so suppose uh you are
0:54 into a
0:57 meeting okay and here in the in that
1:00 meeting you are with uh stakeholders or
1:03 ui ux designers or product managers they
1:05 are giving you some of the requirements
1:07 okay these are the requirements these uh
1:09 so developer will make it and this is
1:10 how you have to test it so this is the
1:13 product there so what i have seen is if
1:16 you are good at listening then
1:19 almost 70 percent of the time you will
1:21 able to catch bugs because you are able
1:24 to understand what exactly they are
1:26 saying and you will able to understand
1:28 the requirement and you will be able to
1:30 correctly map that requirement to the
1:32 test cases so that's really really
1:35 important for you guys to listen
1:38 so i would suggest don't if you have any
1:40 doubt or anything or a concern note it
1:43 down somewhere in your notepad but don't
1:45 ask immediately because whenever you ask
1:48 immediately sometimes uh you basically
1:51 uh are not able to listen properly but i
1:53 have seen so you can what you can do is
1:55 listen them clearly and then ask the
1:59 question and always i would suggest 70
2:01 percent of the time you should listen to
2:03 the requirement because they are clear
2:04 of because they have made this
2:06 requirement right and you can always
2:08 cross check and when you have listened
2:10 enough then definitely you can basically
2:13 give them a proper counter argument okay
2:14 so this is really important guys pay
2:17 attention to listening okay uh
2:18 yeah make sure you watch this video at
2:21 1.5 x for better viewing purpose okay so
2:22 let's move on to the tip number two
2:25 which is basically don't assume this is
2:27 a really really bad thing that i have
2:29 speed especially related to the freshers
2:32 as well as uh any experience qa okay so
2:34 i have told you this example many times
2:37 so uh when i was testing e-commerce
2:39 website in one of the project okay and
2:42 uh there we assume that this button was
2:44 okay i mean it was
2:46 because of the requirement but we have
2:48 assumed right this is the probably the
2:51 worst thing a software tester can do
2:52 don't assume anything if you have a
2:54 doubt you can raise a concern to the
2:56 stakeholder or a pm that okay i don't
2:58 know what is it please let me know this
3:00 is the correct way don't assume anything
3:04 and that that bug that that button right
3:07 uh basically uh due to that button we
3:08 had some revenue losses also because
3:11 that was not working and people were not
3:12 uh people were thinking that this
3:14 website is not credible because the
3:16 button is not working right so pay
3:17 attention to that
3:19 tip number two is basically
3:22 i have told you many time please have a
3:25 learning attitude okay even right now
3:28 i'm taking courses okay so i have uh i
3:30 generally take courses related to how to
3:33 improve uh scalability reliability
3:35 docker and other things right so
3:38 even with 10 years of experience still i
3:40 am taking the courses to learn something
3:42 new so make sure you don't stop your
3:44 learning if you're a manual tester go
3:46 with the automation if your apa tester
3:49 go with the advanced api testing uh do
3:51 it with frameworks and other things okay
3:53 so make sure you do that
3:54 all right
3:55 tip number four
3:57 let me know guys if you are if these
3:59 tips are helping for you i know it's a
4:01 little theoretical concept but this
4:04 thing uh will help you a lot and this
4:06 whatever i'm
4:07 basically discussing with you right
4:09 nobody is right now on the market
4:12 discussing this and you will learn after
4:16 certain period but uh by making your
4:18 mistakes so i am giving you those tips
4:21 with my mistakes so it's always
4:23 it's basically i mean many wise people
4:25 say that right learn from other mistakes
4:27 so these are my mistakes and these are
4:29 the tips that i'm giving you
4:31 uh tip number five uh tip number four is
4:34 basically always ask why why and how
4:36 basically what you are doing why we are
4:37 doing this you can ask the state
4:39 question with these stakeholders ui
4:41 designers and pm why we are doing things
4:42 why we are basically creating this
4:44 feature because when you are clear with
4:47 the why you are basically no you are
4:49 basically working as a user and quality
4:52 assurance or a qa is nothing but a user
4:54 who is using the app extensively that's
4:56 it okay you will get more clarity over
4:58 the topic so that's why where it is
4:59 really important okay
5:01 so tip number five let's move on to tip
5:04 number five which is logics uh you have
5:06 to basically think about extremely
5:08 logical i'll give you one scenario okay
5:10 so for example somebody has given you a
5:12 login page and they basically told you
5:14 to give them a test cases generally what
5:16 i have seen is ninety percent of people
5:18 tell me give you that okay i'll go with
5:20 the invalid cases i will go the valid
5:22 cases and that's it but what about the
5:24 cases where there's no internet
5:26 what happens if there is an api request
5:28 fails what happens if there's a wrong
5:30 headers are coming what happens if
5:32 submit button uh is giving you some
5:35 error or it's not working in some browse
5:36 different browsers right so those things
5:38 you need to take care this is actually
5:40 called as critical thinking or a logical
5:42 thinking so you have to improve it and
5:44 how you will improve it i would suggest
5:47 you to do some sudoku right where your
5:50 mind is basically working a lot okay so
5:52 these activities generally help and for
5:55 me uh mostly playing games also helps
5:57 okay so this is another thing all right
5:59 let's move on to the tip number six guys
6:01 basically uh you can use uh this
6:02 technique which is called as risk of
6:06 failure always ask your stakeholder pm
6:08 whoever or a developer what happens if
6:10 this is failing if it doesn't work what
6:12 will happen so you will know what is the
6:14 end case for this i mean nothing is
6:16 worth not working what will happen to
6:19 this right so you by using this
6:21 technique you will be able to find more
6:24 important test cases which may uh which
6:26 probably you are going to miss so make
6:28 sure you that uh tip number five is
6:30 basically think like this that you have
6:32 to break the
6:34 functionality okay whenever you think
6:37 about these uh what will happen is uh
6:40 think about as a user perspective how i
6:42 can break this scenario for example
6:44 suppose i'm working in a managed banking
6:46 management and i'm transferring some
6:48 money right but if i spa
6:50 what if i have spent all my money then
6:52 i'm transferring all these breaking
6:54 changes or breaking test cases you have
6:55 to keep on doing it okay i know it's a
6:57 little theoretical but trust me it will
6:59 help you a lot all right let's move on
7:00 to the tip number nine which is
7:03 basically observe people observe the
7:05 developer observe their prs observe
7:07 their logical thinkings so one of the
7:09 technique which has helped me a lot is
7:11 basically observing the pull request or
7:14 a code written by developers basically i
7:17 i basically generally what i do is uh
7:19 uh
7:21 i'll get the pr from the developers i
7:23 grow i'll just go through it all of them
7:25 and i'll see what are the logic they
7:27 have applied and what where it can go
7:28 wrong and there i have prepared my test
7:31 cases and trust me that i have found
7:33 many many important bugs due to that so
7:36 make sure you try uh give it a try also
7:38 this okay so tip number 10 is basically
7:40 they break down everything so yes a
7:42 great software tester they break down
7:44 everything they basically go multiply
7:45 modules and prepare the test cases and
7:49 do that okay tip number 11 is document
7:50 everything guys
7:53 in startup in mnc people will say you
7:54 don't create the test plan don't create
7:56 test strategies don't create test cases
7:58 no there's no requirement but whenever
7:59 there is a work people will ask you this
8:02 document so make sure you are creating
8:04 test plan test cases and bug report all
8:06 the videos are available this mind web
8:08 is also available in the description you
8:10 can download it and watch this video two
8:12 videos of how why it is mandatory to
8:14 create it as plan and how to write an
8:16 effective burg report which is a really
8:18 important skill for a software tester
8:21 okay even as a pressure tip 11 tip 12
8:23 which is a bonus for you is basically i
8:25 think this is a repetitive but you got
8:26 the point right they break down
8:28 everything in breakdown everything i'll
8:30 just add one one more line what you mean
8:32 by breakdown everything is you whenever
8:34 you have requirements right make sure
8:36 with one requirement you create certain
8:38 number of test cases and attach them
8:39 okay so that you will have a proper
8:41 mapping of which requirement i have
8:43 covered how many number of test cases
8:45 and this will help you to present to
8:47 stakeholders as well as pm all right so
8:50 i hope this tips will help you a lot and
8:53 uh these are my 12 ways to software
8:55 testing thing differently thanks a lot
8:57 for watching and please make sure guys
8:59 please subscribe to the video uh so that
9:01 i can create lots of awesome videos like
