From Fedora Project Wiki

No edit summary
(Redesigned the use cases)
Line 4: Line 4:
This page lists the general use cases when using wiki, which are divided by different groups, considered as different permissions.     
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: quality assurance engineer or the ones who applied the same permission level as QA
* Host: each test event organizer/host
* Tester: users with normal login permission or anonymous user
* User: general logged in users
* Admin: system administrator


* QA:
=== Creating A Common Page Use Case ===
# Create main/intro page of test day
# Create SOP guide page for hosting a test day
# Create Test Day template
# Create test day schedule
# Create new categories
# Create Test result and test case templates
# Add page to related category


* Host:
# User inputs a url to name the page  
# Create the test day page Using the Test Day template
## Or User moves a existing page to a new name
## Create test cases
# User edits the page with wiki markup
## Set up the results table
## User addresses other pages and rename the links
# Add page to related category
# User uses 'show preview' to preview the contents
# Send out announcement manually
# User compares changes from history logs
# Redirect current link: Test_Day:Current
# User undos the action by history rollback
# Summarize the event with curl command to test-announce


* Tester(anonymous user permitted):
=== Creating A Test Case Use case===
# Posts test result to the table with the template format
# Use the talk page for discussion


=== Release Validation Use case ===
# User creates a page
# User edits it to add contents using [[Template:QA/Test_Case]]
## User adds Link tests to packages using [[Template:Package]]
## User adds files by linking to it
# User adds [[Template:Draft|'draft note']] before use
# User removes the 'draft note' when approved in its trac ticket.
# User creates/searches its category
# User adds it to relative category


* QA:
=== Creating A Test Plan Use Case===
# Create installation/desktop test plan
# Create/maintain Release Criteria
# Create main/intro 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:
# User creates a test plan page by coping some of previous plan contents
# Create test result page using template
# User Uses Templates such as [[Template:FedoraVersion]]
# Add page to related category
# User creates new category
# Set previous page as draft
# User adds the page to relative category
# Use redirect link as current links
# User adds the link of test cases to the page
# Copy previous result page(results) to current
# Send out announcement
# Summarize the report using curl command


* Tester(anonymous user permitted):
=== Creating A Test Result template ===
# Post test results using result format
# Use talk page for discussion


=== Sub use cases ===
# User creates key section as result example using [[Template:Result]]
# User creates sortable and collapse result table
# User links test cases to the page


* QA:
=== Creating A Test Result ===
# 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
# Create test result template
## Have key section as result example: http://fedoraproject.org/wiki/Template:Result
## Create sortable and collapse result table
## Link test cases to the page


* Host:
# User creates result page using result template
# Create test cases
# User modifies the page to fit for the product and test event
## Use test case [https://fedoraproject.org/wiki/Template:QA/Test_Case template format]
# User copies test results from previous result page when needed
## Link tests to the packages they are designed to test
## Use Template:Package
## Rename a test case(Move a page)
## Set as draft before use
# Initiate a test run
## Create new test result page using test result template
## Add test result page to relative category
## Redirect current link
## Move previous test results to new test run
# Create a certain page
## Edit with wiki markup
## Rollback history
## Preview function
## Compare changes between different version
## Use template format
## Use subpages
## Set pages as draft before use
# Submit a test summary
## Use curl command to generate bug and contribution list
## Send out test report to mail lists manually


* Tester(Anonymous permission):
=== Post test result ===
# Post test result
## Contribute result to different platforms
## Add comments as references
## Post a bug to result
## allow multiple results for each one case
## Use signatures
# Search test results
## Search by categories
## Search by current redirect links
## Search from event main/intro page
## Use 'what links to here of Toolbox'
# Upload files
## Post images/packages
## Setup package repos/updates.img through SSH to fedorapeople server


* Admin:
# User opens current links
# Manage pages authority with diff namespaces
# User contributes result to different platforms: i386 and x86_64
# FAS Integration
# User adds comments as references
# Add some plugin to enhance some functions
# User posts a bug to result using [[Template:Bz]]
# Protect a special page
# Users post multiple results in each one case
# Delete a special page
# (Use signatures)
# License
 
=== Search test results/cases ===
 
# User searches by categories
# User searches by current redirect links
# User searches from event main/intro page
# User uses 'what links to here of Toolbox'
 
=== Uploading files ===
 
# User posts images/packages
# User creates package repos/updates.img through SSH to fedorapeople server
 
=== Submitting A Test Summary ===
 
# User uses curl command to generate bug and contribution list
# User sends out test report to mail lists manually
 
=== Administrating Use Case ===
 
# Admin manages pages authority with diff namespaces
# Admin accomplished FAS Integration with wiki
# Admin adds some plugins to enhance some functions
# Admin protects a special page
# Admin deletes a special page
# Admin manages License
 
=== Test Days Use Case ===
 
At the very beginning:
# QA creates [[QA/Test_Days|main/intro page]]
# QA creates [[QA/SOP_Test_Day_management|SOP guide page]]
# QA creates [[QA/Test_Days/Template|test day result page template]]
# QA creates new categories such as [[:Category:Test_Days]] and [[:Category:QA_Templates]]
# QA creates new templates such as [[Template:Result]] and [[Template:QA/Test_Case]]
# QA creates current test day link: [[Test_Day:Current]]
# QA adds pages to related categories
 
Then for each release development cycle:
# QA creates [[QA/Fedora_14_test_days|test day schedule]]
# QA creates new categories for the release, such as [[:Category:Fedora_15_Test_Days]]
# QA adds pages to related categories
 
Then for each test event:
# Host edits [[QA/Fedora_14_test_days|test day schedule]] to propose a test day
# Host creates a test day page Using [[QA/Test_Days/Template|test day result page template]]
# Host searches test cases from categories
# Host creates new cases using [[Template:QA/Test_Case]]
# Host adds pages to related categories
# Host redirects [[Test_Day:Current]]
# Host sends out announcement with links manually to list and irc
# Tester executes the test day
# Tester posts test result using [[Template:Result]]
# Tester uses the talk page for discussion and queries
# Host summarizes the results with curl command to community
 
=== Release Validation Test Event Use case ===
 
At the very beginning:
# QA creates [[QA:Installation_validation_testing|install]] and [[QA:Desktop_validation_testing|desktop]] validation event main/intro pages
# QA creates [[Fedora_Release_Criteria]]
# QA creates [[QA/SOP_Release_Validation_Test_Event|SOP guide page]]
# QA creates new templates such as [[Template:Result]], [[Template:Bz]], and [[Template:QA/Test_Case]]
# QA creates current test event links: [[Test_Results:Current_Installation_Test]], and [[Test_Results:Current_Desktop_Test]]
# QA creates new categories such as [[:Category:Install_Results_Templates]], and [[:Category:Release_Criteria]]
# QA adds pages to related categories
 
Then for each release development cycle:
# QA creates [[QA:Fedora_14_Install_Test_Plan|installation]]/desktop test plan
# QA creates [[QA:Fedora_14_Install_Results_Template|install]] and [[QA:Desktop_validation_results_template|desktop]] test result page templates
# QA creates [[Fedora_Release_Criteria#Current_Release_Milestones|Fedora Release Criteria for current release milestones]]
# QA creates new test cases to extend coverage
# QA creates new categories
# QA adds pages to related categories
 
Then for each test event:
# Host creates test result page using [[QA:Fedora_14_Install_Results_Template|install]] and [[QA:Desktop_validation_results_template|desktop]] templates
# Host adds 'No longer current' note to previous result pages using [[Template:Admon/tip]]
# Host redirects current links
# Host copies some previous results to current result page
# Host creates new category such as [[:Category:Fedora_14_Final_RC_Test_Results]]
# Host adds page to related category
# Host sends out test announcement with links manually
# Tester executes tests
# Test posts test results using [[Template:Result]]
# Tester uses talk page for discussion and queries
# Host summarizes results using curl command

Revision as of 09:01, 14 January 2011

Wiki Use Cases

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

  • QA: quality assurance engineer or the ones who applied the same permission level as QA
  • Host: each test event organizer/host
  • Tester: users with normal login permission or anonymous user
  • User: general logged in users
  • Admin: system administrator

Creating A Common Page Use Case

  1. User inputs a url to name the page
    1. Or User moves a existing page to a new name
  2. User edits the page with wiki markup
    1. User addresses other pages and rename the links
  3. User uses 'show preview' to preview the contents
  4. User compares changes from history logs
  5. User undos the action by history rollback

Creating A Test Case Use case

  1. User creates a page
  2. User edits it to add contents using Template:QA/Test_Case
    1. User adds Link tests to packages using Template:Package
    2. User adds files by linking to it
  3. User adds 'draft note' before use
  4. User removes the 'draft note' when approved in its trac ticket.
  5. User creates/searches its category
  6. User adds it to relative category

Creating A Test Plan Use Case

  1. User creates a test plan page by coping some of previous plan contents
  2. User Uses Templates such as Template:FedoraVersion
  3. User creates new category
  4. User adds the page to relative category
  5. User adds the link of test cases to the page

Creating A Test Result template

  1. User creates key section as result example using Template:Result
  2. User creates sortable and collapse result table
  3. User links test cases to the page

Creating A Test Result

  1. User creates result page using result template
  2. User modifies the page to fit for the product and test event
  3. User copies test results from previous result page when needed

Post test result

  1. User opens current links
  2. User contributes result to different platforms: i386 and x86_64
  3. User adds comments as references
  4. User posts a bug to result using Template:Bz
  5. Users post multiple results in each one case
  6. (Use signatures)

Search test results/cases

  1. User searches by categories
  2. User searches by current redirect links
  3. User searches from event main/intro page
  4. User uses 'what links to here of Toolbox'

Uploading files

  1. User posts images/packages
  2. User creates package repos/updates.img through SSH to fedorapeople server

Submitting A Test Summary

  1. User uses curl command to generate bug and contribution list
  2. User sends out test report to mail lists manually

Administrating Use Case

  1. Admin manages pages authority with diff namespaces
  2. Admin accomplished FAS Integration with wiki
  3. Admin adds some plugins to enhance some functions
  4. Admin protects a special page
  5. Admin deletes a special page
  6. Admin manages License

Test Days Use Case

At the very beginning:

  1. QA creates main/intro page
  2. QA creates SOP guide page
  3. QA creates test day result page template
  4. QA creates new categories such as Category:Test_Days and Category:QA_Templates
  5. QA creates new templates such as Template:Result and Template:QA/Test_Case
  6. QA creates current test day link: Test_Day:Current
  7. QA adds pages to related categories

Then for each release development cycle:

  1. QA creates test day schedule
  2. QA creates new categories for the release, such as Category:Fedora_15_Test_Days
  3. QA adds pages to related categories

Then for each test event:

  1. Host edits test day schedule to propose a test day
  2. Host creates a test day page Using test day result page template
  3. Host searches test cases from categories
  4. Host creates new cases using Template:QA/Test_Case
  5. Host adds pages to related categories
  6. Host redirects Test_Day:Current
  7. Host sends out announcement with links manually to list and irc
  8. Tester executes the test day
  9. Tester posts test result using Template:Result
  10. Tester uses the talk page for discussion and queries
  11. Host summarizes the results with curl command to community

Release Validation Test Event Use case

At the very beginning:

  1. QA creates install and desktop validation event main/intro pages
  2. QA creates Fedora_Release_Criteria
  3. QA creates SOP guide page
  4. QA creates new templates such as Template:Result, Template:Bz, and Template:QA/Test_Case
  5. QA creates current test event links: Test_Results:Current_Installation_Test, and Test_Results:Current_Desktop_Test
  6. QA creates new categories such as Category:Install_Results_Templates, and Category:Release_Criteria
  7. QA adds pages to related categories

Then for each release development cycle:

  1. QA creates installation/desktop test plan
  2. QA creates install and desktop test result page templates
  3. QA creates Fedora Release Criteria for current release milestones
  4. QA creates new test cases to extend coverage
  5. QA creates new categories
  6. QA adds pages to related categories

Then for each test event:

  1. Host creates test result page using install and desktop templates
  2. Host adds 'No longer current' note to previous result pages using Template:Admon/tip
  3. Host redirects current links
  4. Host copies some previous results to current result page
  5. Host creates new category such as Category:Fedora_14_Final_RC_Test_Results
  6. Host adds page to related category
  7. Host sends out test announcement with links manually
  8. Tester executes tests
  9. Test posts test results using Template:Result
  10. Tester uses talk page for discussion and queries
  11. Host summarizes results using curl command
Retrieved from "https://fedoraproject.org/w/index.php?title=Tcms_use_cases&oldid=215375"