From Fedora Project Wiki
Line 29: | Line 29: | ||
| 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 | | add tinyMCE syntax to “Notes” field or link to wiki documentation pages. | ||
| <references/> | | <references/> | ||
|- | |- | ||
Line 44: | Line 44: | ||
|- | |- | ||
| 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. | ||
| | | Feature required to allow multiple testers to provide feedback on a single test given that the environment under test (hardware) can vary for tests. | ||
| <references/> | | <references/> | ||
|- | |- | ||
| Authorities for pages | | Authorities/protection for certain pages | ||
| Pages with different namespaces can have different permissions. | | Pages with different namespaces can have different permissions. | ||
| | | Admin the permissions by different user groups. Integration with FAS. | ||
| <references/> | | <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. | ||
| | | Feature required. | ||
| <references/> | | <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/. | ||
| | | Feature required. | ||
| <references/> | | <references/> | ||
|- | |- | ||
| License the content | | License the content | ||
| | | "GOOD" content license | ||
| Should be in the list of "GOOD" licenses - https://fedoraproject.org/wiki/Licensing#Good_Licenses_3 | |||
| <references/> | | <references/> | ||
|- | |- | ||
| Upstream project community | | Upstream project community | ||
| monitoring | | monitoring nitrate-devel@, and file/share requirements to bugzilla. | ||
| Actively discussing topics/release notes/plans etc. Open permission for TCMS bugs on bugzilla. | |||
| <references/> | | <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. | ||
| | | Consider each test day as a test plan. More exploration needed during pilot instance. | ||
| <references/> | | <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? | ||
| | | Admins should be able to control over re-defining the values to something appropriate for Fedora. | ||
| <references/> | | <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 | ||
| | | If it's hard to implement, set up two runs as a workaround: 1. RC1 - Installation (i386) 2. RC1 - Installation (x86_64) | ||
| <references/> | | <references/> | ||
|- | |- |
Revision as of 06:47, 15 March 2011
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 or 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. | Feature required to allow multiple testers to provide feedback on a single test given that the environment under test (hardware) can vary for tests. | |
Authorities/protection for certain pages | Pages with different namespaces can have different permissions. | Admin the permissions by different user groups. Integration with FAS. | |
Supporting anonymous user read-write access | Anonymous have read-write access for certain test runs. | Feature required. | |
Integration with FAS | Integrated with Fedora Account System: https://fedorahosted.org/fas/. | Feature required. | |
License the content | "GOOD" content license | Should be in the list of "GOOD" licenses - https://fedoraproject.org/wiki/Licensing#Good_Licenses_3 | |
Upstream project community | monitoring nitrate-devel@, and file/share requirements to bugzilla. | Actively discussing topics/release notes/plans etc. Open permission for TCMS bugs on bugzilla. | |
Test day page(run) creation | Test Day Plan and its cases are needed to create test day Run. | Consider each test day as a test plan. More exploration needed during pilot instance. | |
Test cases priority | Nitrate has P1, P2, P3..., modify to Alpha, Beta, Final? | Admins should be able to control over re-defining the values to something appropriate for Fedora. | |
Each case with different platforms | Better support two platform results submitting for each case | If it's hard to implement, set up two runs as a workaround: 1. RC1 - Installation (i386) 2. RC1 - Installation (x86_64) |