So today we're going to focus on testing Basics uh so that would be you know what is testing and what is software testing and also we're going to look into you know certain tools that are used in testing uh and the documentations that are used in testing and so on so tomorrow they too will be dedicated for defects defects they they have their own life cycle and and so on uh day three SQL then we'll do python you'll you know you'll learn how to create your own scripts in Python and day5 will be uh dedicated for test automation so let's just uh jump into the uh main content audience today uh is uh very diverse uh I have to uh tell you so majority of the attendees are new to QA uh but we have also uh attendees who are already studying QA and attending boot camps or self-studying some of them are already in the market actively looking for job and for those good luck and if those five days of lessons in any way will help you uh um along the way in that Journey uh please share that story and we're going to be very happy uh to hear that so uh we also have few uh professionals uh senior you know QA professionals uh in the audience and you know we welcome them as well everybody's welcome we'll try to make the whole uh uh classes each class as as useful as beneficial to every group uh as possible so uh questions please put it in the chat box and I'll try to answer uh every each of them uh at the end uh we'll try to keep it interactive as well uh and I'll also share my contact so that you can reach out to me if you guys have any any questions or any uh feedback uh will be needed so I want to start from uh the bigger picture uh here so this this particular slide is dedicated for those who are completely new to information Technologies who are trying to make their decision to change their career but they're not sure or they're looking for a motivation basically uh so um I'll ask the audience this question so imagine if you had a job offer today two different job offers with all the other parameters same but one is working from home and the other one is working from the office right and I'm not guessing but I know for sure that majority will be choosing working from home because this is the new normal uh especially after uh pandemic you know pandemic uh came harsh but it also also taught the companies that people can actually work from home especially the information technology uh professionals they can still do their job uh staying home and working from home uh and if you're out there looking for job chances are that you're either going to get 100% remote uh job opportunity or hybrid couple of days home and couple of days in the office grateful work life balance uh so um so this is one of the short term sort of uh benefits that you can get right away if if you will be uh in the market when you reach that point um so that's a great uh you know factor to take into account uh certainly but apart from that there's another um important factor that I get uh questions about that is is there an opportunity to grow can I actually grow or am I going to be working as as a tester you know for the next 10 years so and my answer is that there's tons of room for growth for anyone who's willing to you know work hard um and work consistently uh towards uh their goals um when I uh started working for us companies I was surprised to see the you know different positions variety different positions that you have at VP level vice president levels you have like assistant vice president you have vice president first vice president and Senior vice president Executive Vice President and all those uh you know variety uh of VP levels are are achievable and and and of course you know that's something that you have to uh wish for and you have to work towards right you have to put that goal and then you have to work hard uh towards the goal and that's achievable I'm telling you and and then salaries uh in at be level that start from 150,000 a year and about in the United States so um so I think those uh two factors are uh uh you know one of the big uh uh factors that that taken into account when making a decision to jump into the IT career but apart from that there are many other benefits uh that uh that you can also think of for example uh paid vacations right who doesn't want to go a vacation and then come back and and then and then still get the same salary so that's that's a great uh thing that you can take into account and also there's uh health insurance benefits and also 401K that that would be you know your retirement plan whenever you put a dollar and then the company puts uh you know another 50 Cent or 30 cents additional to what you're uh keeping uh or you know putting as a secure fund for your retirement that's something that I do I mean you know you can certainly consult that with your accountant and uh there is an arguable discussion about whether retirement plans are good or or or bad and maybe I'll talk about it in in some other uh session some other day but I personally use that sorry so uh those are the benefits of the uh it uh career and I um I think you know you should take that into account whenever you're um uh thinking or evaluating different factors trying to make a decision so let's answer the uh try to answer the next important question here um that everybody has and how difficult it is or how easy it is right now I want every one of you just to think of any big achievement that you had in your life uh it it can be in education like bachelor's degree for example that's a great achievement and or maybe at work you got a promotion and that's a good achievement and um I'm sure it wasn't easy I'm pretty sure it was not easy you had to go through a certain uh steps uh for example you had to you know put you know have a vision or or a dream and you have to follow your dream uh and you have to set certain goals and uh you had to work hard right so um well guess what the same approach same recipe would work here as well because you were trying to change your career you were trying to replace other candidate who worked maybe for uh for years trying to get a bachelor's degree in it uh and then you were trying to compete with the with that uh other candidate and certainly that requires that determination and um and this approach that you actually used in the past to achieve other achievements in your life so um but there are uh two more important ingredients that I think that has to be mentioned here that makes this formula or the approach complete that would be first one would be um uh consistency right without consistency you will uh not be able to uh complete uh or you know you worked a couple of hours uh day one and then and then you skipped uh your lessons for the rest of the weekend that's uh certainly not consistency and um and the other uh important factor here is sacrifice so I'm certainly uh you know not talking about any religious sacrifice or anything but I'm talking about time management here right sacrifice so um so you have only 24 hours a day and um I'm sure you've been so busy and if you're trying to get into a new field you need some extra time um to to study and and when I say sacrifice I mean those little things that eat up your time like maybe you should turn off or deactivate your subscription for Netflix for a period of time uh or maybe stay off the social network for a period of time like you know stop watching those Instagram reals and you know watching the random people doing weird stuff so you're going to get back to the Instagram or a social network at some point that may and then make that big announcement hey I started working for this big company or doesn't have to be a big brand or anything so but still uh you know any you know achieving goal requires consistency uh and discipline uh so this is you know to make sure that we have this correct expectations and correct mindset right from the beginning right so um so it's this is really important uh to mention now another frequently Asked question that I get a lot and I I saw that question also in uh one of the Facebook groups as well um is is certific ation required or is a license required so if you were planning to become a doctor or uh or um or let's say a lawyer then yes right but if you're going to uh into into it field no you don't need to have a certificate uh but there's but right so let's take a look into uh those two job positions that I got recently so this is a senior Q aut position I I captured the screenshot last week I think and and this uh position might still be hot so if those who are looking for you know job opportunities you can still check that on dice.com so if you look here I highlighted and it says istqb F Foundation level uh certification require not required desirable but not required so so it's desirable they're still listing that as part of their job description here's another one that's more of a manual testing position and as you can see they also you know they're also listing that as as preferred right so the answer to this question is desirable but certainly not required right so if you ask me I say if you're not in rush if you're not like you know going to the market and you need to get the job right now if you're not in Rush then why not you know if you can do it istqb certifications or any other certification uh but International recognized ones though right so everybody provides certifications but I'm you know I'm really talking about the ones that are internationally recognized like iqb so uh and they teach um a lot as well I mean just to go through just to get the certificate you have to study a lot uh independently you can do that independently or get a coach and um and when you get that certificate you you know when you pass that exam it's I would say it's not easy as well your level of knowledge in QA is is in a different level basically you're you're going to feel that some it may not be as practical as as a as boot camps give you right like like ours so it's not as practical but it's just going to prepare you for the future or and also it's certainly going to increase your chances of uh of uh passing through those filters of like recruitment filters so what happens to your resume is that you know it goes through those recruiters right and and it has to end up in the screen these days not the desk right in the screen of of the QA manager or hiring manager and they don't have all day right so they you know they for example I myself I get 1015 uh resumes and and I I really have to select I have to short list and there's no other way because you know you can't be spending all your day interviewing people because you know you have other tasks as well and you really hope believe me those managers uh and the you know recruiters really hope that those candidates end up being good they they end up being as good as described in their uh in their resumes uh so that you know they're also off the hook they the job is done okay hiring process done I mean hiring process so exhausting and and they really hope uh that they get the right candidate as soon as possible so again desirable but not required does it increase your chance of getting through those filters and getting you know being shortlisted yes and um so but certainly not required all right so now that we clarified some of the uh basic or frequently asked questions we have the correct mindset right we know what to expect we know that it's not easy and but you still have to work for it right and um we can answer the question of what is testing right we can jump into the main topic of this whole uh uh a lesson so what is testing and how do you test if you can answer those two questions you know half the job is done you're almost a tester uh so um what is testing this is a very very simple simplified definition I'm putting here testing is checking how well a product works and I'm sure all of you have done this before right you have checked how well a product works and you know you were in a supermarket maybe in a Walmart buying some product and you were touching feeling and you're using it a little bit maybe and what exactly was going through your mind what kind of you know sequence of events or thoughts or algorithms were going uh through your mind at that point you were comparing right what were you comparing you were comparing your expectations versus the reality and that's how you perform testing right this is what testing is about and there are two important very uh very important Concepts that I want you to keep in mind which is expectations versus reality and there's different way of saying it in actual software testing but we'll get to that uh so now think of the uh return period you get from Amazon why do you think is that now what what exactly you were doing during that return period you were testing right you you took that product you're testing and then you're comparing your expectation and then with against the reality and if that if that worked if that matched then they were like okay this is this is good I'm keeping it if it didn't match then what you're doing is you know you're GNA write this bad review and you're going to return right give this three stars um so this is how you actually were performing the testing now let's look into this fun interesting example here in um in mid 1990s there was this uh you know famous commercial about a mattress and a glass of wine and this went viral and and um the the the product the the material that they were using is called temper and it was originally created by NASA to protect the astronauts during space travel and what is specific about this material is that it reduces the motion transfer right transfer of motion is reduced and this couple here this is not the actual commercial but this couple here is testing right this is this is what they're doing they're they saw this commercial commercial is their expectation and they're doing similar actions they're putting this wine you know the glass of wine in the in one corner of the mattress and then they're jumping in the on the other the other corner so how else could you test that product for example this guy decided that he can you know hit it with a hammer and several times so so here's a question to the audience um how would you test so imagine you're working for this company who makes the mattresses and how would you actually test how you know if you can you come up with some other ways of actually testing the same scenario so you can put your answers into the chat box and we call those different scenarios as test cases so I'll give you guys some couple of minutes so that so that you guys can type [Music] in all right any any suggestions all right I see some answers here use this for some times right use the product for some time Jump great okay that's that's great yes and you can also do exactly two people together you can also do a backflip that's right you can do a backflip and you can put bunch of kids and then they can jump on it right um throw some stuff yes so um and uh what else yeah you can use two glasses uh of wine you can put one glass of wine on top of the other one and you can roll over um yeah you can do all those stuffs and those are all um different put a bear yes it you see uh so what we call that in actual testing uh uh terminology is stress testing now uh you know do what you're doing for a period of time or increase the pressure on the product to find that breaking point right I'm sure the testers uh off that company they know the breaking point they know how close if you jump Too Close probably to that uh to the glass of wi it's going to spill so you know find that Breaking Point so um so let's so now that we kind of clarified what what is testing so let's move on to software testing right so um you have been doing testing as as a user all this time but now you can actually do it professionally and get paid for that so software testing right instead of the mattress now we're thinking of the application now we're thinking of the application so here's the definition software testing is verifying right those software testers use this cool word called verify instead of check software testing is verifying the application does what it is supposed to do by comparing the expected conditions against the actual results and Reporting the differ as bugs right you see I just introduced you to a New Concept it's called Bugs so we're going to talk about bugs in detail tomorrow so bugs they have their own life cycle and bugs they they they go back and forth between developers those Engineers who actually type in the code to create the applications and the testers right there's a special relationship between between the testers and developers there's this hate and love I'm just kidding they don't hate us they're just don't realize that they're in love with testers so um expected conditions and actual results so those are the two important Concepts that I want you to keep in mind because uh in the next slide uh I will try to trick you imagine you're tester and you got your first job this is your first day you a little nervous service and you know you came up to your QA manager and asking like okay what's my task what am I going to do do you want me to do anything right so and then your manager also doesn't know what to do and then like busy and thinking like okay let me give you some task here's the application just gave you this you know URL of the application uh the address of the VB based application and and saying like okay you will be assigned to this project and then uh why don't you just think of how are you going to design your test cases what is going to be you know your first uh step basically you know what will be your first step and how will you be designing your test cases so it's a question to you so think think about that what is your first step how you going to handle that situation all right right okay I'm getting really really some really good answers okay exactly that's right yes happy path all right so you're going to look for happy path as well all right that's yes you know that term that's that's great read other test Keys is from other people we do that and great so um and this is also similar to some of the interview questions that you might get as well so uh usually in the interviews as well you're given a certain application not not an application but a scenario like you know why don't you test a pen why don't you test a broken calculator or you know broken toaster or whatever um common mistake that most of the you know new QA testers make is they jump straight into Test's design and thinking of the scenarios that they could do and so on without asking questions right so good testers they start from asking questions and your first step should be learning the product right learn the product first it's logic right so if you know the product better if you know the product better exactly yes I can see some good answers if you know the product better then you can test better right there are more chances that you're going to find those hidden defects you're going to find those problems and you're going to know what to test actually maybe this is an application that already exist and just small feature or part of this application change so you don't have to test the full application right so you're going to have to understand the context right so your first step here would be to ask for documentation thank you yes great answers from the audience you ask for documentation if the documentation exists right and that shows that you know something so um let me actually uh uh give you an another interesting question here that's real interview question and actually this is from my personal experience this is uh uh one of the companies one of the uh past companies that I worked for and at that point I was applying for uh a manual tester position and then I got this question uh and the interviewer gave me a piece of paper that those times it used to be uh more of in person and uh a panel interview with the you know the other interviewers are in the room and then they're giving me the piece of paper with this diagram not exact diagram though you know pretty complex workflow right you see that there a bunch of you know dependencies and then decision making going on there different you know status is changing and then different roles very complex and and look at the question that they're asking me they're saying how many test cases would you create how many test cases would would you create to test this workflow or diagram so pay attention they're asking how many test cases would you create to test this workl right I you know I looked at this uh diagram for a moment and then I quickly realized that you know they're certainly not expecting any number right so that's that's you know that's a tricky question and um they're not expecting you give any any specific number here that's just to check your knowledge of how you handle uh the testing process how you actually go through how you what is your thinking process and how professional you are and so on so so here here's how I answered so I said thank you for the question uh and as a tester my reaction whenever I get a piece of uh paper with a picture or workflow like this my first reaction would be um is there more to it can I can you tell me more about this product is it a web- based application or is it desktop based application does this application has a graphical user interface or maybe it is just the application programming interface um is there any other systems that it works with it's it is integrated with is this a new application that is being created from scratch or it's existing application and some part of it is actually changing maybe there's like a before and after model uh here and is this the latest version of this document or of this picture maybe it's outdated whatever you're giving me so there are so many missing parts there are so many missing information before you can actually start designing your test case let alone the number of test cases number of test cases is the last thing that that should that should concern any QA team because you can have thousand test cases 500 test cases but if you're not testing all of the requirements if your coverage is still below 100% I just introduced you to another term here um coverage right requirement coverage so that means you know are you actually testing all of the requirements that were in scope right or maybe you're missing some of the requirements so maybe you created duplicate test cases of 500 and they're just useless test cases so the count doesn't matter what matters is the coverage right but more important more importantly in this situation is your answer should actually communicate to the to the interviewer that the good testers learn the product before they give any technical answer right you have to learn the product you have to ask questions good testers ask questions and good testers never trust anything that's anybody saying basically you know you have to verify you have to verify double check you have to make sure everything is consistent right and then you don't not you do not assume as ums also against your religion as a tester right if there is such religion so you do not assume testers do not assume you're not allowed to assume you have to work based on the facts based on documentation all right so let's now um jump into the next step I think a follow-up question here from the audience who are new to QA world is okay how do I learn the product right how do I learn the product so you'll learn the product you'll learn about the functionalities of the application by reading surprisingly right by reading so you read the book you read the requirement document and there are many different types of requirement documents that you know you might be given on your first day or during your QA career you know it's they start from business requirement document and some of them might be actual documents some of them might be just information that's electronically Sav in in the um in in Tools in certain tools test management tools like jir for example like in the form of user stories and so on right certainly don't want to complicate this at the moment but uh the purpose of those documents is to describe how the application works to describe specific features functionalities of the application under test right the application that you are planning to test and then when you read those documents now you start understanding the application you get better uh and then sometimes you reach the point that you're actually going to understand the application better than the developers better than maybe even the users you know because the information changed right users requested something thing and then it was converted into some uh some documentation by uh you know Superman or guy called business analyst and that business analyst interpreted in the way they uh they think and then the information changed along the way and then but this is the you know application that's created and users eventually accept right to a certain extent um and then you at the end of testing actually become a subject matter expert in testing and then and then those users actually reach out to you and then they involve you in the meetings and ask you to help out uh understanding the application better uh so that they can test as well before they start using before they accept so now let's assume that you ask the right question from your QA manager QA lead and then they provided you this documentation functional requirement documentation and that's what we're going to look into right now and we're also going to look into a tool called Azure deox and it's a test management tool where you can actually create your test cases so you don't have to create it in a piece of paper or Microsoft Exel so um with that being said let's just jump into let's look into the document first so this is the application that let's say your QA manager gave you it's a test ation let's say it's a test environment right so test environment that means that it's it's um it's an application that you can test without impacting the actual users right so um here's the uh typical functional requirement document here's a typical functional requirement document so again the purpose of this document is to explain you how the product works right so scroll down verion history table of contents there's some you know list of requirements here there's this traceability between the business requirements functional requirements um and and then you go into the detailed information about each requirement now as part of our um teaching courses uh we provide access to uh those documents to our students so that they can work like in a real uh work environment basically so that they can ex you know gain exper experience basically so um let's pick the requirement number one uh which is login and start reading so as you can see it says when the user navigates to this url url means the web address here and login screen will display okay further and the login screen will contain the following elements so we're looking at the username password and the password here's here's one interesting thing you want to pay attention to entered valys will be hidden or masked as those spells so whenever you're entering your password it should be hidden now login now this is where the you know it gets interesting right so login button if the user answers the correct username and password combination login screen will navigate to product screen this is what we call as the happy path sort of right so correct username correct password and the expect result so let's jump into the tool and then create a test case so this is the main sort of uh task that you will be doing on a daily basis you will be reading the requirements regardless of where they are and convert them into test cases right so that's what we're going to do so this is the um one of the tools right there are different tools uh in the market and uh Azure devops is uh one of the widely used tools uh currently and uh to create it has you know several um modules here and we're not going to stop in most of them but we're going to focus on creation of a test case and as you can see very it's very intuitive so you're just going to you have this button that's asking you to click on it so create new test case so we're just going to go ahead and create new test case and this pop-up window opens so your first step would be to give a name to your test case right give a name so so we're just going to name it as login with correct username and password so some people like to put verify in front of it check test and I try to keep it clean um and I follow the um uh pattern called action plus object so you just you know start with the action like login and then log into what the with what so you just mentioned login with correct username and password and there are other parameters that you can work with here but we're just going to jump into the steps or actions right away right to keep it short so first step what we what would be the first step First Step would be we have to open the website website right we have to go there and then I'm getting some here go to the website exactly so navigate to let me just go ahead and copy paste actually you know what this is we should be copying and pasting from the documentation that's right so we're going to copy and paste from here and and the actual result is also described here login screen will display let's just and put the actual result step two enter username but let's say correct username right enter correct username what what are we expecting if we go here there's no much expectation here this as long as the system allows you to enter right system allows to enter now enter password right correct enter correct password what's expectation here let's look at the document entered values should be hidden or masked okay that's our expected result or expected um result that's right right so let's go to the uh step four that's which is a the most I think critical part just click on login button so what's the expected condition here I mean the expected result here which would be log screen will navigate to product screen let's put that that's it so your test case is basically complete right so we just took the requirement and then converted that requirement into a test case so we have the test case name and we have the actions and we have the expected results looks simple like save and close now your next step would be I mean normally you would actually you know create all your test cases and then execute but for demo purposes I'm just going to go ahead and run the test case for you as well so we're going to go here and then select so you're going to go to execute you see you can Define and then you can execute we're going to go to the next um tab execute and um and then click run for web application and on the left hand side here if you can see this this popup window open and we're going to open the actual application also on the right hand side here right I hope you guys uh all can see so and then we'll start executing right okay great you can see so we'll start executing so the first step we navigate that's right we navigated to this website and we got the login screen pass and enter correct username we're going to get this correct username from here because this is a demo website all right it just it allows me to enter next one is enter the password let's enter the password it it is masked it is masked it is hidden you know that's like a you know industry standard then click on the login all right so the next step would be we're going to click on the login it took me to the product screen I didn't see any error message right anything anything you know out of the ordinary so you know we passed so we're just going to pass everything and there's a button called save and close and we're going to go back let me enlarge and go back to this here let's just refresh go back and you can see the test case status actually now passed right so now so this was your happy path now let's go back to the documentation now look at the next paragraph here which says if user enters incorrect username and password combination system will display an error message so so this is more of a negative path right if you enter incorrect username and password combination system will display an error message now here's a question to the audience what does it mean incorrect username and password combination and how many different combinations you could actually come up with you know how would you actually test this right because it's not really telling you you know is it one combination is this two combinations and how would you test right correct name and wrong password here's one one answer great right correct name and wrong password you could do that wrong name and correct pass yes you can you can flip that that's it all right yes how about a blank username and then you know correct password or whatever password and blank password or populated username so you see this is where the testers knowledge or uh professionality uh professionality actually yes blank can be uh considered as incorrect as well kicks in right so you have to come up with the the scenarios now you have to go beyond the documentation in this particular cases right so you have to be able to have you need to have this break uh to test uh ability yeah make make passwords with numbers and symbols great suggestions so let's try to create one of those uh additional test cases here so we're going to go ahead and again click new test case so and again same step but there's one interesting um interesting uh concept here that's called shared steps so if you go if we go to this particular test case that we created here right um so let's just go back and then let's create our new test case right so here we're going to uh name this test case as log in with blank username for example right this is just one um example of the incorrect or invalid scenario right uh so the first step here again would be navigate to the the website now actually this particular uh step can can be taken uh from reusable step that's it's a concept called shared step and if um you can create shared steps in in most of the test management tools so that it makes your life easier so that you don't have to recreate and then uh redo the same step again and again as you can see I just took one of the shared steps uh that I created previously and then this gives me the step autop populates the step uh basically so the next step here would be I'm just going to say leave username as blank and click login button right so what's the expect result here expect result here again uh we're going to go back to system should display an error message now we don't know what kind of error message but certainly it should not let you in right it should not let you in so we're going to create our next test case here and run that test case let's log out from the application for a moment let's put that side by side again this is pass right uh login is pass but let's leave this blank but let's put the correct password here and then click login you see you got this username is required message and we could do the other way around right I mean let's just actually complete our test case first our test case also passed as expected now let's explore some of the other um options here and you can leave the password empty as well right you click and it says password is required and what if we just put in two incorrect combinations then you're going to get another error message that says username and password do not match any user in the service so those are different scenarios that uh that you could potentially test um and um and this is basically how you actually going to read the requirement documents and then convert them into test cases uh and the um and then run them and this is one of the tools uh certainly there are many other uh tools as part of our uh teaching courses we also provide access to uh the uh test management tools so that um students can uh gain experience all right so uh I got some great messages here case no line about password no line about password right so we didn't uh we just left uh the that's right yes I mean you know uh you can you can design your test case in different ways certainly you could you could split it into different steps uh and so on all right so let's talk about now uh what makes a good tester right before uh we move on further what skills actually make a good tester one of the important skills that a good tester should possess is rapid learning skills because you will be given applications frequently new application frequently sometimes uh a completely new application that's being you know developed from scratch sometimes an existing application that you have never seen before but a small part of the application is being changed and those are uh usually called as a change request right no tester actually works in one company and that just works in one project you're going to end up you know working in several project you know we hire consultants and then for one year and then we extend them for you know two years sometimes and then but they end up working during this two years for maybe you know five to 10 different projects you know and different uh you know with different testing types basically so and each time you're given a new project you have to have this uh ability to quickly learn uh the application and that's very important and and certainly you know you don't you don't have to worry if you don't have that skill at the moment because that's something that you going to and develop over time that you will be able to quickly look for the correct material ask correct questions and then understand the application uh quickly and then uh the next important um good skill and this can be actually uh uh this can actually be uh your uh interview question as well right uh this can be your entry question like what what do you think uh makes you a good tester right so you can list up or why do you think we should we should hire you so you could actually uh list up those uh skills as as your own uh abilities and uh and behavior so willingness to continuously improve your testing skills so you should not stay in one place and you should always be challenging yourself with new uh new tasks and uh new types of testing and um maybe work on certifications so that you're always improve your testing skills because you are in information Technologies fields and and Technology Chang fast right so the next one curiosity to uncover defects Beyond what's obvious curiosity to uncover Beyond why do I say Beyond what's obvious because the requirement documents or the user stories another term or in in you know you know if you're working in agile environment um those are not always the whole story right so there are certain things that are missing there are certain things that were not actually described uh as it is and as a tester you need to be able to go beyond I mean certainly You Can Survive by just you know converting what's written in the requirement document and not going any step further but I would say good tester has to be able to go beyond and that's that's you know that's that's a that's a whole purpose of actually hiring a tester uh you know you shouldn't be just blindly copying and converting copying and pasting from the requirement document like I did um actually so further excellent communication skills why right why communication skills important that's a big part um it's important because both written and verbally you will be talking right some people say QA testers don't have to talk or don't have to talk to users and so on but you will be talking right you will be communicating with the developers you have to explain your thinking process you have to sometimes developers call the testers and then ask them to actually explain uh uh the defect right we're going to talk about that tomorrow certainly um and in written and and you also have to write your defect reports in such a way that uh it it gets resolved that it doesn't come back to you saying I'm not sure what what you meant there you know so uh communication skills are very important you will be talking to the project manager business analyst uh and the whole team uh basically next lesson defects right we talked about testing Basics today so uh defects is a big one that's a big part uh of the QA testing uh industry and this is one of the reasons why uh uh this role actually exists because of those defects defects that are found and not found so um I would say you know stay tuned and uh tomorrow same time