(DOCU) System Test Scenarios

Registered by Johannes Wettinger

The following scenarios are used for the system test of RevAger. The input data should be obtained from the corresponding blueprint: https://blueprints.launchpad.net/revager/+spec/docu-system-test-data

Please be aware of the following conditions when executing the scenarios:

* After every input the tester has to check if the input data are represented correctly. This check includes all kinds of output files like invitation packages, list of findings, CSV files etc.

* The following aspects aren't considered in the scenarios, i.e. they should be verified separately:
-- Show and hide the help in the context of the dialogs
-- Show and hide the hints in the bottom area of the frames
-- Application settings
-- Change the application's language
-- Configuration of CSV profiles
-- Help browser
-- About dialog

* The execution of the scenarios should be documented until they came to an end without any error. In case there has been an error occured, you should create a new bug report including the flow trace. If there is a bug report regaring the occured error already existing, the flow trace should be attached to this report as a comment.

* Ideally, all the scenarios should be executed on all supported platforms, i.e. on the current version of Windows, Mac OS X and Ubuntu Linux, always in combination with the current version of the Oracle JDK and the OpenJDK.

Blueprint information

Status:
Complete
Approver:
Team NEOS
Priority:
Undefined
Drafter:
Johannes Wettinger
Direction:
Needs approval
Assignee:
Johannes Wettinger
Definition:
Approved
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None
Started by
Johannes Wettinger
Completed by
Johannes Wettinger

Related branches

Sprints

Whiteboard

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

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
* Quit the application
* 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

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.