Finally in this series of tutorials we come to the most important part. With out this part everything else is pointless. So here we examine how the tester should go about using QaTraq to carry out his or her testing and how results should be recorded in QaTraq. This tutorial demonstrates the essence of QaTraq's test case management

As a Tester using QaTraq you should be considering the following:

So the test analyst or test team lead has given you a nudge and said there's some testing to do. You log into QaTraq and running one of the reports (see below) you see that a test script has been assigned to you. The test script fits into the whole test setup as follows: So you see from the test design document that release (or build) car_0_1 has been delivered to the test team. The test analyst has written the test cases and included them in the 'Stress Testing' test script. You see when you look at the test script here, that you are down as the intended tester. Everything you need to know about stress testing the engine is detailed in the test script and the associated test cases. All you need to do now is carry out the testing and enter the resutls......but where do we enter the results?

We have a test script called "Stress Testing", which has a unique ID of : Which translates directly to a unique Test Result ID of: thus you will see that If your test script ID is TSC37-0.2 then your test result will be TRS37-0.2 (where TRS = Test ResultS). If you search for test result documents with an ID of "TRS37-" on the results search page you should see this. Once you've completed the search you will notice that you have the option to select [Single] or [Multiple] for this set of results: You'll notice in the [Multiple] view that there isn't enough room to display test case content on the page. However you do get a list of test result fields to whiz through and fill out (you'd probably want to have the complete test script displayed in another browser window if you were going to enter results in [Multiple] view).

However, we're going to concentrate on the [Single] view that you'll find here. We don't want to be viewing the results we want to be entering test results, so click the modify button at the bottom of the page. When modifying the test results you will be presented with a page that looks like this.

A point to note here.......if the 'Tester' for this test case/result does not match the person you are logged in as....then you can't enter the results. If you need to enter the result then your login Id must match the tester against the test result record. Change the 'Tester' value and save the results if you need to.

You will see the test script details at the top of the page. In the next section you will see a list of the test cases that apply to this test script (you can jump to a specific test case/result by clicking the test case id here). Below this you have the specific test case details. You need to follow the instructions in this test case and then enter the results in the section below the test case.

Select the result category (perhaps the test case 'Passed' or it may even have 'Failed'). Then click the [T] button (which stands for 'Today') and it inserts today's date in the Date field. Select the version of the product you carried this test case out on (this shouldn't need changing if the right 'Intended Version' was selected for the test script in the first place). In fact if you are running with the build identifier specified in the Test Design document then this value must really be left at its default value (otherwise you could alter the result reports unduly).

If you have a version of QaTraq later than qatraq_5_0 the next sections will be allow you to enter test logs as attachments. You can save attachments or logs which are common to the whole test script (i.e. they'll show up for every test result in the test script) or you can save attachments/logs which are specific to a particular test result record (i.e. you'll only see them when you are looking at this particular test result record).

Lastly you can enter comments and defect information. Comments are straight forward (just click the [edit] text). Entering defects is a little more involved. QaTraq is not a defect tracking application, its a test management application, so if you are entering defects you should only be entering the following information into QaTraq: And there we have it.....we've finished entering our first test result. All you have to do now is finish off the test results for the rest of the test cases in this test script, and if you've got a lot of testing outstanding then you'll have more test scripts to complete after that. To find out which test scripts you should be completing take a look at the reports you need to be running (in the section below).

Coming soon!

So what next? We've finished haven't we? Or did someone say there's another build on the way......