Tcms use cases: Difference between revisions

Latest revision as of 23:06, 8 July 2014

This page aims to identify current wiki test workflows. It lists general use cases when using wiki and summarizes main test events use cases step by step.

General Use Cases

User: general logged in users
Admin: system administrator

Creating A Generic Page

User inputs a url to open the page
- Or User moves an existing page to a new one
User edits the page with wiki markup
- User addresses other pages and rename the links
- User uses existing templates
User uses 'show preview' to preview the contents
User uses talk page for discussion
User compares changes from history logs
User undoes changes by history rollback
User creates/searches its category
User adds it to relative category
User adds it to watchlist

Creating A Test Case

User creates a page
- Or user moves an existing case to a new name
User edits it using Template:QA/Test_Case
- User adds Link tests to packages using Template:Package
- User adds files by linking to it
User adds 'draft note' before use
User removes the 'draft note' when approved in its trac ticket or somewhere else.
User adds the case to category

Creating A Test Plan

User creates a page by coping some of previous plan contents
User edits the page
User adds the link of test cases to the page
User adds 'draft note' before use
Reviewers reviews it and adds review time on the page
User removes the 'draft note'
User adds the plan to category

Creating A Test Result Page(Test Run) Template

User creates a page
User creates key section as result example using Template:Result
User creates sortable and collapse result table
User links test cases to the page
- User groups the cases to different sections
User adds the template to category

Creating A Test Result Page(Test Run)

User creates result page with certain namespace(Test_Day, Test_Results etc) using result page template
User modifies the page to fit for the product and test event
User copies test results from previous result page when needed
User adds the result page to category
User redirects current link to the result page

Posting test results

User opens current link page
User contributes result to the matrices using Template:Result
User adds comments as references
User posts a bug to result using Template:Bz
Users post multiple results in each one case
(User signatures)

Searching test results/cases/plans

User searches by categories
User searches by current redirect links
User searches from event main/intro page
User searches from schedule
User searches from watchlist
User uses 'what links to here of Toolbox'

Uploading files

User posts images/tar 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

Admin manages pages authority with diff namespaces
Admin implements FAS Integration with wiki
Admin adds some plugins to enhance some functions
Admin protects a special page
Admin deletes a special page
Admin manages Licensing for the tcms
Admin licenses the contents
Admin implements our update tools (bodhi/f-e-k) integration with wiki
Admin provides actively upstream project community

Test Events 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

Test Days

At the very beginning:

QA creates main/intro page
QA creates SOP guide page
QA creates 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 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 test day schedule to propose a test day
Host creates a test day page Using 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

At the very beginning:

QA creates Fedora_Release_Criteria
QA creates [[1]] validation event main/intro pages
QA creates 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 installation/desktop test plan
QA creates Fedora Release Criteria for current release milestones
QA creates install and desktop test result page templates
- QA sets priorities for the cases
- QA creates results area for different platforms: i386 and x86_64
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 install and 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

Reference

Wiki and Nitrate features Comparison Page

@@ Line 1: / Line 1: @@
-== Wiki Use Cases ==
+<!-- Identify our current test workflows (or use cases)-->
+This page aims to identify current wiki test workflows. It lists general use cases when using wiki and summarizes main test events use cases step by step.
+== General Use Cases ==
+* User: general logged in users
+* Admin: system administrator
+=== Creating A Generic Page ===
+# User inputs a url to open the page
+#* Or User moves an existing page to a new one
+# User edits the page with wiki markup
+#* User addresses other pages and rename the links
+#* User uses existing templates
+# User uses 'show preview' to preview the contents
+# User uses talk page for discussion
+# User compares changes from history logs
+# User undoes changes by history rollback
+# User creates/searches its category
+# User adds it to relative category
+# User adds it to watchlist
+=== Creating A Test Case ===
+# User creates a page
+#* Or user moves an existing case to a new name
+# User edits it 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 or somewhere else.
+# User adds the case to category
+=== Creating A Test Plan ===
+# User creates a page by coping some of previous plan contents
+# User edits the page
+# User adds the link of test cases to the page
+# User adds [[Template:Draft|'draft note']] before use
+# Reviewers reviews it and adds review time on the page
+# User removes the 'draft note'
+# User adds the plan to category
+=== Creating A Test Result Page(Test Run) Template ===
-<!-- Identify our current test workflows (or use cases)-->
+# User creates a page
+# User creates key section as result example using [[Template:Result]]
+# User creates sortable and collapse result table
+# User links test cases to the page
+#* User groups the cases to different sections
+# User adds the template to category
+=== Creating A Test Result Page(Test Run) ===
+# User creates result page with certain namespace(Test_Day, Test_Results etc) using result page template
+# User modifies the page to fit for the product and test event
+# User copies test results from previous result page when needed
+# User adds the result page to category
+# User redirects current link to the result page
+=== Posting test results ===
+# User opens current link page
+# User contributes result to the matrices using [[Template:Result]]
+# User adds comments as references
+# User posts a bug to result using [[Template:Bz]]
+# Users post multiple results in each one case
+# (User signatures)
+=== Searching test results/cases/plans ===
+* User searches by categories
+* User searches by current redirect links
+* User searches from event main/intro page
+* User searches from schedule
+* User searches from watchlist
+* User uses 'what links to here of Toolbox'
+=== Uploading files ===
-* Test Days Use cases:
+# User posts images/tar packages
+# User creates package repos/updates.img through SSH to fedorapeople server
-QA:
+=== Submitting A Test Summary ===
-# 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
-# Add page to related category
-# Set previous page as draft
-# Use subpages
-Host:
+# User uses curl command to generate bug and contribution list
-# Create the Wiki page Using the Test Day template
+# User sends out test report to mail lists manually
-## 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):
+=== Administrating ===
-# Posts test result to the table with the template format
-* Release Validation Use case:
+* Admin manages pages authority with diff namespaces
+* Admin implements FAS Integration with wiki
+* Admin adds some plugins to enhance some functions
+* Admin protects a special page
+* Admin deletes a special page
+* Admin manages Licensing for the tcms
+* Admin licenses the contents
+* Admin implements our update tools (bodhi/f-e-k) integration with wiki
+* Admin provides actively upstream project community
-QA:
+== Test Events Use Cases ==
-# 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:
+* QA: quality assurance engineer or the ones who applied the same permission level as QA
-# Create test result page
+* Host: each test event organizer/host
-# Add page to related category
+* Tester: users with normal login permission or anonymous user
-# Use redirect link as current links
-# Send out announcement
-# Summarize the report manually
-Tester(anonymous user permitted):
+=== Test Days ===
-# Execute tests and post test results
-QA:
+At the very beginning:
-* Create test cases:
+# QA creates [[QA/Test_Days|main/intro page]]
-# Use test case template format: https://fedoraproject.org/wiki/Template:QA/Test_Case
+# QA creates [[QA/SOP_Test_Day_management|SOP guide page]]
-# link tests to the packages they are designed to test
+# QA creates [[QA/Test_Days/Template|test day result page template]]
-# Use wiki markup
+# QA creates new categories such as [[:Category:Test_Days]] and [[:Category:QA_Templates]]
-# Use Template:Package
+# QA creates new templates such as [[Template:Result]] and [[Template:QA/Test_Case]]
-# Rename a test case(Move a page)
+# QA creates current test day link: [[Test_Day:Current]]
+# QA adds pages to related categories
-* Create test plan
+Then for each release development cycle:
-# Use wiki markup
+# QA creates [[QA/Fedora_14_test_days|test day schedule]]
-# Use links and rename them
+# QA creates new categories for the release, such as [[:Category:Fedora_15_Test_Days]]
-# Manually add reviewers
+# QA adds pages to related categories
-# Manually set as draft before ready
-# Use Template:FedoraVersion:
-* Initiating a test run
+Then for each test event:
-# Create new test result page using test result template: http://fedoraproject.org/wiki/Template:Result
+# Host edits [[QA/Fedora_14_test_days|test day schedule]] to propose a test day
-# Have key section as result example
+# Host creates a test day page Using [[QA/Test_Days/Template|test day result page template]]
-# Create sortable and collapse result table
+# Host searches test cases from categories
-# Use links to the page
+# Host creates new cases using [[Template:QA/Test_Case]]
-# add test result page to relative category
+# Host adds pages to related categories
-# Redirect link
+# Host redirects [[Test_Day:Current]]
-# Move previous test results to new test run
+# 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
-* Submitting a test summary
+=== Release Validation Test Event ===
-# Use curl command to generate bug and contribution list
-# Send out test report
-* Create a new page
+At the very beginning:
-# Edit with permission
+# QA creates [[Fedora_Release_Criteria]]
-# Use wiki syntax
+# QA creates [[https://fedoraproject.org/wiki/QA:Release_validation_test_plan]] validation event main/intro pages
-# Rollback history
+# QA creates [[QA/SOP_Release_Validation_Test_Event|SOP guide page]]
-# Preview function
+# QA creates new templates such as [[Template:Result]], [[Template:Bz]], and [[Template:QA/Test_Case]]
-# Compare changes between different version
+# QA creates current test event links: [[Test_Results:Current_Installation_Test]], and [[Test_Results:Current_Desktop_Test]]
-# View history editing records
+# QA creates new categories such as [[:Category:Install_Results_Templates]], and [[:Category:Release_Criteria]]
-# Use template format
+# QA adds pages to related categories
-* Upload files
+Then for each release development cycle:
-# Post images/packages
+# QA creates [[QA:Fedora_14_Install_Test_Plan|installation]]/desktop test plan
-# Setup package repos/updates.img through SSH to fedorapeople server
+# QA creates [[Fedora_Release_Criteria#Current_Release_Milestones|Fedora Release Criteria for current release milestones]]
+# QA creates [[QA:Fedora_14_Install_Results_Template|install]] and [[QA:Desktop_validation_results_template|desktop]] test result page templates
+#* QA sets priorities for the cases
+#* QA creates results area for different platforms: i386 and x86_64
+# QA creates new test cases to extend coverage
+# QA creates new categories
+# QA adds pages to related categories
-Tester:
+Then for each test event:
-* Post test result:
+# Host creates test result page using [[QA:Fedora_14_Install_Results_Template|install]] and [[QA:Desktop_validation_results_template|desktop]] templates
-# Contribute result to different platforms
+# Host adds 'No longer current' note to previous result pages using [[Template:Admon/tip]]
-# Add comments as references
+# Host redirects current links
-# Post a bug to result
+# Host copies some previous results to current result page
-# allow multiple results for each one case
+# Host creates new category such as [[:Category:Fedora_14_Final_RC_Test_Results]]
-# Use signatures
+# 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
-Admin:
+== Reference ==
-# Manage pages authority with diff namespaces
+[[Tcms_Comparison|Wiki and Nitrate features Comparison Page]]
-# FAS Integration
-# Add some plugin to enhance some functions
-# Protect a special page
-# Delete a special page