From Fedora Project Wiki
(Created this page to analyze the requirements of our TCMS) |
No edit summary |
||
| Line 6: | Line 6: | ||
== Current wiki-based TCMS == | == Current wiki-based TCMS == | ||
=== General Manual Test Use case === | |||
For each release: | |||
* Easy to edit | * Create test plan | ||
* (Update Release Criteria) | |||
* Search from categories or Create new test cases | |||
* Create test result template | |||
Then for each build: | |||
* Create test result page | |||
* Use redirect link as current links | |||
* Send announcement | |||
* Execute tests and provide test results | |||
* Summarize the report manually | |||
=== Pros{{result|pass}} === | |||
* Easy to edit/modify | |||
* Permit anonymous testers | * Permit anonymous testers | ||
* History roll back, easy recovery | * History roll back, easy recovery | ||
* | * Multi-testers contribute one case | ||
* Low barriers to entry | |||
* Flexibility | |||
* User can apply for different permission | |||
* Pages with different name space have diff permission. | |||
* Different name spaces and categories to organize pages. | |||
* Templates designed to fit for different instance. | |||
Details: | <!-- Details: | ||
* Only one result page for current installation/desktop validation event. | * Only one result page for current installation/desktop validation event.--> | ||
=== | === Cons{{result|fail}} === | ||
* Results tracking | * Results tracking | ||
* Results querying | * Results querying | ||
* Data statistics | * Data statistics | ||
* | * Simple appearance | ||
* Syntax editing without | * Syntax editing without forms | ||
* Cases without a category existed | |||
* Cases have no 'review' phase | |||
== Nitrate TCMS Features== | |||
=== Manual testing Use Case === | |||
# QE Project/Team Lead assigns feature to be tested | |||
# QA searches TCMS for Test Plan | |||
# QA creates new Test Run | |||
# QA Executes Test Run | |||
# Test Run report available for viewing | |||
=== Writing a Test Plan Use Case=== | |||
# QE Project/Team Lead assigns feature to be tested | |||
# QA writes a new Test Plan | |||
# QA adds Test Cases: | |||
## Create new Test Case | |||
## Import XML Test Case | |||
## Add existing Test Case | |||
## QA Executes Test Run | |||
== | === Pros{{result|pass}} === | ||
* Tree view | * Tree view showing the current plan, and its parents and children using a tree style layout. It provides the ability to edit both parent and child plans. . | ||
* Email Notification | * Email Notification in workflow. | ||
* Runs and cases easily cloned along with more additional options | * Runs and cases easily cloned along with more additional options | ||
* Bug list automatically generated | * Bug list automatically generated | ||
* | * Test run report auto-generated | ||
* Test cases have reviewing status | |||
* Different status of a Test Run for tracking | |||
* More than one tag for a test case | |||
=== Cons{{result|fail}} === | |||
* Users without authentication (Guests) are granted read only permission to Test Cases and Test Plans | |||
* multi-testers contribute to one case not supported? | |||
* no history roll back | |||
* permissions for users are not well grouped | |||
== Must-Have and Nice-to-Have == | |||
<<TBD>> | |||
== Migration work == | == Migration work == | ||
<<TBD>> <!--how the crowd-source test workflow would integrate within tcms.--> | |||
Revision as of 11:10, 10 December 2010
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
General Manual Test Use case
For each release:
- Create test plan
- (Update Release Criteria)
- Search from categories or Create new test cases
- Create test result template
Then for each build:
- Create test result page
- Use redirect link as current links
- Send announcement
- Execute tests and provide test results
- Summarize the report manually
Pros 
- Easy to edit/modify
- Permit anonymous testers
- History roll back, easy recovery
- Multi-testers contribute one case
- Low barriers to entry
- Flexibility
- User can apply for different permission
- Pages with different name space have diff permission.
- Different name spaces and categories to organize pages.
- Templates designed to fit for different instance.
Cons 
- Results tracking
- Results querying
- Data statistics
- Simple appearance
- Syntax editing without forms
- Cases without a category existed
- Cases have no 'review' phase
Nitrate TCMS Features
Manual testing Use Case
- QE Project/Team Lead assigns feature to be tested
- QA searches TCMS for Test Plan
- QA creates new Test Run
- QA Executes Test Run
- Test Run report available for viewing
Writing a Test Plan Use Case
- QE Project/Team Lead assigns feature to be tested
- QA writes a new Test Plan
- QA adds Test Cases:
- Create new Test Case
- Import XML Test Case
- Add existing Test Case
- QA Executes Test Run
Pros
- Tree view showing the current plan, and its parents and children using a tree style layout. It provides the ability to edit both parent and child plans. .
- Email Notification in workflow.
- Runs and cases easily cloned along with more additional options
- Bug list automatically generated
- Test run report auto-generated
- Test cases have reviewing status
- Different status of a Test Run for tracking
- More than one tag for a test case
Cons
- Users without authentication (Guests) are granted read only permission to Test Cases and Test Plans
- multi-testers contribute to one case not supported?
- no history roll back
- permissions for users are not well grouped
Must-Have and Nice-to-Have
<<TBD>>
Migration work
<<TBD>>