 Hello, everyone. Welcome to software testing online training by software testing help.org. In this today's demo session, I'm going to talk about three topics. One is introduction to instructor roadmap of the entire course. And then today's demo session or I'll be taking one of the topic for today's demo session and then talk about that particular topic. So let's start with the first one introduction to instructor. So let me introduce myself. I'm Ashok having 13 years of experience in software industry as a software test manager, presently working as a software test manager in India. And out of 13 years, I was in North America for two years and worked at the client location. Apart from this 13 years in software industry, I also have three plus years of training experience as a trainer, which I do for online training. So overall 16 years of experience into my profile, 13 years into software testing and the three plus years into software training. Let's just brief about my profile and moving on roadmap of the entire course. So before talking about the roadmap of the entire course for who this course is targeted for, so the participants of this training can be either from a graduates or B or beta graduates who completed their graduation or just finished their B or beta who would like to start their career in software industry as a software tester can go for choosing this training. And also for the guys who are into non IT background and would like to change their career into IT background as a software tester, even they also can choose for this particular course as a software testing. Also the guys who are already into software industry working into software testing or working into software development and would like to re-enounce their skills into software testing, even those guys also can enroll for this particular software testing course. Basically this course we have planned for five weeks, the total course tenure we actually planned for five weeks. And we are planning to have three weeks, sorry, three days per week. And we'll be having classes three days per week that would be Tuesday and Wagner's day and Thursday. So we are planning to have three classes per week that on Tuesday, Wagner's day and Tuesday. And this class is basically planned for two hours per day. And we plan to have every session two hours for each day. And out of these two words we'll plan for one hour 30 minutes, we'll have a discussion on the particular topic. And remaining 30 hours will be using the last 30 minutes of our time for the clarifications of the questions, whatever you guys are having, it would be like questions and answer the clarifications of your doubts based on topic whatever we have discussed. So we also learn by doing the assignments, I'll be giving an assignments for all of you guys on day to day activities. So I'll be also reviewing the assignments that will be done by you and also use these 30 minutes of time for providing a feedback on the assignments that are being given to you for the discussion. So this course basically will have participants from all the combinations like the guys who are fresh graduates and the guys who are experienced in non IT background. And also we have the guys who are already into IT background and would like to change the career to software testing or reenact their skills into software testing. So here we'll be starting this with the fundamentals of with the strong fundamentals and then move on to the advanced with the real time practical experience. And this course is as I said is targeted for five weeks. So I'm just trying to you know, show you guys the schedule how we actually plan for five weeks and what are we trying to cover in each week. So the week one, so we are planning to talk about SDLC models. So what is SDLC? SDLC is nothing but software development life cycle. Software industry has its own, you know, development life cycle and it has their own model. So SDLC is nothing but where exactly the software is going to start and what are the phases of the software in each phase what we are going to do and what are the different models of SDLC what we have, we are going to discuss about them under the week one in the SDLC. In SDLC also we have so many different SDLC models. We'll talk about each and every SD models like a waterfall model, V model, agile model and what is the difference between each model and which model is the best suit for type of the nature of the project you guys are working on. And also we'll talk about SDLC. SDLC is nothing but software testing life cycle where you know, SDLC is one of the part of SDLC itself. So we'll talk about what is software testing life cycle and what are the different phases we have and how do we plan for the testing activities under SDLC. And we also talk about different kinds of testing, what are the different kinds of testings we do and we also talk about test planning. So how to create a test plan and what are the components in the test plan, what we write in test plan, we also talk about the test planning in the week one. On week two, we talk about test documentation like what are the documentation that you guys have to prepare for the testing, test environment setup. So why we need to have a separate environment for the testing. So what is exactly the environment and how many different types of environments we have and what is the difference between each environment we also will talk about the test environment part. And we also talk about that what is test data, why we need test data and how to plan for having a master test data sheet and how do we manage it and how do we distribute it across the teams to use the test data. And we also talk about test cases, what are the different test cases, methodologies we have, what is the test case, what it contains and why do we need to write a test case and what are the different methodologies to write the test case, we will talk about that. And then we will also talk about entire flow of test execution. So what is test execution, when to start the test execution and how to plan the test execution planning and all the stuff also we will talk about in the week two session. Coming on week three we will talk about test reporting metrics, what are the reports that are generally used in the testing to update the management about the testing, what's going on and what is the status of test execution, how many bugs found, how many bugs are open like that. We will talk about in detail about the test reporting and what are the different metrics that we follow. And we also talk about the defect management, this is the most important thing as well in the testing. So what is a defect and then how to raise a defect, how to test the defect, all these things we will talk about in the defect management. And then we also talk about traceability matrix, how are we tracing our testing from against the requirements, we will also talk about the traceability matrix. So and as I said the test environment, we have different environments, we will talk about UAT, pre-prod, production environment. So we will talk about what is a UAT, what user acceptance test and then pre-prod, what is pre-prod, what is prod environments and we will talk about all the different environments. Why do we need to maintain separate environments in the testing and also we will talk about in detail about each environment, what is UAT, what is pre-prod and why you need test UAT and pre-prod, all three are four different environments based on the project. And then we also talk about change management, change management and other miscellaneous topic, anything, what is the change. I mean we have something like defect management and change request management. So what is the difference between defect and the change request, how do we cooperate the change management into the system. We will talk about that on the week three. On week four, we will be completely moving on to the tools basically. Now we learn the defect management and all the things. Now we will talk about defect management tools like Zera and Bugzilla. So when I say you guys get a defect, what you do, you basically raise a defect. You guys raise a defect in any of the defect management tool. So we have something called Zera and Bugzilla where you guys are going to raise the defect. We will show you in detail how to download Zera and how to raise a defect and how to test the defect along with the Zera and as well as the Bugzilla. So we will be using both the tools for the defect management tool. And test management tool tools like test link. We will be talking about test link and any other one of the tool as well for the test management where test management tool basically used for you know storing the test cases requirements, storing the test cases and it also used for test execution of your test cases. So we will talk about using one of the tool like test link and we move on with the live project. So this course also contains something live project where we give you guys one of the live project and we ask you to you know work as you guys work in the real-time environment like in your company when you go to your company and what exactly it starts with your project. Similarly, we'll be trying to give you guys hands-on experience before joining the job itself by giving you the live project where you know you understand the requirements, you write the test scenarios, write the test cases, execute them, you know, and log a defect. So this will give you complete hands-on with the real-time kind of exposure when you actually go to the project in your company once you join. It would be exact same what we guys do in the project and you guys would be experienced before going to the project with the live project. In week 5, we also help you guys in preparing the resumes and as well we also take some mock interviews and we provide guidance on the certification. So in resume basically what should you guys write in your resume and what you should not write in your resume, you know, how your resume should look like and what are the certifications that is better for you which gives you most weightage for your resume to shortlist. I mean to say it would be value added to your resume and we'll also try to help you out on resume preparation and the certification part. We also take mock interviews so that, you know, you guys would be having a kind of experience like, you know, how to attend the interviews and what type of questions that those guys are going to be asking. We also provide FAQs, nothing but frequently asked questions. Basically we cover it in the mock interview itself whatever is needed. And also we provide support for every individual once the training is completed or once training is still going on. Any clarifications that you guys are going on will be helping you out in your clarifications whatever you guys are having. Okay and apart from that anything if you feel we were not able to complete it, we'll be catching up it in the week five. So this is entire course curriculum starts with week one to week five and as I said it basically starts with five week session, three days per week, Tuesday, Wednesday and Thursday, two hours per day. So this is about the entire roadmap of our entire course. Okay and today's demo before going on to the today's demo let's try to understand why should I go for software testing help.com. So I said it basically provides training from well experienced working professionals. Okay and it's completely live hands-on training sessions, live hands-on training session as said we'll be providing assignments and we'll be reviewing the assignments whatever you guys have done. And course content considering the current job market we always you know enhance our course content based on the recent demands in the market. So practical assignments at the end of every session we'll be giving the practical assignments at the end of every session also we are giving you the live project as well where you guys will completely get it's a complete pure practical thing that you guys should be learning. End-to-end live project covered like I said software testing life cycle we'll cover you everything whatever is going to happen from SDLC using the live project. We also provide course completion certificate once you guys have completed your course stating that you guys have completed the course certification from software testing help.com and we also give you a ebook and ISDQB a steady guide for free as a bonus and you guys can utilize this ebook and ISDQB certification guide for clearing the certification part. You always have video access for your live sessions whatever the sessions we are learning here we'll be recording it and then you guys will always have access to these live sessions whenever you guys would like to you know listen it again you guys can just go and use that live sessions videos that are being shared with you. As said email support for your queries even after the course is completed anything that you guys have any clarifications needed you guys can send an email and we'll respond you back with the clarifications whatever questions you have and we also help you in resume preparation interview guidance sessions also included as I said we'll conduct the mock interviews and also help you in the resume preparations. There are so many reasons why to choose for software testing help.com okay and so we just covered introduction to instructor roadmap and voice software testing and now we'll talk about today's demo session so so I would like to talk about types of software testing so before talking about types of software testing the first thing what I would like to explain you guys is what is software testing basically so why we need to do a software testing or in simple term what are the objectives of software testing so what are the major objectives of software testing and what is software testing so software testing is a process of executing a program with intention of finding a defect so it's execution of a program with intent of finding a defect so what program you are trying to execute whatever the program that is written by the developer we are trying to execute that program with intent to find the defect so major objective of software testing is finding defects okay what is defect basically so defect is nothing but anything that is not meeting the requirement so let's take an example client says that his if if you're working for an ATM testing let's take an ATM is your application and where the requirement is client says if you guys enter wrong pin number more than three times after inserting your card your account should be locked so this is what my client requirement is so what is expected results when I insert my card enter wrong pin for more than three times my account should be locked but what is happening even after wrong pin entered for more than three times when I enter fourth time also my account is not getting locked so there is a deviation between what is being expected and what is actually it is doing so wherever you see there is a deviation between the actual result with the expected result then you're going to call it as a defect so major intention and objective of the software testing is finding the defect and second thing is make sure application is meeting with client client requirement so make sure application meeting when I say whatever client is requesting to us so we have to make sure that what client is needed what development team is developed is meeting the client requirement so one of the example I just gave when you entered the pin for more than three times your account should be locked whether it's really locking or not so you have to make sure it is meeting the client requirements as well and another objective of software testing is to you know prevent the defects so prevent defects are nothing but we would like to prevent the defects from the end user we don't want end user would be facing defects and you know where we'll be losing the confidence right from the customer's point of view so we would like to prevent the defects as much as possible so that we don't want any defects to be triggered and we don't want any you know troubling or issues to be faced by the end user itself so how are we preventing we are trying to do the testing you know so that as much as possible find the defects and if fix them and retest it and make sure there are no much defects and then client is prevented from the defects with actual users okay so these are the major objectives why we have to do the software testing and also one more thing is to deliver the quality of the project right so so quality is most important thing in the market in the particularly in competitive market so if you deliver the quality to the client then only will be you know in the business or you can expect more business from the client so to deliver the quality of the product we have to do the testing so these are the major objectives of the software testing finding the defects and making sure system is meeting the client requirements and prevent the defects and provide the quality of the system with the quality and and coming on to types of software testing there are two types of testing we have one is a black box testing and another one is white box testing so we have two different types let's talk about the black box testing so if you look at this this diagram here which is completely in the block so black box testing is what you guys do in black box testing you guys just give an input okay your input be given to your program and then the program executes and then it gives you the output so as you guys look at it's completely black box we really don't know what is happening inside the box we really don't know what is happening inside the black box we only know what input we have to give and what output I supposed to get like an example if you guys you take an example of calculator right so let's say I have a calculator and where I just entered some two numbers 20 plus 20 right and then I would just hit on equal to so I'm getting a 40 but I really don't know what is happening inside the calculator how it is calculating what technology they have used what is the coding logic that these guys have implemented to develop this calculator it's a pure black box to us so whatever you see is in the front end is the place where you guys give some input and then you expect the output based on the input that you are providing so you really don't know what is happening consider this is as your calculator and you are entering some two numbers for addition and you're giving that input you expect the output if you enter 20 plus 20 and your output should be 40 so this is what we are going to do in black box testing in simple term we really don't know internal architecture of the program what is the logic that these guys have I mean when I say these guys what is the logic that development team has written to implement to the system we really don't know we just bother about what to give an input and what to verify in the output so if you guys look at in the white box testing it's completely rewards to the black box testing you guys can easily understand now when I say rewards to the black box in black box you really don't know what is happening inside the black box but in when it comes to the white box testing you you really need to know what is happening inside the box nothing but you need to look at the code and what is the logic that is being written you need to do the code reviews and understand the architecture of the application also you need to understand the technology on which technology the application is implemented until unless you don't know the technology it won't be that much easy to understand the coding that is written so we we are majorly responsible for doing the black box testing but now the trend is slowly is changing we may be future needed to do the white box testing as well in some situations if you are already aware about the technology in which application is developed then it's good to go with doing the white box testing as well because you are already aware like the application is developed in java I am pretty good in java then it is good if you can go and do the white box testing as well so this is about types of software testing okay and moving on to software testing life cycle so as said stlc is nothing but software testing life cycle where it basically it starts so software testing life cycle basically part of sdlc as said let's take an example here let's talk about sdlc before talking about stlc sdlc is nothing but software development life cycle and here how the software development life cycle starts so basically it starts with you know understanding the understanding the requirements okay and then preparing the srs document I'll explain you guys each and everything whatever I'm typing here and then preparing the srs then design coding then testing so here understanding the requirement preparing the srs document nothing but software requirement specification so understanding the requirements is nothing but when you guys are starting on a project first you need to understand what are the requirements that the client is expecting to develop from us so first go and meet the client and understand the requirement what exactly you wanted to develop you guys for designing his application so and then once you guys have understand what exactly client is looking for then put all the requirements in the document which we call it as srs software requirements specification document so who is responsible for right so who is the actor here so actor would be b a b business b a is nothing but business analyst so business analyst role is he has to go and meet the client and understand the client requirement what he is basically looking out for and then put all those requirements in a particular document called srs software requirement specification this would be generally a ms word document or it could be a pdf file where you guys would be putting all the requirement specification that and then it goes on for for understanding requirements and preparing srs document both are done by the business analyst itself and next one is designing so what are we trying to design here you try to design the architecture of the application so who will be responsible for this one is architect who will be the responsible for this designing part and once the application is designed and then you guys go for coding so who will be responsible for writing the coding to meet the client requirements is nothing but the development team so development team starts writing the coding once the development team completes the preparation of the application and then testing would start so as you all guys are here for into the testing so we are responsible here so we are responsible for testing the application to make sure what all this thing to make sure to find a defect to make sure all whatever we talked about all the four things here is responsibility of the tester so once testing is done and then we would call it as a maintenance so who is responsible for maintenance I would say support team support or operation steam work okay so maintenance team would be responsible once we test it everything is working fine then we will we will say that just move it into the production so this is what the SDLC is nothing but software development life cycle starts with understanding the response of understanding the requirements and then prepare the document it's a role of the business analyst to do and then the designing comes into the next phase and where the architect is a guy who will be writing the designing designing the architect once the architect is completed then you guys would go for main development team will go on writing the coding and then once the coding is completed we start with the testing and then it goes on to the maintenance part now coming on to our part as a tester we have to plan testing how we have to do right so software testing life cycle we just looked at SDLC nothing but software development life cycle as said test life cycle is one of the part under the SDLC now what are we going to consider in the software testing life cycle okay so what we start with the software test life cycle basically we start with we start with I'm just trying to explain you guys about SDLC okay it starts with you know test planning so we try to initially start with the test planning so what is test planning contains it's a again I said it's a document where you guys write what are you going to test what are you guys not going to test what is in scope and what is out of scope okay and and compatibility testing details when I say compatibility testing or we need to test do we need to test this application only in windows operating system or do we need to test this application in mobile also like iOS 100 operating system is that in scope for us or not in scope that that also we'll be writing it and what are the browsers if it is a browser compatibility application if what are the browsers that we guys have to use you know is it only fine with the chrome or do you want to use it in internet explorer what are the browsers that client is expecting us to do the testing when to stop testing no when to start testing and everything about environment details also we are going to write it here okay basically in order simple to say it contains what is scope what is out of scope for scope is an example like say client says to test it in windows operating system and he says that I don't need to it to be tested in iOS so in scope of testing is the windows operating system and out of scope would be all operating systems apart from windows and some situation there could be different vendors also involved in testing like company a and company b the client is given it for two companies to testing like say module one is given to company a and module two is given to the company b and if you guys are preparing a test plan for company a you would say module two is not in your scope of the testing in scope out of scope that what you guys are going to write in test planning okay and you guys also will be writing here entry criteria and as well as exit criteria so what do you mean by entry criteria when we should be able to do the when we should start the testing what are the things it should qualify in writing the starting the testing what is the exit testing so exit testing is nothing but when you guys have to say release it to the prediction so we are done thorough testing and not found much defects everything looks fine and typically that would be writing it in the exit criteria however since it's a demo I cannot put everything about the test planning so I'm just trying to brief you guys on the test planning so after test planning now every individual tester will start understanding the SRS document SRS is nothing but software requirement specification document asset where you guys would be writing I mean business unless would be writing all the requirements whatever is client is looking for so here what you guys will be doing or doing is understanding understanding the requirements and then once you understand the requirements you once you start reading the requirements you will obviously get some questions raise questions slash your doubts or whatever clarification so you guys get in a requirement and you go through the requirement document you guys would get in a you know clarification let's take on the same example if you insert your ATM card in ATM enter wrong pin for more than three times and your account should be locked but they didn't talk about anything when a phone could be activated now I entered been wrong three times wrong so it is logged is it logged only for 24 hours or do I need to visit to the bank to activate what is the process to activate it or does it would be activated on its own after 24 hours so like this you guys would always get some questions when you guys understand start reading this or a document so once you guys have understand the software requirement specifications once your doubts are clarified then the third step would be we will be writing test scenarios test scenarios test cases okay so you whatever you guys have understood from the requirement specification document and then you guys go ahead and start writing the test scenarios test scenario let's take an example if you wanted to test the login functionality of your application let's say Yahoo is your application and where you guys would like to you know test the application whether it's logging in successfully or not so you guys can create one test scenario which is called verify login functionality under the test scenario you guys would be writing couple of test cases okay and once test scenario and test cases are prepared so what are we going to write let's take an example under test scenarios as said login I would write one test scenario saying that verify login so this is what my scenario is under this I'll be writing one test case enter valid user ID and password this is one test case second test case enter valid user ID and wrong password like this I would keep on writing the test cases for one test scenario so maybe a little bit confusing what is the test scenario and test case so for every requirement like say login is one of the requirement from the client so for every requirement you guys would write one test scenario so I have one test scenario where one requirement is to verify the login so I would write one test scenario which is called verify login and for this I would write multiple test cases so one scenario can contain multiple test cases verify valid user ID and valid password is given you are able to log in successfully that's one test case another test case verify valid user ID and given but password is wrong what should behave so like this you guys would keep on writing the test scenarios under the test cases and the fourth one would be test execution and the next step what you guys would be doing is test execution so what you guys would be doing in test execution is once the application is ready for you guys to test it you take all this test cases or test scenarios whatever you have taken and start executing them on your application then once you start executing the application you guys always see some defects like say after entering the valid user ID and valid password system still not allowing you to log in it's a defect though you are giving right user ID and right password the system is still not allowing you to log in it's a defect then you just go for raising defects so once you guys say the defect then defect team development team will fix it retest the defect and do take the decision go slash no go go no go is nothing but is the application is is really ready to go to the production if you say it's ready to go if it is not ready to go you always say no go so it will not be you know deployed to the production so this is how the testing life cycle what what we do in day to do activities as a tester this is what is being given here it starts with test planning test planning basically contains to brief it contains scope out of scope entry criteria exit criteria and there are a lot of other things we'll discuss in detail when we write we also write a test plan I said we'll give you live project we'll write a test plan for that live project and then understand the client requirements in the document that is given to you is SRS and then raise your questions doubts and clarifications and then go ahead writing the test scenarios execute them and raise the defect defect asset if anything the actual result is not meeting with the expected result then you guys can go ahead and raise the defect once the defects are fixed it retest the defects and then make a decision go and no basically go and no go decision will be taken by your test manager okay so thanks guys for all your time I hope this session would be helpful to you to decide on choosing a career and an IT software testing and start participating in this particular thank you so much guys and we'll catch up in the next sessions