From Fedora Project Wiki
(Created page with 'This page aims to list feature requirements for Nitrate system for the smooth test cases/plans/runs transition from Wiki to Nitrate TCMS. It identifies Must-Have and Nice-To-Have...') |
No edit summary |
||
| Line 1: | Line 1: | ||
{{draft}} | |||
This page aims to list feature requirements for Nitrate system for the smooth test cases/plans/runs transition from Wiki to Nitrate TCMS. It identifies Must-Have and Nice-To-Have features missed currently in Nitrate TCMS based on [[Tcms_Comparison|feature comparison table]]. | This page aims to list feature requirements for Nitrate system for the smooth test cases/plans/runs transition from Wiki to Nitrate TCMS. It identifies Must-Have and Nice-To-Have features missed currently in Nitrate TCMS based on [[Tcms_Comparison|feature comparison table]]. | ||
| Line 33: | Line 35: | ||
|- | |- | ||
| Multiple contributions for each case | | Multiple contributions for each case | ||
| | | [https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test#Key An example] to show multiple results for one case on wiki. | ||
|- | |- | ||
| Authorities for pages | | Authorities for pages | ||
Revision as of 11:40, 26 January 2011
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.
This page aims to list feature requirements for Nitrate system for the smooth test cases/plans/runs transition from Wiki to Nitrate TCMS. It identifies Must-Have and Nice-To-Have features missed currently in Nitrate TCMS based on feature comparison table.
Must-Have
| Feature | Description |
|---|---|
| History rollback(Undo changes) | User can view history versions and undo changes, see example |
| History comparison | Different versions can compare with each other, see example |
| Categories creation permission | User who generates the case should have permission to create a new category.(or use tag in nitrate instead?) |
| Description part in test case | See the description in the example, modify “Setup” to adapt it? |
| Group cases (by media) | better to separate the cases to different groups in one test run. An example on wiki. |
| Documents in test result page(Run) | The area and syntax for the documents in test result page. |
| Moving test results | Moving previous results in a test run to another. |
| Result format | Nitrate doesn't have 'warn' but has 'error' result status. Modify it to 'warn'? |
| Multiple contributions for each case | An example to show multiple results for one case on wiki. |
| Authorities for pages | Pages with different namespaces can have different permissions. |
| Supporting anonymous user read-write access | Anonymous have read-write access for certain test runs. |
| Page protection | Protect certain plans/cases |
| License the content | License the contents the same with wiki |
| Upstream project community | monitoring it and actively discussing topics. |
| Test day page(run) creation | Test Day Plan and its cases are needed to create test day Run. |
| Test day page documented contents | Documentation area(instead of 'Notes') is needed to place contents. |
| Test cases priority | Nitrate has P1, P2, P3..., modify to Alpha, Beta, Final? |
| Each case with different platforms | Better support two platform results submitting for each case |
| Test result page documented contents | The 'Notes' area can only place short contents. |