The Test Cases module closes the gap between Development and QA. The Test Cases and Bug Tracking modules bring additional benefits, providing comprehensive information about the actual state and quality of User Stories.
Each User Story should have several Test Cases. Then you need a Test Plan that groups related Test Cases together (for example, "Smoke Tests" or "Reports Module Tests"). And finally you need a Test Plan Run. Usually you want to have historical data about the 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. Test Plan Run supports this concept. Simply speaking, you can run the same Test Plan over different builds and have run results stored in TargetProcess.
TargetProcess fully supports Test Cases management:
Prev