Tcms use cases

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