From Fedora Project Wiki

Revision as of 09:37, 20 January 2011 by Rhe (talk | contribs)

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