From Fedora Project Wiki

No edit summary
No edit summary
Line 2: Line 2:


<!-- Identify our current test workflows (or use cases)-->
<!-- Identify our current test workflows (or 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:
=== Test Days Use Cases ===


QA:
* QA:
# Create main page of test day
# Create main/intro page of test day
# Create sop guide for hosting test day
# Create SOP guide page for hosting a test day
# Create Test Day template
# Create Test Day template
# Create test day schedule
# Create test day schedule
# Create new categories
# Create new categories
# Create Test result and test case template
# Create Test result and test case templates
# Add page to related category
# Add page to related category
# Set previous page as draft
# Use subpages


Host:
* Host:
# Create the Wiki page Using the Test Day template
# Create the test day page Using the Test Day template
## Create test cases
## Create test cases
## Set up the results table
## Set up the results table
Line 23: Line 22:
# Send out announcement manually  
# Send out announcement manually  
# Redirect current link: Test_Day:Current  
# Redirect current link: Test_Day:Current  
# Summary the event with curl command to test-announce
# Summarize the event with curl command to test-announce


Tester(anonymous user permitted):
* Tester(anonymous user permitted):
# Posts test result to the table with the template format
# Posts test result to the table with the template format
# Use the talk page for discussion


* Release Validation Use case:
=== Release Validation Use case ===


QA:
* QA:
# Create installation/desktop test plan
# Create installation/desktop test plan
# Create and Update Release Criteria
# Create/maintain Release Criteria
# Create main introduction page
# Create main/intro page
# Create new categories
# Create new categories
# Create new test cases
# Create new test cases
Line 40: Line 40:
# Add page to related category
# Add page to related category


Host:
* Host:
# Create test result page
# Create test result page using template
# Add page to related category
# Add page to related category
# Set previous page as draft
# Use redirect link as current links
# Use redirect link as current links
# Copy previous result page(results) to current
# Send out announcement
# Send out announcement
# Summarize the report manually
# Summarize the report using curl command
 
* Tester(anonymous user permitted):
# Post test results using result format
# Use talk page for discussion
 
=== Sub use cases ===
 
* QA:
# Create test plan/main page
## Use wiki markup
## Use links and rename them
## Manually add reviewers
## Manually set as draft before ready
## Use Templates such as FedoraVersion:
## Create new category
## Add the page to relative category
## Link test cases to the page


Tester(anonymous user permitted):
# Create test result template
# Execute tests and post test results
## Have key section as result example: http://fedoraproject.org/wiki/Template:Result
## Create sortable and collapse result table
## Link test cases to the page


QA:
* Host:
* Create test cases:
# Create test cases
# Use test case template format: https://fedoraproject.org/wiki/Template:QA/Test_Case
## Use test case [https://fedoraproject.org/wiki/Template:QA/Test_Case template format]
# link tests to the packages they are designed to test
## Link tests to the packages they are designed to test
# Use wiki markup
## Use Template:Package
# Use Template:Package
## Rename a test case(Move a page)
# Rename a test case(Move a page)
## Set as draft before use


* Create test plan
# Initiate a test run
# Use wiki markup
## Create new test result page using test result template
# Use links and rename them
## Add test result page to relative category
# Manually add reviewers
## Redirect current link
# Manually set as draft before ready
## Move previous test results to new test run
# Use Template:FedoraVersion:


* Initiating a test run
# Create a certain page
# Create new test result page using test result template: http://fedoraproject.org/wiki/Template:Result
## Edit with wiki markup
# Have key section as result example
## Rollback history
# Create sortable and collapse result table
## Preview function
# Use links to the page
## Compare changes between different version
# add test result page to relative category
## Use template format
# Redirect link
## Use subpages
# Move previous test results to new test run
## Set pages as draft before use


* Submitting 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
# Send out test report  
## Send out test report to mail lists manually


* Create a new page
* Tester(Anonymous permission):
# Edit with permission
# Post test result
# Use wiki syntax
## Contribute result to different platforms
# Rollback history
## Add comments as references
# Preview function
## Post a bug to result
# Compare changes between different version
## allow multiple results for each one case
# View history editing records
## Use signatures
# Use template format


* Upload files
# Search test results
# Post images/packages
## Search by categories
# Setup package repos/updates.img through SSH to fedorapeople server
## Search by current redirect links
## Search from event main/intro page
## Use 'what links to here of Toolbox'


Tester:
# Upload files
* Post test result:
## Post images/packages
# Contribute result to different platforms
## Setup package repos/updates.img through SSH to fedorapeople server
# Add comments as references
# Post a bug to result
# allow multiple results for each one case
# Use signatures


Admin:
* Admin:
# Manage pages authority with diff namespaces
# Manage pages authority with diff namespaces
# FAS Integration
# FAS Integration

Revision as of 10:19, 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
  1. 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
  1. 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
  1. 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
  1. 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
  1. 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'
  1. 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
Retrieved from "https://fedoraproject.org/w/index.php?title=Tcms_use_cases&oldid=213097"