 |
Download Access 97 Ver. Download Access 2000 Ver. |
|
| • Author:
Pierce Business Systems • Version Number: 2.11 Bld 2 - Release Notes - Wish List • Revision Date: October 3, 2000 • Byte Size: 1,150,489 (1,124KB) • License: Freeware, License, Warranty Disclaimer • Cost: Free • Requirements: Microsoft Access 97/2000 is required to run this MDB file • Screen Shots: Test Case Explorer, Test Case Detail, Properties Wizard, Report Wizard, Pick Language, MultiLingual Dictionary Wizard • Report Images: Sample Project Summary Report, Sample Test Case Summary Report, Sample Test Case Detail Report • Description: Test Case Manager (TCM) is a tool designed for software test engineers to organize test cases for storage and execution logging. Test cases are written up in a standard format and saved into the system. Test cases can be organized by level (Smoke, Critical Path, Acceptance Criteria, Suggested), by area (GUI breakdown, installation, data, etc.), by status (pass, fail, untested, etc.), or other breakdown criteria. Once test cases are built, testers use TCM to track and report success or failure of test cases. TCM provides an unlimited number of central, multi-user databases, each of which will support an entire test team. TCM is intended for use by small to midsize software development companies or organizations. TCM was designed to be easy to learn and use. Most features are implemented as intuitive wizards for users to step through. Why would you want to use a Test Case Manager: 1. Coverage: TCM is designed to report testing coverage. Test case coverage can be reported across areas, levels, etc. Once the test approach for an app is completely broken down in TCM, generating useful metrics becomes achievable. Examples of these metrics include how many test cases exist, and of those, how many have passed, failed, or remain untested. 2. Structure & Organization: TCM provides a systematic method of organizing all of the testing department's test cases. Without some type of central Test Case repository, test cases are just done adhoc (rarely written down, never re-used, etc.). However, systematic testing can be achieved by breaking down an app into separate test spec areas, and then writing formal test cases to plug into those areas. Then, useful metrics can be derived from the volume, status, type, etc. of the test cases. One powerful technique I've actually seen testing departments use is having more experienced testers write test cases, then temporarily hiring less experienced testers to execute those same test cases. I've also seen testing departments write test cases, then towards the end of the project, print and hand-out those test cases for technical support and others help out by executing (spreads out workload while controlling coverage at critical project completion phase). 3. Training: TCM is also a great tool for facilitating knowledge transfer. Testers new to a project can easily jump right into a project and easily begin executing test cases. The entire test approach for the app/project will be laid out for them in TCM (making it much easier to insert in new Test Cases and execute existing ones). Also, inexperienced testers will find TCM test cases to be a wonderful learning tool. • Troubleshooting: Please review the FAQ for troubleshooting. • Source Code: Available as part of the download. Press the F11 key to popup the database window and edit the code, forms, tables, etc. from there. • Dictionary Files: Dutch.dic • Sample Project: TCM TCM was developed in and requires Microsoft Access 97 to run. Join the TCM mailing list for notification of new releases, bugs, etc.! Click here to subscribe now. |
||
