This tutorial briefly describes a typical test project and the aspects of that project that are of importance to any QaTraq setup. Whilst the examples used here may seem simplistic they should highlight the key points of any test management process. The project and test team aspects described here set the scene for the rest of the tutorials in this section.

We are going to be testing a product known to the development and test teams as a 'car'. This car is made up of a number of components; engine, chassis, gear box and wheels (actually its quite a basic car). Thus From start to finish on this project we are expecting the development team to release 5 builds for us to carry out our testing (we're hoping for a lot of functionality in each build otherwise we're probably not going to sell too many of these cars). We have agreed to give each of these builds a unique version number along the lines of car_<major_version>_<minor_version>. Thus we have settled on the following version identifiers (or build identifiers if you prefer this terminology): All test cases, test scripts and results are linked against this product and the associated components and versions. So its important to make sure you get this setup right at the beginning. We'll come on to setting this product up in QaTraq at a later stage but for now if you want to take a look at how QaTraq stores this information look here.

We are assuming a fairly common test team structure is in place for this project. So this test team consists of members who carry out the following roles: In many companies Test Analysts and Testers are one and the same. Descriptions of each of these roles and how they have been setup in our tutorial example of QaTraq can be found here.