Requirements (in Projects module)
The module Projects contains features for Requirement Management and there are two options how to work with these elements:
- First is that requirements are used as definition of test analysis.
- Secondly through requirements module which track Test Execution statuses (statuses of the entire project or just specific sprint).
For start let´s work with module requirements. User has to realize 3 steps or import template with similar data.
- create folder
- create master requirement
- create child requirement
The main table
In the main table you can see the basic functions:
- Filters & Setting of the table in specific folder
The other functionalities which work with requirements: Create, Edit, Add Child requirement, Delete and Clone.
Here you can arrange the requirements in the groups by folders. The folder make up object for group requirement of application.
Create master requirement
Master requirement which contains one or more child requirement, define bigger part of the projects (ex.: We want to create specific modules (storage, project, campaign) we need to define basic functionality of those modules).
When you create the master requirement you have to fill in every required box (which is marked with red border):
- the placement – folder, name
- the basic information – (short) description
- author, owner
- status of the requirement
- the attachments & links
If you need to implement something into the application here is where you can define every important step of this change.
Create child requirement
The child requirement contains every detail of the demand. It is assigned to master requirement (ex.: In the master requirement we have defined creation of the storage. In the child requirement we’ll define the buttons in main menu (the export, import, show, delete, etc.). In addition for every button we can create child requirement).
In this template you have to fill in required fields too and after that you can create the requirement:
- the placement – folder, master requirement, name
- author, owner
- the attachments & links
You can define more detail information about functionality of emerging application and its better development.
Add, Clone, Edit & Delete requirement
The function are situated on the right side of the requirements list. For all function except Delete you will see similar template like in creation of the requirement.
- Add child requirement looks like blue plus and its form is equal to the form for create child requirement.
- Clone requirement is same like the template for creating the requirement but with pre-filled fields (you just need to fill in the name and change some information if you need).
- Edit form is same as well only there you have two extra rows – the difference & type of change. This fields have to be filled if you change important information about requirement.
Export & Import
Between other useful functions belong Export and Import. These two functions are beneficial for saving or loading the requirements of the application. The functions work with .xlsx documents. For import you have to use document with specific template ( click here for download).
In the main table you can see the last and current version of the requirements. When the master requirement is edited the status of all assigned child requirement will be changed to “Not approved“. If the child requirement is edited the status of all assigned TC (test cases) will be changed too. The version will be changed if the modification is sufficiently big.
Detail of master requirement
After the click on the name of requirement we’ll see the dashboard with detail information. You can clone, edit, delete or add requirement. These functionalities are describe above.
On the right side you can see the details of the requirement. After you click on the “test case count” and “issues count” we’ll see the sub-modules “Test coverage” and “Issues“.
From dashboard you can see other submodules. Between them belong “Child requirement“. Here we can see the list of all assigned demands. We can add, clone, edit or delete child and edit master requirement (the functionality is described above).
The table with this list we can edit by filter or settings of table.
The submodule “Test coverage” contains statistics about assigned TC. For these functionality we have to know how works modules Test analysis, test plan and test execution. After the create child requirements we can perform a few steps for set the test coverage:
1. SETTING OF TEST ANALYSIS:
If you create or edit TC (test cases) we can set the option for connection with requirement by fill 4 boxes (folder, master requirement, child requirement and version of child requirement). After that you have to assigned TC to demand. Now if you check the submodule test coverage you won’t see assigned TC here anymore.
2. SETTING OF TEST PLAN:
When you have created test plan and test sprint (for more information click “here”) you can edit it and add created TC which are assigned to requirement into test plan and test sprint. After that if we check the submodule test coverage you’ll see the number of assigned TC in column “TC count” and “coverage status – count” (usually in gray box).
3. SETTING OF TEST EXECUTION:
When the previous 2 points are finished you can click on the module test execution (for more information click “here”) and find specific sprint with TC which are assigned to requirement. When you evaluate them, the status of TC will be changed. After that you can click on the submodule “test coverage“. In columns coverage status – count and percentage you‘ll see the statistics about assigned TC (the every TC will be classified by current status).
Ex.: We have 5 TC in test execution which are assigned to the one requirement. One of TC has status passed, two other TC have status failed and other have status not completed. After that we open the submodule test coverage. The column “test coverage – count” has 4 boxes with different colors. In green box we’ll see the number 1 (passed TC), red box 2, yellow box 2 and in gray box 0 by status of TC. In column test coverage percentage will see the 20% (1 of 5 TC has status passed).
In this module you can see the table with basic settings. Issues which are assigned to requirements are located here. To connect them you have to set some information in the module issues.
ADD ISSUES INTO REQUIREMENTS
When you are in the module issues you can create or edit the issues. In the template form for creating or editing is located part for connection with requirements. You can fill the folder, master, child and version of the child requirement. After this step you can return to submodule issues in master requirement and you’ll see the edited/created issue here.
After the click on this submodule you’ll see page with folders. When you create the child/master requirement the folder with same name will be automatically created and connect with it.
After the click on the one of folders you’ll see “gallery” with attachments. Through group action you can delete or download them. When you click on the one of attachments you’ll see the detail information about it and from this window we can download or delete it from requirement.
The button delete cancel the connection between requirement and attachment but the file won’t delete from instance.
The next functionality is button back after the click on that you’ll see the submodule attachments. The last functionality is add files. After the click on this button you’ll see the window (on the picture on right side). The first box is folder. Here we have to choose one of created folders in module files (for more information take a look on “files” in user guide) and after that we can choose any files from PC. The files will be added into requirement and files at the same time.
The sub-module history record every change in requirements. For every requirement will be created new table. Here we can see history of master and assigned child requirements. The current version can be changed by this sub-module by the action delete.
The action delete has important functionality for us in this sub-module. By it you can change the version of current requirement into previous versions or we can delete requirement:
- When you delete the latest version (which is current) the previous version became the current
- You can delete one of the previous version (not actual) and after that you’ll see the same version as before
- You can delete all versions and after that the requirement will be deleted. If you delete the requirement the child requirements will be deleted too
Here you’ll see one or more tables. You can compare it with sub-module history or attachments. For every requirement will be created one table. You can work with it by settings of table. Here you can see the list of links which are connected with specific requirement. The links can be edited or deleted.
The last function is the add links when you can fill the link and description.