Test Automation Management
The Key Features of Gredy:
Hierarchical Tests organizations: Projects, Suites, Test Levels and Environments
Wiki style Updates
Calendar grid style Updates
Quick notice of changes in test results between day A and day A+1
Trends, KPIs and metrics at fingertips
Filtering and Search capabilities
New: High-level management reporting. Flexible building of reports, saving and sharing
Test case association with: test design, found issues, test data, notes
New! Built-In Defect Tracker based on 
BugPub.com tracker
Individual Test Result instance analysis details
Enterprise edition: Plan and schedule test sets execution - execution and results synchronization are automation Tool independent
Results analysis workflow and inheritance from previous run
Simple REST API of results submission & xUnit compatible API for retrieving test results
Easy integration with any Test Automation and Continious Integration tools
Grid-view administration
Download Gredy Whitepaper 
|
In fact, automated testing should have own specific tool [Wikipedia] for reporting and as collaborative environment. Usually automated testing is much more intensive then manual, so mixing up test run results of manual effort with automated ones is a unhappy practice.
Another point, test automation combines many practices from both development and testing, though it still serves as testing mechanism. This is why test automation collaboration tool should be specific for this very domain: it should be able to report gracefully and it should ease test results analysis, debugging and traceability.
Each discipline deserves appropriate tools.
So now, being armed, check out How does it work and then dive into User Documentation! |
