From Fedora Project Wiki
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
It is still under construction and content may change. Do not rely on the information on this page.
Overview
This proposal analyses our current mediawiki-based system workflow and use cases, list the pro's and con's and compare them with nitrate system. The purpose is to find out what features we Must-Have and Nice-to-have in future TCMS, aka nitrate, and nitrate should be customized bases on these requirements.
Current wiki-based TCMS
pro's and con's of wiki-based workflow
Pro's
- Easy to edit
- Permit anonymous testers
- History roll back, easy recovery
- multi-testers contribute one case
Details:
- Only one result page for current installation/desktop validation event.
Con's
- Results tracking
- Results querying
- Data statistics
- Appearance
- Syntax editing without form
Must-Have and Nice-to-Have
Nitrate TCMS Features
- Tree view - automatically arrange plan, sub-plan, nodes, sub-nodes.
- Email Notification for work flow.
- Status easily adjusted for tracking
- Runs and cases easily cloned along with more additional options
- Bug list automatically generated
- Report automatically generated
Limitations:
- Test runs/cases need be assigned to specific persons.
- single result permitted to submit for each run.