From Fedora Project Wiki
No edit summary |
|||
| Line 9: | Line 9: | ||
|-style="color: white; background-color: #3074c2; font-weight: bold" | |-style="color: white; background-color: #3074c2; font-weight: bold" | ||
|Feature||Description | |Feature||Description | ||
|Solution on Nitrate | |||
|Bug No. | |||
|- | |- | ||
| History rollback | | History rollback | ||
| User can view history versions and undo changes, see [https://fedoraproject.org/w/index.php?title=QA/TestCases/BootMethodsBootIso&action=history | | User can view/compare history versions and undo changes, see [https://fedoraproject.org/w/index.php?title=QA/TestCases/BootMethodsBootIso&action=history one], and [https://fedoraproject.org/w/index.php?title=QA%2FTestCases%2FBootMethodsBootIso&diff=188386&oldid=141783 another example]. | ||
| Discussion with TCMS team needed to achieve this step by step. | |||
| <references/> | |||
|- | |- | ||
| Description part in test case | | Description part in test case | ||
| See the | | See the Description field in the [https://fedoraproject.org/wiki/QA/TestCases/BootMethodsBootIso example] | ||
| Write this in 'Note' field, add tinyMCE syntax editing to it. | |||
| <references/> | |||
|- | |- | ||
| Grouping cases (by media) | | Grouping cases (by media) | ||
| better to separate the cases to different groups in one test run. [https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test#Test_Matrix An example | | better to separate the cases to different groups in one test run. [https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test#Test_Matrix An example on wiki]. | ||
| More exploration needed during pilot instance. | |||
| <references/> | |||
|- | |- | ||
| Documents in test result page(Run) | | Documents in test result page(Run) | ||
| The area and syntax for the documents in test result page, such as contents on [[Test_Day:2011-01-27_Network_Device_Naming_With_Biosdevname|the example run page]] | | The area and syntax for the documents in test result page, such as contents on [[Test_Day:2011-01-27_Network_Device_Naming_With_Biosdevname|the example run page]]. | ||
| add tinyMCE syntax to “Notes” field and link to wiki documentation pages. | |||
| <references/> | |||
|- | |- | ||
| Moving test results | | Moving test results | ||
| Moving previous results | | Moving previous results from previous test run to new run. | ||
| Selectively include test cases when creating a new test run. On the other hand, the calculation/summary of the new run need support adding previous run results into account. | |||
| <references/> | |||
|- | |- | ||
| Result format | | Result format | ||
| Nitrate doesn't have 'warn' but | | Nitrate doesn't have 'warn' status which indicates the test | ||
passed, but other bugs were discovered while executing the test. Add or modify 'error' status to 'warn'? | |||
| Mark the test PASS, and linking to additional bugs filed. | |||
| <references/> | |||
|- | |- | ||
| 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. | | [https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test#Key An example] to show multiple results for one case on wiki. | ||
| | |||
| <references/> | |||
|- | |- | ||
| Authorities for pages | | Authorities for pages | ||
| Pages with different namespaces can have different permissions. | | Pages with different namespaces can have different permissions. | ||
| | |||
| <references/> | |||
|- | |- | ||
| Supporting anonymous user read-write access | | Supporting anonymous user read-write access | ||
| Anonymous have read-write access for certain test runs. | | Anonymous have read-write access for certain test runs. | ||
| | |||
| <references/> | |||
|- | |- | ||
| Integration with FAS | | Integration with FAS | ||
| Integrated with Fedora Account System: https://fedorahosted.org/fas/ . | | Integrated with Fedora Account System: https://fedorahosted.org/fas/. | ||
| | |||
| <references/> | |||
|- | |- | ||
| Page protection | | Page protection | ||
| Protect certain plans/cases | | Protect certain plans/cases | ||
| | |||
| <references/> | |||
|- | |- | ||
| License the content | | License the content | ||
| License the contents the same with wiki | | License the contents the same with wiki | ||
| | |||
| <references/> | |||
|- | |- | ||
| Upstream project community | | Upstream project community | ||
| monitoring it and actively discussing topics. | | monitoring it and actively discussing topics. | ||
| | |||
| <references/> | |||
|- | |- | ||
| Test day page(run) creation | | Test day page(run) creation | ||
| Test Day Plan and its cases are needed to create test day Run. | | Test Day Plan and its cases are needed to create test day Run. | ||
| | |||
| <references/> | |||
|- | |- | ||
| Test cases priority | | Test cases priority | ||
| Nitrate has P1, P2, P3..., modify to Alpha, Beta, Final? | | Nitrate has P1, P2, P3..., modify to Alpha, Beta, Final? | ||
| | |||
| <references/> | |||
|- | |- | ||
| Each case with different platforms | | Each case with different platforms | ||
| Better support two platform results submitting for each case | | Better support two platform results submitting for each case | ||
| | |||
| <references/> | |||
|- | |- | ||
|} | |} | ||
Revision as of 06:23, 15 March 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 | Solution on Nitrate | Bug No. |
| History rollback | User can view/compare history versions and undo changes, see one, and another example. | Discussion with TCMS team needed to achieve this step by step. | |
| Description part in test case | See the Description field in the example | Write this in 'Note' field, add tinyMCE syntax editing to it. | |
| Grouping cases (by media) | better to separate the cases to different groups in one test run. An example on wiki. | More exploration needed during pilot instance. | |
| Documents in test result page(Run) | The area and syntax for the documents in test result page, such as contents on the example run page. | add tinyMCE syntax to “Notes” field and link to wiki documentation pages. | |
| Moving test results | Moving previous results from previous test run to new run. | Selectively include test cases when creating a new test run. On the other hand, the calculation/summary of the new run need support adding previous run results into account. | |
| Result format | Nitrate doesn't have 'warn' status which indicates the test
passed, but other bugs were discovered while executing the test. Add or modify 'error' status to 'warn'? |
Mark the test PASS, and linking to additional bugs filed. | |
| 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. | ||
| Integration with FAS | Integrated with Fedora Account System: https://fedorahosted.org/fas/. | ||
| 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 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 |