QualityMate for Tests Management (QM for TM) supports any kind of test cases (functional and load) allowing you to manage, in one place, all your testing artifacts. QM for TM allows you to design your test cases and test procedures, execute them, review and compare test procedure executions in order to reduce the application deployment risks. QM for TM is the right tool to support and facilitate your tests management process by providing the following benefits:
Completely adaptable: QM for TM does not force you to work in a pre-determined way or use a specific methodology. QualityMate easily adapts to the way your organization works. Whether your process is highly structured or very agile, QM for TM can be customized to support the way your teams work. The workflow process can be completely configured by setting security options and creating constraints, actions and transitions rules for each atomic attribute. By doing this you can assure your tests management process will be institutionalized.
Improve collaboration: Forum discussion allows stakeholders to provide important input regarding quality control information.
Database centric: QM for TM guarantees that the most current data is available to the people who need it, whenever they need it. Each test case can always be associated with any requirement type allowing you to draw conclusions about you project.
Access information from anywhere: QM for TM is a complete web-based four tier solution. The client layer is supported by a web browser, the presentation layer is developed using .Net technology, the business layer was developed using Java technology and the data layer which can be stored in Microsoft Access or Microsoft SQLServer databases. This technology allows you to access the information from anywhere without installing any extra software on your desktop.
Easy-to-use interface: Intuitive user interface allows you to guarantee a short learning curve for all stakeholders.
Automatic notifications: Users can receive automatic notifications every time a change happens.
Audit trail and change history: Every change is automatically audited. Each change creates a unique history record, highlighting the differences between one version of a test artifact and another, including the reason for the change.
Parallel development: Different project releases allow different teams working on the same project but in different releases of the product. Baselines can be created for each project release. By comparing baselines and respective releases you can see where volatility, modifications, additions, and deletions have taken place.
