Hello, and welcome to module four. In this module, you will have an opportunity to practice, you will see a couple of live demonstrations of what we've learned so far. In this demonstration, you will get an opportunity to see exactly how a software tester execute a manual test case. So the test cases here on the left are the test cases that we created earlier. So now we're going to test the cycles, new user login registration. And so what a tester would do it is actually take the the Manual Test Case that was created here with Excel, and they would just go through each step and execute the steps.

They would enter the information in as they see it here on the test. case. So right here on the right, I am following the steps and entering the data from the test case. And to the these fields here in the cycles application if you're working for a company and some companies have automated tools that you can use to create test cases, but here we have this manual test case that was created in an exhale. And so just scrolling through and following the steps. And we go down a little bit further, and we're almost done with this this test case right here.

We're just again entering in all the required information. We are checking the appropriate boxes based upon the steps in the test case. And in a second here, we will click the submit button. And thank you for registering, which is what the test case stated that it should do. And we will move on to the second step and the next step, where we would actually log into our email address. And make sure that that vallot that validation email appears, which it does here in this example.

So we're on this step right here. And we click on this link, and the user is taken to the cycles login screen, and it states that the account has been activated. And we'll see one more step here. And now that person, the tester would sign in using a new user login name and password. So they will put in their, their login name, they create it. So in this case it was no solid 2017 along with that password I'm signing.

So that's basically what a tester does. They take your their test cases, they create it after reviewing the requirements. And here, they would go back in each step that passed or fail. You could do it after each step. Or you can after everything is done, you can go back and just put p or spell out the repairs for each step that that pass which is what I'm doing here in this case. All of those steps pass.

So that particular scenario, it pass. We have another the other test case here where we can execute those tests. execute those steps here. So it's the same thing that you as I mentioned earlier, a software tester. They create test scenarios and test cases after reviewing the test cases, after the test cases have been completed, they take that test case and then execute it and test a new system out any issues that are found during that time they create a defect and report those problem to their lead they lead then we'll assign that defect over to the developer A team to fix it later. So that concludes test execution.

Thank you so much. In this demonstration, you will have an opportunity to see how to create a defect using a defect tracking tool. So here, what I'm doing is just logging in. And a test manager or tests lead would create a project, the test project for that particular application. So if you recall, the name of the application that we're working on is cycles. So what I'm doing here is creating a new project.

And this defect tracking tool. It's a demo here, call redmine demo until if you'd like you can access yourself just by going to demo.redmine.org and just play around with it. So again, here, I am just creating a project they cyclos demo project. So I'll put in these cycles demo name, along with a brief description of the project itself. The modules are already pre selected, so I will keep them and the trackers for tracking bugs, features and support. So I'll just say create and continue.

And so my project was successfully created. So now we're set up and we're ready to create the fix. So, I am going to actually go back here and find the project. So we have cycles demo. That's the name of the project. As you can see Hear My name is there, Alison Juanita Hamel, I am the manager.

I'm going to click on the new issue tab. And we're going to pretend that we found the defect during our test execution, just so you can see an example of how to create a defect. So the subject line, we'll just write a brief description on the error message. So my error message did not appear. or something of that nature emissions was was incorrect. So again, just a brief description of the error message you receive.

In the description. Text box below, you have a lot more land landscape to enter additional information. So here, I'm going to just add some more information about the error message that I received. And another thing too, and you will see this in a second, a tester will also enter the steps to reproduce the error message. This is very important to put the steps to reproduce the error message. So when a tester is reporting these issues to a developer developer will know exactly where At what point that error message occurred.

So this assists them greatly with their troubleshooting and debugging, when they're when they're trying to fix the problem. So the second you will, you'll get a chance to see just some of what I just spoke up spoke about putting the steps to reproduce. So the more information you provide in the defect tracking tool is just silly. The developer greatly in finding the root cause of the problem. So here's step to reproduce. And also, if you are using a, you can also maybe copy the steps from the actual test case, into the, into this field.

Sometimes it's quicker and easier to just copy the steps instead of typing everything yourself. But we just take a few more seconds here so you can see exactly what happened and what what I did. And that was just entering all of the steps. And as I'm doing that, as as, as I'm writing the steps here, let's go over just some of the the fields that you learnt earlier about the components of diffic. We see the status, the priorities which we discussed earlier assignee, who was your son and this defect to also we have you'll see you'll have an opportunity to insert a screenshot if necessary. So just a few seconds longer we have the start date, the estimated time sometime a developer will put in estimate the time they think it will take to to fix the problem.

So again, the more information you provide to developer the easier makes their job easier. And so here what you saw a second is that I went over to the test case itself. copy some information from from there. So, just a few more seconds here of entering the steps to reproduce. And again, as I mentioned earlier, it's a lot easier to just copy the steps. But this is basically how you created the fit.

Take a few more seconds here. Once we're once we're done and I'm scrolling down over here to copy some information from the test case and put that information into the end the defect itself In a developer will, as I mentioned earlier, that person will look at these steps, execute these steps and see if they're able to reproduce the problem. And they can go behind the scenes and go to the code and see exactly what's wrong, why there's a problem. So again, it's vital to put as much information is possible in these defect tracking reports. should be done in a second. And so the problem is the incorrect error message was incorrect error message appears.

So that was the problem. So say error handling issue and scroll down here. And so what I'm doing here is attaching an actual screenshot of the error message. So not only do I have my steps to reproduce, I have proof that this problem did occur. So the the developer has everything that they need. And so I'm going to change the priority.

So this is urgent. I need to have this problem fix right away because this prevented me from moving Forward well from this test case, test case passing. And so, what he did was create a defect number. And so, since that test case failed, I will go to the test case. And if this step will actually fail, I will put sale and put the defect number. And so, when someone else is trying to or when someone else has to execute this test case, they will see that, at that step, it fail in that test case itself fail and we have a defect, defect number So that concludes how to create a defect using the defect tracking tool.