← Back to team overview

neos team mailing list archive

[Blueprint docu-system-test-scenarios] (DOCU) System Test Scenarios

 

Blueprint changed by Johannes Wettinger:

Whiteboard changed:
  SCENARIO 1: PLAN A NEW REVIEW MEETING
  
  * Set the product's properties
  * Set the review's properties
  * Create one or more meetings
  * Cancel one of the meetings if there is more than one meeting
  * Modify the severities; test all possibilities of interaction like adding, removing, editing or resorting severties
  * Add one or more attendees
  * Allocate some aspects
  * Create the invitation package for one certain attendee; try all kinds of output formats
  * Create the invitation packages for all the attendees; try all kinds of output formats
- * Save the review as .REV file
+ * Save the review as REV file
  
  SCENARIO 2: CONDUCT A PLANNED REVIEW MEETING
  
  * Open the review file which has been created during the execution of scenario 1.
  * Continue with step "Create a list of findings" like it is described in scenario 3.
  
  SCENARIO 3: CONDUCT AN INSTANT REVIEW
  
  * Set the reviewer's properties
  * Set the product's properties
  * Set the review's properties
  * Allocate some aspects for the review
  * Create a list of findings
  * Add two or more findings to the list of findings
  * Change the the view of some findings (compact vs. edit view)
  * Resort the findings; test all possibilities of changing the order
  * Edit an arbitrary finding
  * Remove all existing findings
  * Add two or more findings to the list of findings
  * Finalize the list of findings
  * Export the list of findings as PDF file
  * Export the findings as CSV file
- * Save the review as .REV file
- * Save the review as .XML file
+ * Save the review as REV file
+ * Save the review as XML file
  * Quit the application
- * Open the previously saved .REV file
- * Open the previously saved .XML file
+ * Open the previously saved REV file
+ * Open the previously saved XML file
  
  SCENARIO 4: MANAGE ASPECTS
  
  * Open the Aspects Manager without creating a new review or loading an existing one
  * Remove all existing catalogs
  * Load standard catalogs
  * Load standard catalogs a second time
  * Export an arbitrary catalog
  * Import an arbitrary catalog
  * Export an arbitrary selection of aspects
  * Import an arbitrary selection of aspects
  * Resort the existing catalog in an arbitrary manner
  * Resort the categories of a certain catalog in an arbitrary manner
  * Resort the aspects of a certain catalog in an arbitrary manner
  * Create a new catalog
  * Add two new aspects to an arbitrary existing catalog
  * Edit an arbitrary aspect
  * Edit an arbitrary category
  * Edit an arbitrary catalog
  * Remove an arbitrary selection of aspects
  * Remove an arbitrary selection of categories
  * Remove an arbitrary selection of catalogs

-- 
(DOCU) System Test Scenarios
https://blueprints.launchpad.net/revager/+spec/docu-system-test-scenarios