Steps

• 1. Map TeamForge and TestLink projects: The first step is to establish a project mapping between the intended TeamForge and TestLink projects. During mapping, in TestLink, you’ll be able to specify the TeamForge ‘Requirements’ and ‘Defects’ trackers for your project. These trackers will be used throughout the workflow.

• 2. Create Requirements and Test Suites: When a requirements tracker artifact is created in the TeamForge tracker specified in Step 1, you can choose to have a ‘Test Suite’ created in TestLink. The Test Suite, once created, is associated with the requirements tracker artifact in TeamForge.

• 3. TeamForge’s Requirements: TeamForge’s Requirements Artifacts mapped with TestLink’s Test Suites.

• 4. Populate Test Suite with Test Cases: Within TestLink, you can find and populate your Test Suite with Test Cases.

• 5. Run Test Cases against Builds: Once the Test Cases have been defined, you can run them against desired builds, tracking results in TestLink. Test Case runs are associated to the build/binary being tested for traceability purposes.

• 6. Create Defects for failed Test Case runs: If you encounter failing Test Case runs, you can simply click a button inside TestLink to create a defect in TeamForge. This is a ‘push button’ defect that opens a new TeamForge window pre-populated with Test Case run failure data. An association will be created between the failing Test Case run and the new Defect.

• 7. Visualize Traceability: Once this cycle is complete, you can view the associations chain between the requirements tracker artifact and the Test Suite, Test Case runs and any associated defects, the builds or binaries they exercised, the commits which triggered the build, and ultimately the requirements that started it all.