hello students I Professor Puja ptin from tssm sa College of Engineering and research Nar I am associated with computer engineering department of Institute in this video I'm going to talk about laboratory practice second for final year students it is related to the elective subject that is software testing and quality assurance in this laborary practice we have to develop mini project for that purpose I have designed different assignments for you so you can understand the basic concepts of that from that assignment number four title of assignment is write test cases for email login by using a manual testing learning objective is understand how to write a test cases for email login using a manual ual test casing outcome will be after the completion of assignment students will able to implement test cases for email loging using a manual testing some of the theory concepts related to the assignment is test case which is nothing but a document with user action and expected result test cases are set of positive and negative executable steps of test scenario which has a set of precond condition test data expected Results post condition and actual result so there is a difference between a test case and scenario T scenario which will represent or which will give us the idea of what we have to test for an example verify the login functionality of Gmail account some of the basic rules for writing a test cases are first one is Excel sheet means what test cases are normally written in Excel sheet but you can write it in also notepad word but in Excel sheet it will be easier to understand also to implement second one is a naming convention it follows naming convention so we have to provide a un ID for that it is easier to understand and Implement test cases should be a simple next one is the valid test cases and invalid test cases suppose whenever we write a test cases we make sure that we have to develop valid and invalid data which is dependent on the requirement that we have providing for that test case suppose I'm taking an example of email loging which are providing with the correct username and password then it should pass or it should login with correct username and password and suppose if I am providing with the invalid data then it should reject that test cases so here it is a valid test cases and invalid test cases next one here is an simple test case template format for a how to write a tast cases for that purpose we need to write a test cases for a particular model so we need a project name and a module name next one is the reference document if suppose we are referring from any part or anything else next one is a created by here I'm taking example from the one side so I have given it then date of creation and date of Freeview now we will understand particular column and the particular row and its meaning first one is the tast case ID first one is the test case IDE means what each test case should be represented by a unique ID second one is the test scenario or the test case description which will uh describes the test cases properly from the test scenarios that what we have to do actually and what we have to taste next one is the Taste case which will Define the test cases properly from the test scenarios next one is the preconditions that is nothing but conditions that need to be me before executing a particular test cases next one is a test steps we have to execute the test cases and we have to perform some action based upon that so we have to do a test steps in detail and we have to follow it next one is the expected result sorry before that there is a taste data so we have to provide a proper test data to execute a particular test steps and we have to gather all the appropriate test data next one is the expected result the result which we expect once if the test cases we have to execute it next one post conditions conditions that need to achieve when the test case was successfully executed last second is actual result in actual result in which the system shows Once the test case was executed and what we capture the result after the execution it will be shows and the last one is a status it will finally set the status it may be a pass or it may be a fure let me show you simple taste case and I am writing in Excel sheet just second I'm writing in uh Excel sheet but every company use its own template to write a particular tast case the fields required by writing a test cases are are different and we need to write proper test cases for a particular module name and we required some are the project name and the module name here it is project name second fill is module name next one reference document next one is the created by date of [Music] creation creation dat prie now I'm going to take now I'm going to take next field as a paste case ID next one is that t scenario next test case description next one is the precond condition precond condition is necessary while we are executing the particular test case after that test tests next we require test data which will shows positive and some of the negative test cases next one is the expected result next field has a post conditions which will show our actual result after executing a test case next field is the actual result next status that we chose tast is a pass or well now we have to sort out it I will take it is as horizontally yes now our project name is here it is Google email next one our module name is login reference document from if any I have taken it from uh side created by me own date of creation that will some the date month and year you can write this format so I will give a today's date dat of preview if anyone it will be reviewed by our team lead or any PS team so test case ID here it is tast case ID is for login page that I'm giving it as a 0 1 T scario is verify verify the login of Gmail so this is my test scenario for that particular test scenario I'm giving a test description I'm considering one test case that I'm enter valid usern name and valid password this is four okay then there's a precond condition for entering the valid username and password that we need a valid Gmail account to do a login need a valid Gmail account to do login next one is a teste steps so I will do the first step is the I will enter valid username next step is the I will enter password next I will enter will click on login button so here the my steps for the first test scenario that is the verify the login of the Gmail then test data in previous slide I I have told you that tast data should be a valid so I have to enter the valid username and valid password username and valid password so my expected result will be a successful login it will shows our Gmail login screen post post condition for particular scenario is Gmail inbox will be shown show in actual result we will go to our Gmail inbox screen and it will be a pass it is the same as it is so everyone understood the first one is the scenario first test case that is the verify the login of the Gmail so second way is this is the positive test case because I providing with the valid data next one is for the negative test cases so I'm taking the one example is the same as it is I'm test case ID providing for that just changing the scenario scenario is also same verify the login of Gmail next I'm changing the test case description means I'm entering the valid user valid username and invalid password invalid password so for that precondition is nothing but we need a valid Gmail account to login same as it is steps steps are also same just the input we are providing with the test data it will be a change in that I'm providing with the valid username and next one is the invalid password so this test data will be provided while execution of our test case next Ed result what we get it will shows a message with that the our email and the password you have entered will not be a match the message will be shown on the screen Emil and password rer don't match this message will be shown po condition is same as it is but it will reject and it will fail so it is related to our negative test case so here I'm giving the some positive test case and negative test case so you can take another example too for same as it is for ebanking for ATM just here you will change your project name and the model name but you will follow the all steps as it is test case ID test scenario test case description precond condition test steps test data expected result post condition actual result and status that will be fail or the pass