As testing requirements come at you from all directions - documents, links, wikis, Sharepoint, meetings, dreams and hallway conversations - you can build and manage a test requirements tree per Release or Sprint or park them in a Global repository. Drag-n-drop individual requirements or entire repositories. You have complete flexibility. A requirement got pushed out to the next release? Drag it back to the Global tree and reuse it for that next release.
Using a rich editor, author your own requirements. Add those attachments that come via email to it. Link it to where requirements are documented on websites, wikis or doc mgmt systems. Import them from Excel. Create Custom fields to track everything. Get as wordy as you want or just plain lazy. |
Map your testcases to these requirements. Or map them the other way around. 1:1 or 1:n or n:n - you get the picture. Speaking of pictures, track your requirements coverage with real-time metrics and charts. Full drill-down and live. Like it ought to be.
Almost done with your release? Wondering if you covered it all? Don't wonder, just pull open the end-to-end traceability matrix to see which requirements have been covered, tested or are buggy. Save these reports. Your auditors will love you. |
