From Fedora Project Wiki

No edit summary
No edit summary
Line 47: Line 47:
Tester(anonymous user permitted):
Tester(anonymous user permitted):
# Execute tests and post test results
# Execute tests and post test results
QA:
* Create test cases:
# Use test case template format
# link tests to the packages they are designed to test
# Use different syntax such as <nowiki><pre></pre><code></code> </nowiki>
* Initiating a test run
# Create new test result page using test result template
# Have key section as result example
# Create sortable and collapse result table
# Use links to the page
# add test result page to relative category
# Redirect link
# Move previous test results to new test run
* Submitting a test summary
# Use curl command to generate bug and contribution list
# Send out test report
* Create a new page
# Edit with permission
# Use wiki syntax
# Rollback history
# Preview function
# Compare changes between different version
# View history editing records
# Use template format
Tester:
* Post test result:
# Contribute result to different platforms
# Add comments as references
# Post a bug to result
# allow multiple results for each one case
* Admin:
# Manage pages authority with diff name spaces
# FAS Integration


== Cons for Wiki-based TCMS ==
== Cons for Wiki-based TCMS ==
Line 52: Line 91:
<!-- Identify problems with our current system and workflows - e.g.
<!-- Identify problems with our current system and workflows - e.g.
     what would we like to do but are difficult/impossible with wiki-->
     what would we like to do but are difficult/impossible with wiki-->
# edit form instead of syntax
# manage test cases/plans
# automatically summarizing results


== Comparison ==
== Comparison ==
Line 57: Line 99:
<!-- Objectively compare feature sets of both tools in relation to
<!-- Objectively compare feature sets of both tools in relation to
         the important workflows-->
         the important workflows-->
{| class="wikitable sortable"
|-
! Feature !! fedoraproject.org/wiki !! nitrate
|-
| License
|style="background-color:white;"| {{result|unknown}}
|style="background-color:white;"| {{result|unknown}}
|-
| Integration with [https://admin.fedoraproject.org/accounts/ FAS]
|style="background-color:lightgreen;"| {{result|pass}}
|style="background-color:tomato;"| {{result|fail}}
|-
| Supports anonymous user read-only access
|style="background-color:lightgreen;"| {{result|pass}}
|style="background-color:lightgreen;"| {{result|pass}}
|-
| Supports anonymous user read-write access
|style="background-color:lightgreen;"| {{result|pass}}
|style="background-color:tomato;"| {{result|fail}}
|-
| Data entry format
|style="background-color:lightgreen;"| [http://www.mediawiki.org/wiki/Help:Formatting mediawiki markup]
|style="background-color:white;"| {{result|unknown}} [http://tinymce.moxiecode.com/ tinyMCE]?
|-
| Test case re-use (write once, link anywhere)
|style="background-color:lightgreen;"| {{result|pass}} using Category
|style="background-color:white;"| {{result|unknown}} Using test plans
|-
| Test case tags
|style="background-color:lightgreen;"| {{result|fail}}
|style="background-color:lightgreen;"| {{result|pass}}
|-
| Redirect links
|style="background-color:lightgreen;"| {{result|pass}}
|style="background-color:lightgreen;"| {{result|fail}}
|-
|}


== MUST HAVE & NICE-To-HAVE ==
== MUST HAVE & NICE-To-HAVE ==

Revision as of 08:28, 24 December 2010

Wiki Use Cases

  • Test Days Use cases:

QA:

  1. Create main page of test day
  2. Create sop guide for hosting test day
  3. Create Test Day template
  4. Create test day schedule
  5. Create new categories
  6. Create Test result and test case template(http://fedoraproject.org/wiki/Template:Result)
  7. Add page to related category

Host:

  1. Create the Wiki page Using the Test Day template
    1. Create test cases
    2. Set up the results table
  2. Add page to related category
  3. Send out announcement manually
  4. Redirect current link: Test_Day:Current
  5. Summary the event with curl command to test-announce

Tester(anonymous user permitted):

  1. Posts test result to the table with the template format
  • Release Validation Use case:

QA:

  1. Create installation/desktop test plan
  2. Create and Update Release Criteria
  3. Create main introduction page
  4. Create new categories
  5. Create new test cases
  6. Create test result template
  7. Create templates format for cases and results
  8. Add page to related category

Host:

  1. Create test result page
  2. Add page to related category
  3. Use redirect link as current links
  4. Send out announcement
  5. Summarize the report manually

Tester(anonymous user permitted):

  1. Execute tests and post test results

QA:

  • Create test cases:
  1. Use test case template format
  2. link tests to the packages they are designed to test
  3. Use different syntax such as <pre></pre><code></code>
  • Initiating a test run
  1. Create new test result page using test result template
  2. Have key section as result example
  3. Create sortable and collapse result table
  4. Use links to the page
  5. add test result page to relative category
  6. Redirect link
  7. Move previous test results to new test run
  • Submitting a test summary
  1. Use curl command to generate bug and contribution list
  2. Send out test report
  • Create a new page
  1. Edit with permission
  2. Use wiki syntax
  3. Rollback history
  4. Preview function
  5. Compare changes between different version
  6. View history editing records
  7. Use template format

Tester:

  • Post test result:
  1. Contribute result to different platforms
  2. Add comments as references
  3. Post a bug to result
  4. allow multiple results for each one case
  • Admin:
  1. Manage pages authority with diff name spaces
  2. FAS Integration

Cons for Wiki-based TCMS

  1. edit form instead of syntax
  2. manage test cases/plans
  3. automatically summarizing results

Comparison

Feature fedoraproject.org/wiki nitrate
License
Integration with FAS
Pass pass
Fail fail
Supports anonymous user read-only access
Pass pass
Pass pass
Supports anonymous user read-write access
Pass pass
Fail fail
Data entry format mediawiki markup tinyMCE?
Test case re-use (write once, link anywhere)
Pass pass
using Category
Using test plans
Test case tags
Fail fail
Pass pass
Redirect links
Pass pass
Fail fail

MUST HAVE & NICE-To-HAVE

Roadmap for Transition