From Fedora Project Wiki

No edit summary
No edit summary
Line 65: Line 65:
## Add the page to relative category
## Add the page to relative category
## Link test cases to the page  
## Link test cases to the page  
# Create test result template
# Create test result template
## Have key section as result example: http://fedoraproject.org/wiki/Template:Result
## Have key section as result example: http://fedoraproject.org/wiki/Template:Result
Line 78: Line 77:
## Rename a test case(Move a page)
## Rename a test case(Move a page)
## Set as draft before use
## Set as draft before use
# Initiate a test run
# Initiate a test run
## Create new test result page using test result template
## Create new test result page using test result template
Line 84: Line 82:
## Redirect current link
## Redirect current link
## Move previous test results to new test run
## Move previous test results to new test run
# Create a certain page
# Create a certain page
## Edit with wiki markup
## Edit with wiki markup
Line 93: Line 90:
## Use subpages  
## Use subpages  
## Set pages as draft before use
## Set pages as draft before use
# Submit a test summary
# Submit a test summary
## Use curl command to generate bug and contribution list
## Use curl command to generate bug and contribution list
Line 105: Line 101:
## allow multiple results for each one case
## allow multiple results for each one case
## Use signatures
## Use signatures
# Search test results
# Search test results
## Search by categories
## Search by categories
Line 111: Line 106:
## Search from event main/intro page  
## Search from event main/intro page  
## Use 'what links to here of Toolbox'
## Use 'what links to here of Toolbox'
# Upload files
# Upload files
## Post images/packages
## Post images/packages

Revision as of 10:21, 29 December 2010

Wiki Use Cases

This page lists the general use cases when using wiki, which are divided by different groups, considered as different permissions.

Test Days Use Cases

  • QA:
  1. Create main/intro page of test day
  2. Create SOP guide page for hosting a test day
  3. Create Test Day template
  4. Create test day schedule
  5. Create new categories
  6. Create Test result and test case templates
  7. Add page to related category
  • Host:
  1. Create the test day 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. Summarize the event with curl command to test-announce
  • Tester(anonymous user permitted):
  1. Posts test result to the table with the template format
  2. Use the talk page for discussion

Release Validation Use case

  • QA:
  1. Create installation/desktop test plan
  2. Create/maintain Release Criteria
  3. Create main/intro 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 using template
  2. Add page to related category
  3. Set previous page as draft
  4. Use redirect link as current links
  5. Copy previous result page(results) to current
  6. Send out announcement
  7. Summarize the report using curl command
  • Tester(anonymous user permitted):
  1. Post test results using result format
  2. Use talk page for discussion

Sub use cases

  • QA:
  1. Create test plan/main page
    1. Use wiki markup
    2. Use links and rename them
    3. Manually add reviewers
    4. Manually set as draft before ready
    5. Use Templates such as FedoraVersion:
    6. Create new category
    7. Add the page to relative category
    8. Link test cases to the page
  2. Create test result template
    1. Have key section as result example: http://fedoraproject.org/wiki/Template:Result
    2. Create sortable and collapse result table
    3. Link test cases to the page
  • Host:
  1. Create test cases
    1. Use test case template format
    2. Link tests to the packages they are designed to test
    3. Use Template:Package
    4. Rename a test case(Move a page)
    5. Set as draft before use
  2. Initiate a test run
    1. Create new test result page using test result template
    2. Add test result page to relative category
    3. Redirect current link
    4. Move previous test results to new test run
  3. Create a certain page
    1. Edit with wiki markup
    2. Rollback history
    3. Preview function
    4. Compare changes between different version
    5. Use template format
    6. Use subpages
    7. Set pages as draft before use
  4. Submit a test summary
    1. Use curl command to generate bug and contribution list
    2. Send out test report to mail lists manually
  • Tester(Anonymous permission):
  1. 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
    5. Use signatures
  2. Search test results
    1. Search by categories
    2. Search by current redirect links
    3. Search from event main/intro page
    4. Use 'what links to here of Toolbox'
  3. Upload files
    1. Post images/packages
    2. Setup package repos/updates.img through SSH to fedorapeople server
  • Admin:
  1. Manage pages authority with diff namespaces
  2. FAS Integration
  3. Add some plugin to enhance some functions
  4. Protect a special page
  5. Delete a special page