From Fedora Project Wiki

No edit summary
No edit summary
Line 1: Line 1:
== Wiki Use Cases ==
<!-- Identify our current test workflows (or use cases)-->
* Test Days Use cases:
QA:
# Create main page of test day
# Create sop guide for hosting test day
# Create Test Day template
# Create test day schedule
# Create new categories
# Create Test result and test case template(http://fedoraproject.org/wiki/Template:Result)
# Add page to related category
Host:
# Create the Wiki page Using the Test Day template
## Create test cases
## Set up the results table
# Add page to related category
# Send out announcement manually
# Redirect current link: Test_Day:Current
# Summary the event with curl command to test-announce
Tester(anonymous user permitted):
# Posts test result to the table with the template format
* Release Validation Use case:
QA:
# Create installation/desktop test plan
# Create and Update Release Criteria
# Create main introduction page
# Create new categories
# Create new test cases
# Create test result template
# Create templates format for cases and results
# Add page to related category
Host:
# Create test result page
# Add page to related category
# Use redirect link as current links
# Send out announcement
# Summarize the report manually
Tester(anonymous user permitted):
# 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 99: Line 11:
<!-- 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-->
* Link format
Page Tabs:
* Default for all users
** “namespace” (page, help, special page, template, user page etc.)
** “discussion”
** “edit” (may read “view source” if anonymous editing is disabled, the page is in the MediaWiki: namespace, or the page is protected)
** “history”
*Extra tabs for logged-in users
** “move”
** “watch”
* Extra tabs for sysops
** “protect”
** “delete”
User links:
* “<username>”: This links to your user page which is where you can put information about yourself, store bits of information you want to remember or whatever else you fancy.
* “my talk”: This links to your discussion page, where people can leave messages for you.
* “my preferences”: Allows you to change your personal site preferences.
* “my watchlist”: A list of all pages that you are watching. Pages can be added to this list by clicking “watch” at the top of the page.
* “my contributions”: A list of all contributions you have made to the wiki.
* “log out”: Click this link to log out of the wiki.


{| class="wikitable sortable"  
{| class="wikitable sortable"  

Revision as of 11:38, 27 December 2010

Cons for Wiki-based TCMS

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

Comparison

  • Link format

Page Tabs:

  • Default for all users
    • “namespace” (page, help, special page, template, user page etc.)
    • “discussion”
    • “edit” (may read “view source” if anonymous editing is disabled, the page is in the MediaWiki: namespace, or the page is protected)
    • “history”
  • Extra tabs for logged-in users
    • “move”
    • “watch”
  • Extra tabs for sysops
    • “protect”
    • “delete”

User links:

  • “<username>”: This links to your user page which is where you can put information about yourself, store bits of information you want to remember or whatever else you fancy.
  • “my talk”: This links to your discussion page, where people can leave messages for you.
  • “my preferences”: Allows you to change your personal site preferences.
  • “my watchlist”: A list of all pages that you are watching. Pages can be added to this list by clicking “watch” at the top of the page.
  • “my contributions”: A list of all contributions you have made to the wiki.
  • “log out”: Click this link to log out of the wiki.
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

Retrieved from "https://fedoraproject.org/w/index.php?title=Rhe/tcms_requirements_proposal_draft&oldid=212861"