Tcms Comparison: Difference between revisions

Revision as of 09:59, 18 January 2011

Comparison

Feature	fedoraproject.org/wiki	nitrate
Creating A Common Page
Any page creation	pass	fail Can only create test case/plan/run
Readable link names	pass human-readable link names	fail use ID for identification
Data entry format	mediawiki markup	tinyMCE
Moving a Page	pass by redirect links	pass by cloning or changing the summary(name) of case/plan/run
Templates creation/use	pass such as Special:MostLinkedTemplates	fail
Editting preview	pass	fail
Submitting format	fail wiki syntax	pass form format
Talk page	pass	warn Can only add comments in test cases
History rollback	pass	fail Only offer change logs
Changes comparison	pass	warn Only offer change logs
Categories creation	pass manually add new category	warn cases categories can be added by Admin
Adding pages to categories	pass manually add category	warn Only cases have categories
Subpage using	pass	Unknown unknown by Tree View?
Bookmarks/watchlist	pass watch the page	pass bookmark the page
Creating a test case
Renaming a case	fail move to another page	pass change the summary
Test case template	pass Template:QA/Test_Case	pass Defined
Linking files/packages/images	pass Upload somewhere and link to it	pass Test cases/plans support attachments
Case draft status	fail manually add draft category/note	pass Set as PROPOSED or NEED_UPDATE
Case review status	fail approved in ticket or somewhere else	pass Set as CONFIRMED
Categorizing cases	pass manually add to category	pass add category or use tag or add to plan to group cases
Description part in test case	pass	fail only have setup and notes parts
Tests that impact multiple packages	warn Categories could be used to organize this data, but get messy	pass allows linking tests to the packages they are designed to test
Test case re-use (write once, link anywhere)	pass search from Category and link to it	pass clone from other plans
Creating A Test Plan
Test Plan re-use/update	pass copy contents from previous	pass clone previous plans
Linking test cases	pass linking to cases section on test result template page	pass clone from other plans
Plan draft status	fail manually add draft category/note	fail Set as non-active?
Plan review status	fail manually add reviewer and review time	fail Set as active
Categorizing plans	pass manually add to category	pass no category for plan but have Plan Type and Tag etc.
Creating A Test Result Page Template
Result Page Template	pass	fail doesn't support result page template creation. Test run(result page) can be cloned from previous run with modifications.
Sortable table	pass	pass using sort
Collapse table	warn hard to manage as a whole	pass
Group cases (by media)	pass flexible wiki design	fail
Each case with different platforms	pass	fail ?? two test runs for both platforms?
Creating A Test Result Page
Test result page creation	pass	pass Create a test run
Moving test results	pass manually copy	fail manually add one by one?
Redirecting links	pass redirect links to current result page	fail set test run as running or finished
Categorizing runs/result pages	pass manually add to category	pass Can set 'product', 'version' and 'tag' etc
Posting test results
Opening 'current' links	pass Open current links	fail search my runs(how?) or the run's ID
Result format	pass use Template:Result	pass defined
Comment as references	pass	pass
Bug posting	pass use Template:Bz	pass
Multiple contributions for each case	pass	fail only display the last modified one
*Signatures using	pass ~~~~ -> Rhe 09:59, 18 January 2011 (UTC)	fail
Searching test results/cases/plans
Searching cases/plans/runs	fail only by searching from categories or name	pass advanced search
Toolbox(what links to here)	pass	pass plans, cases, and runs related to each other
Uploading Files
Upload files/packages/images	pass upload somewhere and link to it	warn test cases/plans support attachments(test run doesn't)
Upload updates.img/repo to certain server	pass fedorapeople server	fail link to wiki.
Generating A Test Summary
Result summary/report generation	fail run curl command	pass automatic
Administrating
Authorities for pages	pass Use namespaces	Unknown unknown Can admin configure it?
Supporting anonymous user read-only access	pass	pass
Supporting anonymous user read-write access	pass	fail
Integration with FAS	pass	Unknown unknown
Feature extension	pass Add plugin	Unknown unknown Add plugin?
Page protection	pass by Admin	Unknown unknown
Case/plan deletion	pass by Admin	pass Set as DISABLED. Test run can be deleted.
License	Unknown unknown	Unknown unknown
Test Days
Test day main/intro page	pass	fail link to wiki.
Test day SOP guide page	pass	fail link to wiki.
Test day/event result template page	pass	fail Clone from previous test run.
Test day schedule	pass	fail link to wiki.
Test day notification	fail send out announcement manually	warn Assign through mail, but the content is very brief.
Release Validation Test Event
Test event Main/intro page	pass	fail link to wiki.
Test event SOP guide page	pass	fail link to wiki.
test event Result template page	pass	fail Clone from previous test run.
Release Criteria page	pass	fail link to wiki.
Test cases priority	fail manually add priority before each case link	warn from P1 to P5, need change to: Alpha, Beta, Final.
Roadmap for each run	fail	pass

@@ Line 13: / Line 13: @@
 |style="background-color:lightgreen;"| {{result|pass}}
 |style="background-color:tomato;"| {{result|fail}} Can only create test case/plan/run
+|-
+| Readable link names
+|style="background-color:lightgreen;"| {{result|pass}} human-readable link names
+|style="background-color:tomato;"| {{result|fail}} use ID for identification
 |-
 | Data entry format
@@ Line 21: / Line 25: @@
 |style="background-color:lightgreen;"| {{result|pass}} by redirect links
 |style="background-color:lightgreen;"| {{result|pass}} by cloning or changing the summary(name) of case/plan/run
-|-
-| Renaming a link
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}}
 |-
 | Templates creation/use
@@ Line 61: / Line 61: @@
 |style="background-color:lightgreen;"| {{result|pass}}
 |style="background-color:white;"| {{result|unknown}} by Tree View?
-|-
-| link names
-|style="background-color:lightgreen;"| {{result|pass}} human-readable link names
-|style="background-color:tomato;"| {{result|fail}} use ID for identification
 |-
 | Bookmarks/watchlist
@@ Line 71: / Line 67: @@
 |-
 ! colspan=3|Creating a test case
+|-
+| Renaming a case
+|style="background-color:tomato;"| {{result|fail}} move to another page
+|style="background-color:lightgreen;"| {{result|pass}}change the summary
 |-
 | Test case template
@@ Line 80: / Line 80: @@
 |style="background-color:lightgreen;"| {{result|pass}} Test cases/plans support attachments
 |-
-| Draft status
+| Case draft status
 |style="background-color:tomato;"| {{result|fail}} manually add draft category/note
 |style="background-color:lightgreen;"| {{result|pass}} Set as PROPOSED or NEED_UPDATE
 |-
-| Review status
+| Case review status
 |style="background-color:tomato;"| {{result|fail}} approved in ticket or somewhere else
 |style="background-color:lightgreen;"| {{result|pass}} Set as CONFIRMED
 |-
-| Test case re-use (write once, link anywhere)
+| Categorizing cases
-|style="background-color:lightgreen;"| {{result|pass}} search from Category and link to it
+|style="background-color:lightgreen;"| {{result|pass}} manually add to category
-|style="background-color:lightgreen;"| {{result|pass}} clone from other plans
-|-
-| Rename a case
-|style="background-color:tomato;"| {{result|fail}} move to another page
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Adding cases to categories
-|style="background-color:lightgreen;"| {{result|pass}} manually add category
 |style="background-color:lightgreen;"| {{result|pass}} add category or use tag or add to plan to group cases
 |-
@@ Line 107: / Line 99: @@
 |style="background-color:lightgreen;"| {{result|warn}} Categories could be used to organize this data, but get messy
 |style="background-color:lightgreen;"| {{result|pass}} allows linking tests to the packages they are designed to test
+|-
+| Test case re-use (write once, link anywhere)
+|style="background-color:lightgreen;"| {{result|pass}} search from Category and link to it
+|style="background-color:lightgreen;"| {{result|pass}} clone from other plans
 |-
 ! colspan=3|Creating A Test Plan
@@ Line 118: / Line 114: @@
 |style="background-color:lightgreen;"| {{result|pass}} clone from other plans
 |-
-| Draft status
+| Plan draft status
 |style="background-color:tomato;"| {{result|fail}} manually add draft category/note
-|style="background-color:lightgreen;"| {{result|pass}} Set as PROPOSED or NEED_UPDATE
+|style="background-color:tomato;"| {{result|fail}} Set as non-active?
 |-
-| Review status
+| Plan review status
 |style="background-color:tomato;"| {{result|fail}} manually add reviewer and review time
-|style="background-color:lightgreen;"| {{result|pass}} Set as CONFIRMED
+|style="background-color:tomato;"| {{result|fail}} Set as active
 |-
-| Adding plan to categories
+| Categorizing plans
-|style="background-color:lightgreen;"| {{result|pass}} manually add category
+|style="background-color:lightgreen;"| {{result|pass}} manually add to category
 |style="background-color:lightgreen;"| {{result|pass}} no category for plan but have Plan Type and Tag etc.
 |-
@@ Line 158: / Line 154: @@
 |style="background-color:lightgreen;"| {{result|pass}} Create a test run
 |-
-| Move test results
+| Moving test results
 |style="background-color:lightgreen;"| {{result|pass}} manually copy
 |style="background-color:tomato;"| {{result|fail}} manually add one by one?
@@ Line 165: / Line 161: @@
 |style="background-color:lightgreen;"| {{result|pass}} redirect links to current result page
 |style="background-color:tomato;"| {{result|fail}} set test run as running or finished
+|-
+| Categorizing runs/result pages
+|style="background-color:lightgreen;"| {{result|pass}} manually add to category
+|style="background-color:lightgreen;"| {{result|pass}} Can set 'product', 'version' and 'tag' etc
 |-
 !colspan=3|Posting test results
@@ Line 189: / Line 189: @@
 |-
 | *Signatures using
-|style="background-color:lightgreen;"| {{result|pass}}
+|style="background-color:lightgreen;"| {{result|pass}} <nowiki>~~~~</nowiki> -> [[User:Rhe|Rhe]] 09:59, 18 January 2011 (UTC)
-|style="background-color:white;"| {{result|unknown}}
+|style="background-color:white;"| {{result|fail}}
 |-
 ! colspan=3|Searching test results/cases/plans
@@ Line 205: / Line 205: @@
 |-
 | Upload files/packages/images
-|style="background-color:lightgreen;"| {{result|pass}}
+|style="background-color:lightgreen;"| {{result|pass}} upload somewhere and link to it
 |style="background-color:lightgreen;"| {{result|warn}} test cases/plans support attachments(test run doesn't)
 |-
@@ Line 254: / Line 254: @@
 ! colspan=3|Test Days
 |-
-| Main/intro page
+| Test day main/intro page
 |style="background-color:lightgreen;"| {{result|pass}}
 |style="background-color:tomato;"| {{result|fail}} link to wiki.
 |-
-| SOP guide page
+| Test day SOP guide page
 |style="background-color:lightgreen;"| {{result|pass}}
 |style="background-color:tomato;"| {{result|fail}}link to wiki.
@@ Line 270: / Line 270: @@
 |style="background-color:tomato;"| {{result|fail}} link to wiki.
 |-
-| Test notification
+| Test day notification
 |style="background-color:tomato;"| {{result|fail}} send out announcement manually
 |style="background-color:lightgreen;"| {{result|warn}} Assign through mail, but the content is very brief.
-|-
-| Table format
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}} no syntax needed!
 |-
 ! colspan=3|Release Validation Test Event
 |-
-| Main/intro page
+| Test event Main/intro page
 |style="background-color:lightgreen;"| {{result|pass}}
 |style="background-color:tomato;"| {{result|fail}} link to wiki.
 |-
-| SOP guide page
+| Test event SOP guide page
 |style="background-color:lightgreen;"| {{result|pass}}
 |style="background-color:tomato;"| {{result|fail}}link to wiki.
 |-
-| Result template page
+| test event Result template page
 |style="background-color:lightgreen;"| {{result|pass}}
 |style="background-color:tomato;"| {{result|fail}} Clone from previous test run.
@@ Line 295: / Line 291: @@
 |style="background-color:lightgreen;"| {{result|pass}}
 |style="background-color:tomato;"| {{result|fail}} link to wiki.
-|-
-| Test case re-use (write once, link anywhere)
-|style="background-color:lightgreen;"| {{result|pass}} using Category
-|style="background-color:lightgreen;"| {{result|pass}} Using test plans
-|-
-| Test case/plans tags
-|style="background-color:tomato;"| {{result|fail}}
-|style="background-color:lightgreen;"| {{result|pass}}
 |-
 | Test cases priority
@@ Line 312: / Line 300: @@
 |style="background-color:lightgreen;"| {{result|pass}}
 |}
-----
-<!--
-{| class="wikitable sortable"
-|-
-! Feature !! fedoraproject.org/wiki !! nitrate
-|-
-| Wiki markup
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}}
-|-
-| Rename the links
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Review status
-|style="background-color:tomato;"| {{result|fail}} manually add review time
-|style="background-color:lightgreen;"| {{result|pass}} Set as CONFIRMED
-|-
-| Draft status
-|style="background-color:tomato;"| {{result|fail}} manually add draft category/note
-|style="background-color:lightgreen;"| {{result|pass}} Set as PROPOSED or NEED_UPDATE
-|-
-| Templates
-|style="background-color:lightgreen;"| {{result|pass}} such as result, case format, fedora version
-|style="background-color:tomato;"| {{result|fail}} Defined
-|-
-| Test case re-use (write once, link anywhere)
-|style="background-color:lightgreen;"| {{result|pass}} using Category
-|style="background-color:lightgreen;"| {{result|pass}} clone from other plans
-|-
-| Categories adding
-|style="background-color:lightgreen;"| {{result|pass}} manually add new category
-|style="background-color:lightgreen;"| {{result|pass}} by Admin
-|-
-| Add cases to categories
-|style="background-color:lightgreen;"| {{result|pass}} manually add category
-|style="background-color:lightgreen;"| {{result|pass}} Either add category or use tag or add to plan
-|-
-| Sortable table
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}} using sort
-|-
-| Collapse table
-|style="background-color:lightgreen;"| {{result|warn}} hard to manage as a whole
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Test case template
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Rename a case
-|style="background-color:tomato;"| {{result|fail}} move to another page
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Use template page
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}} Clone from previous run
-|-
-| Redirect links
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}} set test run as running or finished
-|-
-| Move test results
-|style="background-color:lightgreen;"| {{result|pass}} manually copy
-|style="background-color:tomato;"| {{result|fail}} manually add one by one?
-|-
-| History rollback
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}}  only have change log for reference
-|-
-| Editting preview
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}}
-|-
-| changes comparison
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|warn}} Only have change logs
-|-
-| Subpage using
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:white;"| {{result|unknown}} by Tree View?
-|-
-| Result summary/report
-|style="background-color:tomato;"| {{result|fail}}
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Results for diff platforms
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}} ?? two test runs for both platforms?
-|-
-| Comment as references
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Result format
-|style="background-color:lightgreen;"| {{result|pass}} use result template
-|style="background-color:lightgreen;"| {{result|pass}} defined
-|-
-| Bug posting
-|style="background-color:lightgreen;"| {{result|pass}} use bug template
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Multiple contributions for each case
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}} only display the last modified one
-|-
-| *Signatures using
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:white;"| {{result|unknown}}
-|-
-| Search tests/plans
-|style="background-color:tomato;"| {{result|fail}} by categories or name
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Main/intro page
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}} link to wiki.
-|-
-| Toolbox(what links to here)
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}} plans, cases, and runs related to each other
-|-
-| Upload files/packages/images
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|warn}} test cases/plans support attachments(test run doesn't)
-|-
-| Upload updates.img/repo to certain server
-|style="background-color:lightgreen;"| {{result|pass}} fedorapeople server
-|style="background-color:tomato;"| {{result|fail}} link to wiki.
-|-
-| Authorities for pages
-|style="background-color:lightgreen;"| {{result|pass}} Use namespaces
-|style="background-color:white;"| {{result|unknown}} Can admin configure it?
-|-
-| Feature extension
-|style="background-color:lightgreen;"| {{result|pass}} Add plugin
-|style="background-color:white;"| {{result|unknown}} Add plugin?
-|-
-| Page protection
-|style="background-color:lightgreen;"| {{result|pass}} by Admin
-|style="background-color:white;"| {{result|unknown}}
-|-
-| Case/plan deletion
-|style="background-color:lightgreen;"| {{result|pass}} by Admin
-|style="background-color:lightgreen;"| {{result|pass}} Set as DISABLED. Test run can be deleted.
-|-
-| SOP guide page
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}}link to wiki.
-|-
-| Test day/event result template page
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}} Clone from previous test run.
-|-
-| Test day schedule
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}} link to wiki.
-|-
-| Test notification
-|style="background-color:tomato;"| {{result|fail}} send out announcement manually
-|style="background-color:lightgreen;"| {{result|warn}} Assign through mail, but the content is very brief.
-|-
-| Table format
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}} no syntax needed!
-|-
-| Submitting format
-|style="background-color:tomato;"| {{result|fail}} wiki syntax
-|style="background-color:lightgreen;"| {{result|pass}} form format
-|-
-| Talk page
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|warn}} User can add comments in test cases
-|-
-| Release Criteria page
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}} link to wiki.
-|-
-| License
-|style="background-color:white;"| {{result|unknown}}
-|style="background-color:white;"| {{result|unknown}}
-|-
-| Integration with [https://admin.fedoraproject.org/accounts/ FAS]
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:white;"| {{result|unknown}}
-|-
-| Supports anonymous user read-only access
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Supports anonymous user read-write access
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}}
-|-
-| Data entry format
-|style="background-color:lightgreen;"| [http://www.mediawiki.org/wiki/Help:Formatting mediawiki markup]
-|style="background-color:lightgreen;"| [http://tinymce.moxiecode.com/ tinyMCE]
-|-
-| Test case re-use (write once, link anywhere)
-|style="background-color:lightgreen;"| {{result|pass}} using Category
-|style="background-color:lightgreen;"| {{result|pass}} Using test plans
-|-
-| Test case/plans tags
-|style="background-color:tomato;"| {{result|fail}}
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Bookmarks
-|style="background-color:tomato;"| {{result|fail}}
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Test case priority
-|style="background-color:tomato;"| {{result|fail}} manually add priority before each case link
-|style="background-color:lightgreen;"| {{result|warn}} from P1 to P5, need change to: Alpha, Beta, Final.
-|-
-| Tests that impact multiple packages
-|style="background-color:lightgreen;"| {{result|warn}} Categories could be used to organize this data, but get messy
-|style="background-color:lightgreen;"| {{result|pass}} allows linking tests to the packages they are designed to test
-|-
-| Test case/plan attachments
-|style="background-color:tomato;"| {{result|fail}} uploaded somewhere and link to it
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Roadmap for each run
-|style="background-color:tomato;"| {{result|fail}}
-|style="background-color:lightgreen;"| {{result|pass}}
-|-
-| Group cases by media
-|style="background-color:lightgreen;"| {{result|pass}}flexible design
-|style="background-color:tomato;"| {{result|fail}}
-|-
-| Description part in test case
-|style="background-color:lightgreen;"| {{result|pass}}
-|style="background-color:tomato;"| {{result|fail}} only have setup and notes parts
-|-
-| link names
-|style="background-color:lightgreen;"| {{result|pass}} human-readable link names
-|style="background-color:tomato;"| {{result|fail}} use ID for identification
-|}
--->