Requality: user guide
Projects
Create Requality project
- To create project select in main menu
'File' -> 'New' -> 'Project...'
- In opened dialog window choose 'Requality' ->
'Requality Project' and push 'Next' button.
- On the next page input project name and push 'Finish'.
Documents
Import document
If you want to mark requirements
in document, first of all you should import the
document that contains text of the requirements.
The requirements could be written in a free-form. Requality allows importing documents with
following extensions: 'doc', 'pdf', 'htm',
'html'. Herewith Requality copies an original document, converts it to 'xhtml'
and puts the resulting document to the project. The original document isn’t changed. Resulting
'xhtml' –document is a document that is used in the following work.
Requality allows importing of one document, set of documents, and folders with documents.
-
To import document select 'Documents'node (or its sub-node). In context menu select
'Import Document...'.
-
To select source directory push 'Browse...' to the right of the
'From directory:' field in opened
'Document Import Wizard' window and select directory where
documents or files with documents are situated.
-
There are some ways to select required document or folder:
- In 'Document Import Wizard' window in the left area
click (not select) on folder where needed document (documents) is situated.
In the right area you will see all the documents from this folder.
Select needed documents.
- To select all documents in some folder and all documents
in its sub-folders, select this folder in the left area.
- Use buttons 'Select all' and 'Deselect all'
to select and deselect all documents in the folder at once.
-
You can use document extension filter. As we wrote above Requality
provides import of documents with 4 extensions: 'doc',
'pdf', 'htm' and 'html'. But you can change
the default filter and try to import other documents. So if you want
to import document with other extension follow these instructions:
-
Push button 'Select types' in 'Document Import Wizard' window.
-
In opened 'Select Types' window in the list of available
extensions select those you want. Not-selected extensions are not
available to import and you won’t see them in 'Document Import Wizard' window
-
In 'Select Types' window you can also use 'Select All'
and 'Deselect All' buttons to select and deselect all extensions in folder at once.
-
If you want to import a document with extension not in the list,
(e.g. 'xhtml') input this extension to 'Other extensions:' field.
-
Note! Requality supports importing for only documents with extensions
'doc', 'pdf', 'htm' and 'html'.
For other extensions the result could be incorrect.
-
Note! If you didn't find your document in the target folder check filter settings.
If you selected required extensions push 'OK'. Now documents with
selected extensions are available to import.
-
Now you should select a target folder. The target folder is a folder in
Requality-project where you want your documents to be imported to. Select it in 'Into folder:'
field. Default target folder is 'Documents' (the root documents folder) or its sub-folder
(if you called import on it). Push 'Browse...' to the right of the
'Into folder:' field to select or create other folder.
(Read more about document folders in Document folder creation.)
-
If imported documents have the same names as documents in the project folder you can choose
'Rename existing documents' option. Just select this flag. Now imported documents
will be renamed (by adding indexes) if their names are similar to the already imported documents.
-
When importing a folder with all nested documents and sub-folders, this hierarchy is not
transferred in your Requality project as default. All document from the folder and sub-folders are
got into the target folder 'Documents'. If you want to save the hierarchy use
'Create folders' option in 'Document Import Wizard' window.
Now all importing documents will be transferred by a hierarchy.
-
Now if you have already chosen importing documents and selected target folder finish import
by pushing 'Finish' button in 'Document Import Wizard' window.
After process finish 'xhtml'-documents appear in target folder.
Delete document
-
To delete a document select it in 'Requality Explorer' view.
- In context menu select 'Delete Document'.
- Also you can use 'Delete' hotkey.
-
Push 'OK' in the confirmation dialog to proceed document deletion.
-
If there are marked locations in the document you want to delete, you will get one more
confirmation dialog on this step. This dialog warns you that all marked locations
will be deleted together with the document. If you agree and want to proceed push
'OK'. Note! All locations marked in this document will be deleted from the
requirements. The requirements will remain without links to these locations.
Update document
Requality allows updating documents by transferring requirements locations
from an old document version to a new one. You can read about it here: "Transferring locations
to new document version".
Create documents folder
There is possibility to create folders in 'Documents' node and set documents there.
It helps to comfortably organize documents in 'Requality' project.
- To create a documents folder select 'Documents' node or any it’s sub-folder
(if exists), select 'Create Folder' in the context menu.
- In the opened window input folder name to the 'Enter folder name' field.
- The name shouldn’t replicate name of folders are on the same hierarchy level
in the documents node. Otherwise you get a warning and can’t proceed.
- After you input a correct name push 'OK'. Now you can see this folder in 'Requality Explorer'.
And now you can import documents to the new folder.
Delete documents folder
-
To delete a documents folder choose it in 'Requality
Explorer'.
- Select 'Delete Folder' in the context menu.
- You can also use 'Delete' hotkey.
-
Note! Folder deletion causes deletion of all nested documents and sub-folders.
If you are sure push 'OK' button in a confirmation dialog to proceed.
-
If folder being deleted or its sub-folders contain documents with
marked locations you get
one more confirmation dialog on this step. Note! If you delete the folder
all nested documents are deleted. Thus all the locations in these documents
are deleted too. If you agree and want to proceed push 'OK' button in
a confirmation dialog.
Requirements
All requirements in
Requality project
are situated in 'Requirements' node.
Create requirement
- Select 'Requirements' node or any it’s sub-requirement in
'Requality Explorer'.
Let it be a target requirement. In context menu select 'Create Requirement'.
New requirement appears in the target requirements. An identifier is generated automatically.
A name of the new requirements is empty by default. Other parameters are empty by default.
Delete requirement
Note! If you delete a requirement all its locations
are deleted and all corresponding marks in the documents are
deleted too.
- To delete the requirement choose it in 'Requality Explorer', select
'Delete Requirement' in the context menu.
- You can also use 'Delete' hotkey.
- In the opened dialog confirm deletion by pushing 'OK'.
Create requirement by selecting location
You can create a requirement in the document editor ('Markup
Editor') and add the location to it at the same time.
- Open document where you want to mark some location
for new requirement.
- Choose node 'Requirements' or some sub-requirement in 'Requality Explorer'. Let this requirement
be a target.New requirement we want to create will be sub-requirement for the target requirement.
- Select text part you want to be a location in 'Markup Editor'. Note! If required location
has already been marked for some requirement, you shouldn't select it in document text, just skip this step.
- Call context menu on selected text and choose one of two menu items:
- 'Create new Requirement:
<target_requirement_name>/<new_requirement_id>'.
Here '<new_requirement_id>' is generated automatically.
New requirement name (see
requirement properties) is empty.
- 'Create new Requirement:
<target_requirement_name>/<new_requirement_name>'.
Here '<new_requirement_name>' is the text of selected location.
Id for new requirement is generated automatically.
- Note! If the target requirement is 'Requirements' node,
'<target_requirement_name>' is not shown in these two menu items.
It looks like: 'Create new Requirement: <new_requirement_id>'
and 'Create new Requirement: <new_requirement_name>' respectively.
- Remember you always can change requirement id and name later.
Just edit properties of the requirement (see
'Edit requirement properties').
-
As a result, the target requirement gets new sub-requirement with the location.
The text of this location is marked in the document.
You can read about simple requirement creation here: 'Create requirement'.

Add location to requirement
A requirement can have some location (some links to text pieces marked in the document).
So you can add new location to an empty requirement (which has no locations yet)
or to a requirement, which has already have some locations.
- Open the document which text fragment you want to mark and add to the requirement.
- Select the target requirement in 'Requality Explorer'.
- Select needed text location in the document editor. Note! If required location
has already been marked for some requirement, you shouldn't select it in document text, just skip this step.
- Call the context menu on selected text and choose one of two menu items:
- 'Add to Requirement…' allows selecting target requirement independently.
In opened window select the target requirement. You can also create a new requirement
by 'Create New', button. After you chose the target requirement push 'OK'.
If chosen requirement is not one that you have chosen in step 2 it becomes a new target requirement.
- 'Add to Requirement: <requirement_name>' allows adding new location to
<requirement_name>requirement. Note! This is the target requirement you have selected in step 2.
-
As the result selected location is marked in the text and is added to the target requirement.
Delete location in document editor
To delete a location from the requirement you should delete its selection in the document.
Thus location will disappear from the document and from the requirement. Note! If the location belongs to
several requirements at the same time, it will be deleted from all these requirements. (If you want to delete
the location from the specified requirement only see
Delete location in Properties view).
- Double-click on location in 'Properties view'. The document will be opened
and scrolled to the place where the location is situated.
- Call the context menu on the location and select 'Remove from Requirement'.
- Now you can see that this location is not marked in the document anymore and there
is no link to this text in the requirement 'Properties' view ('Description' tab).
Delete location in Properties view
Here is another way how to delete a location from a requirement. This way is suitable if the location belongs to
more than one requirement but you want to delete it from the one specified requirement.
- Open 'Properties'
view for the target requirement, open 'Description'
tab (see Edit requirement parameters).
- Select required location in 'Locations' list.
- In context menu select 'Delete' item. Or just use Delete hot-key.
Auto-mark locations in document
'Requality' allows marking locations in document automatically.
Select document in в 'Requality Explorer' and in context menu select
'HTML Headers Document Processor'. This processor allows marking HTML-headers
(text inside <h1></h1>, <h2></h2> and so on) as locations.
Every location is added to a new requirement.
Edit requirement parameters
To edit requirement parameters select the requirement
in 'Requality Explorer' or one of its locations
in 'Outline'. Now you can see requirement
properties in 'Properties' view.
Here we describe requirement parameters you can change manually.
-
Id
- Identifier is generated automatically by could be changed. Edit it directly in this field.
(Note! The identifier of 'Requirements' node can't be changed.)
- Note! If requirement name is empty the requirements is identified by Id.
- Id should be unique for all requirements on the same hierarchy level.
If input not unique id you get warning flag and this change is not saved.
- Id can’t begin or end with spaces. When saving such symbols are deleted.
-
Name
- Requirement name is empty by default (except the case
when you create requirement from a document and use it’s text as name –
see Create requirement by selecting location).
- Name shouldn’t be unique.
- Edit name directly in this field.
- If name is empty requirement is identified by Id, otherwise - by name.
-
Attributes
- Attributes are represented in a table of two fields: attribute name and attribute value.
- To add attribute push 'Add…' button. In the opened window input attribute name and value,
push 'OK'.
- Attribute name shouldn’t be empty. And it shouldn’t begin and end with spaces.
Attribute names in one requirement should be unique. If you try to add and save attribute with
incorrect name you get warning flag and 'OK' is not available.
- To edit existed attribute, double-click on it. Edit attribute name and value in the opened window.
- To delete attribute select its name in the attributes table and push 'Remove...' button.
In dialog window push 'Yes'.
-
Alternative
Description
- Is empty by default.
- Edit alternative description text directly in this field.
-
Locations
-
Predicate
- Edit it directly in this field.
- Rules for writing predicates are equal to JavaScript predicates.
Transferring locations to new document version
Requality allows transferring locations to a new document version.
If you have a document with locations and you get a new document amended
and supplemented than you may want to transfer old locations to the new document. Do the following:
- Be sure new document is imported to the project. If not import
it to a recent project.
- Select the new document in 'Requality Explorer' view and select
'Update Document' in context menu.
- In opened window select old document.
After the processing is complete the window with information about the number of locations found in the old version and the number of locations transferred into a new version will appear. And in the Requiality Explorer view will appear small overlay icons over the requirements icons in the top right corner. Those overlays tell about the statuses of the transferred requirements and their children requirements. There are the following types of statuses:
- Failed - red checkmark - not a single location has been transferred for this requirement, but there is at least one in old version
- Incomplete - yellow checkmark - this requirement consists of few locations but not all of them has been transferred to the new document
- Complete - green checkmark - all locations of this requirement have been transferred into a new version
- And there is the separate case - no status, the overlay is also absence in this case - if the requirement is a leaf requirement and doesn't contain any locations in the old version of the document

The statuses are distributed from children requirements to the parent for the following design: the parent get the worst status from all its children.
The parent will have no status only in case all its children have no statuses.
Automated requirements transfer rarely may transfer all the requirements so after the transfer is finished user should carefully review the transferred
and not transferred requirements and correct them is necessary. For the convenience for tracking of transferred and corrected requirements
there is an option for manually changing statuses for transferred requirements. It is possible to change status only in a way to improve it,
that is in order Failed -> Incomplete -> Complete. Also there is an option to remove status in any time. To change a status right click on the
requirement and choose in the context menu the option "Change transferred status" and then in the pulldown choose new status or remove the old
one. After the status has been removed the overlay icon will not be represented, there is no options to return that icon manually.
Note. It is assumed to transfer requirements sequentially for different documents. Firstly, requirements from one document are transferred and if
necessary corrected. For automated transferring of the requirements from another document it is necessary that all requirements will have no transferred statuses.
User may remove the statuses manually or by deleting one of the versions of the corresponding document. Transferring requirements for few documents in the same time is not allowed.
Requirements tree sorting
In Requality project requirements could be sorted in two ways: 'By Locations' and 'By Names'.
Default sorting is 'By Locations'.
-
By Locations - requirements are sorted by location position in document. If requirement has several locations sorting depends only on the
first location. Requirements without locations are at the end of the list and are sorted by names. If locations are situated
in several documents of the project sorting depends on document name (documents are sorted by name).
-
By Names - requirements are sorted by name (first, in ascending order, then in alphabetical order). In case of coincidence
or lack of names requirements are sorted by id.
To change sorting method open context menu on the project in Requality Explorer and select 'Properties'.
Window with project properties will be opened. Select Requality on the left side of the window. On the right you will see properties of Requality project.
In 'Sort method' drop-down list select sorting method ('By Locations' or 'By Names') and push Apply button.
Now selected sorting method is set for this project.
Generate test for requirement
ATTENTION! The feature is experimental. It can be changed in further
releases.
Requality allows to add new tests to a test purpose or a requirement by using extending test generator.
Requality 0.16 provides test generation by special pattern.
Tests can be generated from 'Requality Explorer':
- Select a requirement or a test purpose in 'Requality Explorer'.
- Open a context menu for the selected element and choose 'Create Test'.
- List of available generators will be displayed. If there is no test
generator available, dialog window with title "Test generators are not
available" will be shown. In this case it is required to install
additional plugins that includes test generators. One of them 'Requality Coverage' plugin is available now on Requality update site.
- When test generator is selected there will be shown a dialog window to configure selected generator.
For example for 'ttcn' test generator implemented in 'Requality Coverage Tool' its required
- to select project for a new test,
- to set name of a test file,
- to confirm target requirement or test purpose
- to confirm or to change a template of selected file
It is also possible to add test from 'Coverage' report by
pressing "Add test" button in the report view.
Also you can use Eclipse main menu -> 'New' -> 'Other' -> folder 'Requality' -> "Create Test".
Test purposes
All test purposes in Requality project
are situated in 'Requirements' node in terminal requirements
(requirements that have no sub-requirements).
Create test purpose
Note! Test purpose could be added only to terminal requirement
- In 'Requality Explorer' view select a terminal requirement where you want to add new test purpose.
- Open context menu and select 'Create Test Purpose'..
Edit test purpose properties
To edit test purpose parameters select this test purpose in 'Requality Explorer'.
Now you can see its parameters in the
'Properties' view.
Here we describe test purpose parameters you can change manually.
- Id
- Identifier is generated automatically but could be changed manually. Edit it directly in the field.
- Id should be unique for all the test purposes of the same requirement.
If you input not unique id, you get warning flag and this change is not saved.
- Id can’t begin or end with spaces. When trying to save changes, such symbols are deleted.
- Test target
- By default it is a requirement for which you create this test purpose.
- To edit push 'Browse...' button near and select a requirement.
- You can select only the requirement that has no any sub-requirements.
- Status
- By default 'in process' is set.
- To edit status, open combo box and select one of three available statuses.
- Author
- By default it is a user name that was set while registering in Eclipse.
- Edit author name directly in this field.
- Attributes
- Attributes are shown as a table of two columns: attribute name and attribute value.
- To add a new attribute push 'Add…' button. In the opened window input attribute name
and value. Push 'OK'.
- Attribute name can’t be empty. It can’t begin or end with spaces. Attribute names
in one test purpose should
be unique. When trying to save attribute with incorrect name you’ll see warning flag and
'OK' button will be not available.
- To edit existing attribute, double-click on it's name. In opened window you can edit name
and value of attribute.
- To delete existing attribute select it in the attributes table and push 'Remove...' button.
In the opened dialog window push 'Yes' button.
- Description
- Is empty by default.
- Edit alternative description text directly in this field.
- Expected Results
- Is empty by default.
- Edit expected results text directly in this field.
- Predicate
- Edit directly in this field.
- Predicates should be formulated according to the JavaScript rules.
Delete test purpose
- To delete a test purpose select it in 'Requality Explorer',
in the context menu select 'Remove Test Purpose'.
- You also can use 'Delete' hot-key.
- In the opened dialog window push 'OK'.
Generate test for test purpose
Requality allows to create a new test aimed to check a test purpose in the same way as it made for requirement. More information is available
in corresponding section of manual
Reports
Create report
A report could be created for
any requirement. Such report
includes data about selected requirement node itself and about all its sub-nodes.
A report type depends on selected template.
- Select target requirement in 'Requality Explorer' view,
select 'Generate Report' in the context menu.
- In the opened dialog window edit report name and push 'OK'.
You also can create a report by selecting 'Create Report Data' in the
context menu of the 'Reports' node. A name of such report is
generated authomatically and 'Requirements' node is set as
a Root requirement.
Edit report properties
To edit report parameters select the report in 'Requality
Explorer' view, you’ll see its
properties in 'Properties' view.
Here we describe report parameters you can change manually.
- Root
requirement
- By default it is a target requirement for which the report was created.
- Push 'Browse...' button, in the opened window select other requirement and push 'OK'.
- Template
- Attributes
- To add new attribute push 'Add…' button. In the opened window input attribute
name and value. Push 'OK'.
- Attribute name can’t be empty. It can’t begin or end with spaces. Attribute name
should be unique for one report. If you try to save the attribute with incorrect name you’ll
see warning flag and 'OK' button will be not available.
- To edit existing attribute double-click on it's name. In the opened window you can edit name and value
of the attribute.
- To delete the attribute select it in the attributes table and push 'Remove...' button.
In the opened dialog window push 'Yes' button.
- Note! 'date' attribute is generated automatically after every report generation.
If you create your own attribute with the name 'date' its value will be changed
after report generation.
Working with 'Coverage' report
ATTENTION! The feature is experimental. It can be changed in further releases.
'Coverage' report is designed to present information about coverage of
requirements and test purposes by tests.
To build coverage report its required to select source of coverage information:
- Create a new report.
- In Properties view select 'Coverage' template for the report.
- Open context menu for the report in 'Requality Explorer' view and select 'Update Coverage Source'.
- Then choose one of available coverage sources:
- 'From File' collects coverage information from a file (see
description of the corresponding file format in glossary). Use file
selection dialog to choose a file.
- 'Coverage By Projects' collects coverage data from another
Eclipse project available in the same workspace. You will be asked for
the following additional parameters:
- Projects where needed files will be searched.
- Extension of these files .
- Regular expression to find identifiers of requirements and
test purposes. The first capturing group is used to extract found value.
More information about regular expressions see here: Java regular expressions.
- When coverage source is chosen it is possible to generate report as
usually.
Working with 'Document Model' report
ATTENTION! The feature is experimental. It can be changed in further releases.
'Document Model' report is designed to present information about coverage of document locations by tests. Working
with 'Document Model' report is similar to 'Coverage' report but as a result you get a document with selected locations where the color of selection shows if this location has been covered or not.
To build coverage report its required to select source of coverage information:
- Create a new report.
- In Properties view select 'Document Model' template for the report.
- Open context menu for the report in 'Requality Explorer' view and select 'Update Coverage Source'.
- Then choose one of available coverage sources:
- 'From File' collects coverage information from a file (see
description of the corresponding file format in glossary). Use file
selection dialog to choose a file.
- 'Coverage By Projects' collects coverage data from another
Eclipse project available in the same workspace. You will be asked for
the following additional parameters:
- Projects where needed files will be searched.
- Extension of these files .
- Regular expression to find identifiers of requirements and
test purposes. The first capturing group is used to extract found value.
More information about regular expressions see here: Java regular expressions.
- When coverage source is chosen it is possible to generate report as
usually.
Open report
- Select required report in 'Requality Explorer' and double click on it. The report is opened.
- Note! If you have changed report properties, or did some manipulations with requirements and
other nodes in the target report node, or just edited them, you should note that these changes are not shown
in the opened report. To re-generate the report close it and open again.
Delete report
- To delete the report select it in 'Requality Explorer', select 'Delete Report'
in context menu.
- You also can use 'Delete' hot-key.
- In the opened dialog window push 'OK'.
UniEditor
Open UniEditor
In 'UniEditor' you can open
requirements tree (with test purposes and comments).
The root node of this tree is a requirement on which you called 'UniEditor'.
Thus in UniEditor you can open whole requirements tree (just call 'UniEditor' on root
'Requirements' node) or some sub-tree
(call it on some sub-requirement).
Select target requirement in 'Requality Explorer',
in context menu select 'Edit in UniEditor'.
Add new requirements in UniEditor
- Select a requirement in 'UniEditor'.
- Push menu button in the upper-right corner of the requirement field and select in the menu one of two items:
- 'Add sibling requirement' to create requirement-neighbor. New requirement is
created after the target requirement.
- 'Add child requirement' to create
sub-requirement. New requirement is created
as child node for selected requirement.
Delete requirement in UniEditor
Note! When deleting requirement its sub-tree is deleted too,
including nodes of all types (requirement, test purposes, comments).
- Select target requirement in 'UniEditor'.
- Push menu button in the upper-right corner of the requirement field and select 'Delete requirement'.
- In the opened dialog window push 'OK'.
Edit requirement in UniEditor
Requirement field consists of two parts. The upper one contains requirement name,
the lower one contains requirement alternative description.
- To edit requirement name double-click on the upper part of the field.
The field becomes editable. To finish editing click somewhere else on the screen.
- To edit requirement text double-click on the lower part of the field.
The field becomes editable. Here you can see control panel to edit the text.
It includes buttons for text formatting, for adding symbols, pictures, links, etc.
To save changes push 'Save' button in this menu. Also you can use button to undo editing.
- To change requirement status click on status-icon on the left side of the
requirement name. When clicking, the status changes from 'in process' to
'complete' and vice versa.
Add new test purpose in UniEditor
- Select in 'UniEditor' one of two nodes:
- requirement where you want to add new test purpose,
- or test purpose which belongs to a requirement you want to add new test purpose to.
- In the upper-right corner of this node (requirement or test purpose) field open menu
and select 'Add new test purpose'.
Delete test purpose in UniEditor
- Select the target test purpose in 'UniEditor'.
- In the upper-right corner of this test purpose field open menu and select 'Delete test purpose'.
- In the opened dialog window push 'OK'.
Edit test purpose in UniEditor
The field of the test purpose consists of two parts. The upper part contains the name of the test purpose;
the lower part contains the text of the test purpose.
- To edit test purpose name double-click on the upper part of the test purpose field.
The field becomes editable, and you can make changes. To finish editing click anywhere else on the screen.
- To edit test purpose text double-click on the lower part of the test purpose field.
Here you can see control panel to edit the text.
It includes buttons for text formatting, for adding symbols, pictures, links, etc.
To save changes push 'Save' button in this menu. Also you can use button to undo editing.
- To change test purpose statuse, click on status-icon on the left side of the
requirement name. When clicking, the status changes from 'in process' to
'complete' and vice versa.
Add comment in UniEditor
Comment can be added to
any node in the 'UniEditor', except a comment-node.
- Select in 'UniEditor' the node (requirement, test purpose or requirement)
which you want to add a comment to.
- In the upper-right corner of the selected node expand the menu and select 'Add new comment'.
- When creating a comment, it's field appears in the 'UniEditor' and it's node appears
on the appropriate place in the project tree in 'Requality Explorer' view.
By default, the comment gets name in form of 'Comment <num>', where <num>
is node number (if there is no any other comments on the same level than number is 01, else next free number).
By default created comment is empty, editing of the comment text is described below.
Edit comment in UniEditor
To edit the text of the comment, double click in the comment field.
Here you can see control panel to edit the text.
It includes buttons for text formatting, for adding symbols, pictures, links, etc.
To save changes push 'Save' button in this menu. Also you can use button to undo editing.
Delete comment in UniEditor
- Select the target comment in 'UniEditor'.
- In the upper-right corner of the comment field open menu and select 'Delete comment'.
- In the opened dialog window push 'OK'.
Hotkeys in UniEditor
You can use hotkeys when working in 'UniEditor'. There are hotkeys for all items of the node context menu
in 'UniEditor'. Also there are additional hotkeys to comfortable use some other actions. Here there is a full list
of all hotkeys in 'UniEditor'.
Hotkey |
Usage |
Esc |
Close node aditor without saving |
Ctrl+S |
Save changes in node editor |
Up |
Switch focus to node above |
Down |
Switch focus to node below |
Left |
Collapse expanded node or switch focus to parent-node |
Right |
Expande collapsed node or switch focus to node below |
PageUp |
Scroll selected view by one page up |
PageDown |
Scroll selected view by one page down |
Home |
Go to start of editor |
End |
Go to end of editor |
Alt+Ins |
Add sub-requirement |
Ins |
Add test purpose |
Alt+C |
Add comment |
Del |
Delete node |
Enter |
Start node editing |
F2 |
Start node name editing |
Alt+S |
Change status |
Num+ |
Expande node |
Num- |
Collapse node |
Ctrl+C |
Copy node |
Ctrl+X |
Cut node |
Ctrl+Shift+V |
Paste node as sibling (without sub-nodes) |
Ctrl+V |
Paste node as child (without sub-nodes) |
Ctrl+Alt+Shift+V |
Paste node with all its subnodes as sibling |
Ctrl+Alt+V |
Paste node with all its subnodes as child |
Review
Working in 'Review' is similar to working in 'UniEditor',
but more limited in functionality. Here you can't add or delete requirements and
test purposes, you can only edit their status.
Open Review
In 'Review' editor you can open
requirements tree with
test purposes and
comments.
Requirement for which you open 'Review' is displayed as root node.
It means that you can open the requirement tree in a whole (by calling them in the
'Requirements' root node) or separate
requirements sub-tree
(by opening the editor on the several sub-requiremets).
In 'Requality Explorer' choose the target requirement, open context menu and chose 'Review'.
Edit statuses of the requirements and test purposes in Review
To change the status of requirement/test purpose click on status-icon on the left side of the
node name. When clicking, the status is changed in the following order:
'in process' -> 'complete'
-> 'verified' -> back 'in process', etc.
Hotkeys in Review
When working in 'Review' you can use hotkeys. In 'Review' there are hotkeys not only for
manipulation with comments but for some other usages too.
The list of all hotkeys for 'Review' is similar to the list of
hotkeys for 'UniEditor',
except for the prohibited usages.
Virtual Nodes
NOTE! Virtual Nodes are experimental functionality. Therefore working with virtual nodes and information
about virtual nodes in this manual could be not quite correct and relevant.
Create virtual node
- In 'Requality Explorer' select or create a requirement for which you want to create virtual node.
Select 'Create Virtual Node' in a context menu for this node. New virtual node will appear.
Delete virtual node
- To delete virtual node select it in 'Requality Explorer', select 'Delete Virtual Node' in a context menu for this node.
- You can also use 'Delete' hotkey.
- In the opened dialog confirm deletion by pushing 'OK'.
Edit virtual node parameters
To edit virtual node parameters select it in the 'Requality Explorer', Now you can see requirement properties in the 'Properties' view.
Here we describe parameters of the virtual node you can change manually.
- Target
- Is empty by default.
- To set 'Target' push 'Select...' button. In the opened window select requirement or test purpose or create new requirement with the help of 'Create New' button. Push 'OK'.
- If a parent-requirement of virtual node has a child test purpose then only test purpose (not requirement) could be selected as a 'Target' in this case.
- Iteration method
- 'Reuse' is set by default.
- To edit open the drop-down list and select one of two values: 'Reuse' or 'Base Element'.
- Iterate over
- Multiple iterators could be specified. No one is set by default.
- To add new iterator push '+' button, new element with drop-down list (to select iterator) will appear. Select required iterator in the list.
- To remove iterator push button 'X' near the field.
- Id
- Id is generated automatically but could be changed manually. Edit it directly in this field.
- Note! If virtual node name is empty the node is identified by Id
- Id should be unique for all virtual nodes on the same hierarchy level. If input not unique id you get warning flag and this change is not saved.
- Id can’t begin or end with spaces. When saving such symbols are deleted.
- Name
- Virtual node name is empty by default.
- Name shouldn’t be unique.
- Edit name directly in this field.
- If name is empty virtual node is identified by Id, otherwise - by name.
- Attributes
- Attributes are represented in a table of two fields: attribute name and attribute value.
- To add attribute push 'Add…' button. In the opened window input attribute name and value,
push 'OK'.
- Attribute name shouldn’t be empty. And it shouldn’t begin and end with spaces.
Attribute names in one requirement should be unique. If you try to add and save attribute with
incorrect name you get warning flag and 'OK' is not available.
- To edit existed attribute, double-click on it. Edit attribute name and value in the opened window.
- To delete attribute select its name in the attributes table and push 'Remove...' button.
In dialog window push 'Yes'.
- Generators
- Is empty by default.
- To add generator push 'Add' button.
- To remove generator select it in the list and push 'Remove' button.
- Attr.name
- Is available only if there is at least one generator in the 'Generators' list.
- Corresponds to the generator which is selected in the 'Generators' list.
- To edit just edit text in this field. Changes appear in the name of the corresponding generator in the 'Generators' list.
- Attr.gen.type
- Is empty by default.
- To edit open the drop-down list and select one of 3 available values: 'RANDOM', 'BY_FORMULA', 'CYCLE'.
- If 'RANDOM' is selected following 3 fields are available: 'Min', 'Max' and 'Count'. By default they are 0.
Edit values directly in these fields.
If you set 'Min' value more than 'Max' then values will change places with each other.
Changing these values directly affects the contents of 'Preview'.
Also if 'RANDOM' is selected, 'Generate new set' button is available. Pushing this button generates new set of values in the 'Preview' field.
- If 'BY_FORMULA' selected edit field 'Formula' appear. Is empty by default. Edit this value directly in the field.
Example: set in 'Formula' field value: 'element'+_i, generator will generate following values element_0, element_1, element_2 etc.
- If 'CYCLE' is selected, following 3 fields are available: 'From', 'To' and 'Step'. By default they are 0.
Edit values directly in these fields. If you set 'To' value more than 'From' then values will change places with each other.
Changing these values directly affects the contents of 'Preview'.
- Scope
- By default 'DIRECT_CHILDREN' is set.
- To edit open the drop-down list and select one of 3 available values: 'DIRECT_CHILDREN', 'LOCAL', 'SUBTREE'.
- Preview
- Is empty by default.
- The content of this field is the result of setting generator parameters.
- Editing is possible indirectly by changing generator parameters. (see editing of 'Attr.gen.type' field).
Hide virtual node
- To hide virtual node select it in 'Requality Explorer', select 'Hide Selected Virtual Nodes' in its context menu.
The virtual node will be hided in the project tree, only its subtree (reused elements) will be shown.
Show virtual node
- To show (undo hide) virtual node select project tree element that contains this virtual node and call context menu on it. Select 'Show hidden children' in the context menu.
Virtual node will be shown in the project tree.
Checking the project tree
It's possible to check if Requality project tree is correctly set and to find problems in nodes description.
Open context menu on the root node of your Requality project and select 'Enable Checkers'.
After that all the nodes in which checker finds error are highlighted.

Version Control
For version control Requality allows working with CVS,
Subversive,
EGit and other Eclipse Team Provider (excluding
Subclipse). In 'Requality Explorer' context menu there is a standard
item 'Team' to manipulate versions.
SVN
To use 'SVN' you should install SVN-plugin to 'Eclipse'
(see Installation of plugin for interaction
with control version system) and get URL of repository where your project
is shared or will be shared (also you should get user login and password if needed). It's recommended to use
Subversive plugin. All instructions below are for exactly this plugin.
Export project to SVN
- In 'Requality Explorer' view click on the project folder and select 'Team -> Share Projects...' in the context menu.
- In 'Share Project Wizard' window in 'General' tab input URL of repository where you want to push your project to.
- Input user login and password in 'User:' and 'Password:' fields.
(If you don't want to be asked for password again select 'Save authentication'.) It is not necessary if repository
is not protected with a password.
- Push 'Finish'.
- In 'Commit' window input your comment in 'Comment' field. Verify that all project items are selected in the table below.
Push 'OK'.
- Wait until files transfer to repository. After that all project nodes in 'Requality Explorer' should be displayed
without an angle bracket in front of the name. The angle bracket means that the node has changes are not saved in 'SVN'. All parent nodes
of such node are also marked with the angle bracket. If some node is still marked with the angle bracket (after transfer to 'SVN' is finished)
try to refresh 'Requality Explorer': click on the project node, then push 'F5'
or select 'File -> Refresh' in 'Eclipse' main menu. If the angle bracket doesn't disappeare changes are not transferred to 'SVN'.
Commit changes to SVN
Following instructions describe how to transfer local project changes to repository (if this project already exists in 'SVN').
How to know that your local project is connected to 'SVN' (you are working with local copy of repository project):
there are version number and repository URL near project name in 'Requality Explorer'. This number is a number of version
that was last syncronized with the repository.
- In 'Requality Explorer' select changed node that you want to push to repository. If you want to push all project changes
then select root node of the project.
- Opent context menu on it and select 'Team -> Commit'.
- In 'Commit' window in 'Comment' field input your comment. Check that all needed items are selected
in поле выбора файлов. Push 'OK'.
- If 'User Credentials' dialog asks you about username and password, input it in 'User:' and 'Password:'
fields. If you don't want to be asked for password again select 'Save authentication'.
Import project from SVN
- In 'Requality Explorer' on empty place open context menu and select 'Import...'.
- In 'Import' window select 'SVN -> Project from SVN' and push 'Next >'.
- In 'Checkout from SVN' window look through the list of available repository URLs.
- If one of available repositories suits you select 'Use existing repository location:', then select this repository
in the table and click 'Next >'.
- If you didn't find your repository in the list select 'Create a new repository location' and click 'Next >'.
- In 'General' tab input URL of repository where you want to push you project.
Also input username and password in 'User:' and 'Password:' fields. (If you don't want to be asked for password
again select 'Save authentication'.) It is not necessary if repository is not protected with a password.
- In 'URL:' field input path to the project in the repository (including project folder). Click 'Finish'.
- In 'Check Out As' window doesn't change anything and click 'Finish'.
Update project from SVN
If project in the repository has been changed you can update your local copy following the instructions below.
- First of all it's recommended to close all opened documents. Or you should reopen them after update is finished to see all changes.
- In 'Requality Explorer' on you project open context menu and select'Team -> Update'.
- If 'User Credentials' dialog asks you about username and password, input it in 'User:' and 'Password:'
fields. If you don't want to be asked for password again select 'Save authentication'.