v.2.1 - Test Cases, CSV Import

All the features described below appeared in TP 2.1.

• Test Cases Management
• CSV Import/Export
• Batch Actions (Copy & Delete)
• Store Files in Database

Test Cases Management

Test Cases module closes the gap between Development and QA. TestCases and Bug Tracking modules bring additional benefits, providing comprehensive information about actual state and quality of user stories.

Usually, QA use Excel or MS Word to run manual test cases and bug tracking software to post bugs. This makes manual testing more complicated. Typical workflow:

1. QA open test plan in Excel, read test case
2. QA run application that should be tested and verify test case
3. QA switch to Excel and mark test case as failed, specify build number and run date
4. QA switch to bug tracking tool and add a bug
5. In the end, QA makes report in MS Word and send it to Project/Product Manager

With TargetProcess this workflow much simple

1. QA open test plan in TargetProcess, read test case
2. QA run application that should be tested and verify test case
3. QA switch to TargetProcess and mark test case as failed and add a bug

No reports required, since all data available online real time. No additional software like Excel or Bug Tracking tool, TargetProcess do all the work (except testing itself).

As you see, less tools and less steps will save time and keep QA focused on functional testing.

Test Cases Concept Overview

Briefly, test cases module should be used this way:

1. Add Test Plan
2. Add Test Cases and assign them on test plan
3. Create Test Plan Run for build or iteration
4. Assign Test Plan Run on QA
5. Run test cases against specific build
6. View Test Cases stats

Below is the schema of entities relations in test cases module.

Test Plan and Test Plan Runs

Test Plan is an entity that groups test cases. For example, you may create test plan for smoke testing and test plan for testing several user stories. Each test case may be included in as many test plans as required.

Usually you want to have historical data about iterations/builds quality. For example, if build 1.0.0 has 50 failed test cases and build 1.0.5 has 15 failed test cases it is clear that quality improves over time. To support this concept, TargetProcess introduces Test Plan Run entity. Simply speaking, you may run the same test plan over different builds and have run results stored in the TargetProcess.

Run Test Cases

Test Runner allows to execute specific test plan run.

Test runner contains two areas: current test case on the left and all test cases grouped by user story on the right.

You may:

1. Click on Passed or Failed button to mark test case as passed or failed
2. Add bug if test case is failed without lost focus
3. Click on test case name on the right to load this test case into the left area and execute it

When test case marked as passed, test runner loads next test case. When all test cases will be run you will see results and may re-run specific test case.

Quality Stats

Test Cases for User Story

Test Cases tab in user story view contains all test cases with last run states:

Test Cases Reports

Test Cases Runs by Release/Iteration/Build report shows overall quality state over releases/iterations/builds. For example, the chart below shows that only in last iteration all test cases have been passed, while in previous iterations about 30% of test cases failed.

Test Cases by User Story report shows quality of exact user stories. You may see quality of all user stories in current release or current iteration. For example, chart below shows that only one user story has failed test cases, while three other user stories completed and tested.

CSV Import/Export

TargetProcess may import Features, User Stories, Bugs and Test Cases from CSV files and export these entities into CSV format.

Import features:

• Map columns to entity properties (automatic mapping exists as well)
• Insert or update entities from CSV file
• Complete import log

Batch Actions

Almost any web application requires batch actions like delete all selected items, move them or something else. TargetProcess is not an exception and we've implemented batch actions in TP 2.1. However, we've tried to not burden UI with one additional column and introduced "Batch Mode" for lists. In usual mode there is just one additional link "Turn On Batch Mode" on UI. When user clicks on it, check box column appear as well as batch actions menu (which contains Delete and Copy actions).

Store Files in Database

In TP 2.1 it is possible to store files in database instead hard drive. This feature improves data integrity and simplifies backups.