Congratulations! You have completed a Software Testing course on Learnvern. We have covered a lot of topics here. Now is the time for some practical implementations. So, whatever practical you have read till now. We will use that and test the application practically. I want you to pay attention to 2 things. The 1st one is Test Case Creation and the 2nd one is Bug Report. Happy Testing Now we will see Software Requirement Specification. Software Requirement Specification is given to us in which we get to know how we have to technically manage the software requirement. How to test it and what are the modules in it? In those modules how the interaction is happening? We will see that in this. So, this project that is there, it is for the ABC company. Like it is written here, project for the ABC company. And this project that is there is for the ABC company. And its work is Manager HR Payroll implementation. Means this is mostly used for employees, HR. Now we will see in depth. Like here it is given document information. What is the document number, what is the version, what is the status, who the author, the department, then what is the purpose of the document and then revision? Here the meaning of the revision is that, when we had made the 1st version, after that we discussed with the client that this is how technically the project’s output will come. Then we had a discussion with the client and the client suggested a few more changes. All the technical changes which were possible for us,technically, we implemented it and we made another version. So, these are its content, project scope, organization structure, what is the general setup, what will come in employee master. Here they have given project scope, employee information, and employee insurance. The modules that are company related or any particular employee related, those are included in this project. Like if we see the organizational structure here, so branches, like these are ABC company branches, in Ahmedabad, Bhopal and Baroda. If it is there tomorrow in Surat, we will even add Surat. In this there are different departments, there is marketing, finance, human resources. So, you must have got a general knowledge that this system, the entire company is going to use and every department of this company is going to use this particular department. okay! got it? Now, we will see the Login module requirement. And we will prepare a traceability matrix of this module. We have read the requirement traceability matrix before. You revise it before going ahead with this project. So that it is easy for you to understand this. okay! So, what have they given us in login? The System Administrator will be having full authorities. This means that the main admin will have all the authorities, he will create the employees, he will give them necessary rights. And the employees who are there will have particular page wise rights. Suppose there is a Sales employee. The sales employee will not be able to see the details of the development team or if there is any finance employee, he will not be able to see the details of the sales employee. Got it? So, this is the requirement given to us by the client and we have changed it technically. How to change the requirements, all that we have explained in the Software Development Lifecycle. So, you even revise that process before going ahead. okay! So, till now we have completed a Software Testing Course. We have covered a lot of topics. So, till now what all we have studied, we will use it and test the application. Here, we have an HRMS system of ABC company under which we have a lot of modules such as HR modules, sales modules, resource allocation, personal data management, training module, attendance management, and so on. So, we will test 2 modules of this system, which is login and employee registration. So, come we will see in a systematic manner how we will test any module of the application. But before starting it, there are few things that you should know. This is called ST, which means small but important things regarding Software Testing.okay! Every application is tested in a different way. Every company has a different way for the testing process. Any module, it is possible that you test it in a different way and I test it in a different way. So, it is not hard and fast that the testing should be done in this manner itself. This is a basic flow of testing. Got it? Now we will make RTM here. We have made the RTM here. You can see that we have classified it into B1 and B2 etc. In front of B1 we have written the module name. The 1st requirement we have bifurcated in module names like login and logout. The login and logout roles are applicable for what at 1st? Admin and sub admin. And what will be the description? That admin will have full access over the system while sub admin has limited access. That means the main admin will be able to see all the details in the particular application. But the sub admin will see only the limited things. B2, another requirement is taken here for employee registration. What does employee registration mean? It is part of the sub admin. When the employee will login he will see all the registration details? No, he will only see the details regarding self. So, that part is coming from the sub admin. What is the description of it? Need to create the employee login with all personal details in the form. What does that mean? The sub admin that is there, will fill the form of employee registration and employee login and password will be created so that the employee gets to log in with it. Like we saw in the RTM after business comes the technical requirement. Here, we have taken technical requirements. Admin should access each and every module in the system. All passwords should be alphanumeric characters with minimum 6 lengths. That means the limit of the characters of the password, that should be 6 minimum. Like if you are entering 5 it should have an error. If you are entering 4 it should have an error. We will keep all these technicalities in mind at the time of testing.Right? So, we saw that the business requirement is classified between B1 and B2 and then we have made the technical requirement. Now we will see how we have taken the Requirement Testability Matrix in a table. Like you can see here, B1 for business requirement, technical requirement T1 and Test Case ID is blank. Why is it blank? As we have not yet made the test cases. Now we will see the login of the system, registration form of the system and we will make the test case related to that. We will see about the project. This is our URL, where the project is particularly hosting our application. So, we have the login details. We have opened its backend side. Username, password and login button. These are the fields that we have. 1st of all, what will we make? We will make the test case. The particular admin module that we have for the admin login. For that we will make the test case. Test case, even this we have discussed before. If you don’t remember, revise it from the previous module and then go ahead with the project. So, what we will do is, we will open the excel and write Test Case there. Remember that the test cases should always be written in excel. What will come 1st? Test case ID. After that will come TR, what is the TR of? Technical requirement of requirement traceability matrix. After that will come BR, what is BR of? BR is a traceability matrix. After that will come the test case name. Then what will come? Test steps. After that what we will add is test data. After that will come, expected results. What are we doing here is, we are verifying the admin login. So, what will be the test case name? Verify admin login. Okay. Steps, how will we execute the steps? That we have to write in steps. What will come 1st in the steps? The 1st thing that will come is Go to Login URL, admin user, we have to enter, admin password we have to enter and then we have to click on login. Now test data, what will we insert in data? User name, right? What will come first? Username. What is the username? User name is admin and the password that is there is admin123.okay! These login details are correct. So, what should be the expected result? Admin should be able to login to the system. Right? Once, we will quickly revise it. Test case name, verify admin login. Because we are doing the verification of admin login whether it is letting the admin login enter or not. For that these are our steps. Login URL, admin user ID, password and login. This is the data we have taken. This is the correct data. Admin and admin123. What should be the correct data? Admin should be able to login to the system. Right? Come we will see the practical of it on a website.okay! So, whatever test data that was there, admin and the password that we had admin123, that we have added here and now we will click on login. Okay, fine, it is working. Our system is working on our particular user ID and password. Now we will test different situations in it.
Lawal Adewale David
LearnVern gives a deep view of software testing. This is one of the best learning platforms out there. Keep it up.
very nice. keep it up
Very well done courses
Cover all topics
Vinayak Vijaykumar Savle
it was helpful
very nice explanation and in depth knowledge
very nice explanation and quality videos, in depth knowlege of subject
Learn Vern is good platform for learning n gaining the knowledge....