This page objectively compares feature sets of Wiki and Nitrate systems in relation to the important workflows. Instead of displaying a long feature lists, it is divided into groups by use cases. Click [show] button on each item to view the detailed comparison. To avoid overlaps, features compared in former use cases are not listed in later cases again.
Key Section
| Colour |
Explanation
|
 pass
|
Supported
|
 fail
|
Unsupported currently
|
|
|
Unknown/Research needed
|
| A
|
Feature A is Nice-to-Have
|
| B
|
Feature B is Must-Have
|
Wiki vs Nitrate Feature Comparison
| Creating A Common Page
|
| Feature |
fedoraproject.org/wiki |
nitrate
|
| 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
|
| Supports data entry using a form
|
fail wiki syntax
|
pass
|
| 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
|
by Tree View?
|
| Bookmarks/watchlist
|
pass watch the page
|
pass bookmark the page
|
| Creating A Test Case
|
| Renaming a case
|
warn 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
|
| The time historical test case results be available
|
pass all history?
|
unknown
|
| Referencing to versioned history
|
pass
|
fail can view text history and version
|
| 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
|
| Creating A Test Result Page
|
| Test result page creation
|
pass
|
warn Create from plans
|
| Contents in test result page
|
pass flexible wiki markup design
|
warn write in 'Notes' field without any syntax except cases
|
| Moving test results
|
pass manually copy
|
fail manually add one by one?
|
| Directing to current test run
|
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
|
| Quick access to active test runs
|
pass Open 'current' links
|
fail search the run's ID or search my runs(assigned to me in advance)
|
| 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
|
Can admin configure it?
|
| Supporting anonymous user read-only access
|
pass
|
pass
|
| Supporting anonymous user read-write access
|
pass
|
fail
|
| Integration with FAS
|
pass
|
|
| Feature extension
|
pass Add plugin
|
Add plugin?
|
| Page protection
|
pass by Admin
|
|
| Case/plan deletion
|
pass by Admin
|
pass Set as DISABLED. Test run can be deleted.
|
| Licensing
|
pass
|
pass
|
| License the content
|
pass
|
should match wiki
|
| Integration between update tools (bodhi/f-e-k) and our test infrastructure.
|
pass investigating
|
|
| Upstream project community
|
pass upstream wiki list
|
pass upstream nitrate list
|
| 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 page creation
|
pass
|
fail test runs can only be created from plans
|
| Test day page contents
|
pass
|
fail write all intro to 'Notes' field will be too crowded!
|
| 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.
|
| Each case with different platforms
|
pass
|
fail ?? two test runs for both platforms?
|
| Test result page creation
|
pass
|
pass created from plans
|
| Test result page contents
|
pass
|
warn write intro to 'Notes' field without any syntax
|
| Progress bar for each run
|
fail
|
pass
|
