From Fedora Project Wiki

(Created use cases page)
 
No edit summary
Line 11: Line 11:
# Create test day schedule
# Create test day schedule
# Create new categories
# Create new categories
# Create Test result and test case template(http://fedoraproject.org/wiki/Template:Result)
# Create Test result and test case template
# Add page to related category
# Add page to related category


Host:
Host:
# Create the Wiki page Using the Test Day template  
# Create the Wiki page Using the Test Day template
## Create test cases
## Create test cases
## Set up the results table
## Set up the results table
Line 50: Line 50:
QA:
QA:
* Create test cases:
* Create test cases:
# Use test case template format
# Use test case template format: https://fedoraproject.org/wiki/Template:QA/Test_Case
# link tests to the packages they are designed to test
# link tests to the packages they are designed to test
# Use different syntax such as <nowiki><pre></pre><code></code> </nowiki>
# Use different syntax such as <nowiki><pre></pre><code></code> </nowiki>


* Initiating a test run
* Initiating a test run
# Create new test result page using test result template
# Create new test result page using test result template: http://fedoraproject.org/wiki/Template:Result
# Have key section as result example
# Have key section as result example
# Create sortable and collapse result table
# Create sortable and collapse result table

Revision as of 08:34, 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
  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: https://fedoraproject.org/wiki/Template:QA/Test_Case
  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: http://fedoraproject.org/wiki/Template:Result
  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
Retrieved from "https://fedoraproject.org/w/index.php?title=Tcms_use_cases&oldid=212678"