Requirements (in Projects module)
- First option – requirements are used as definitions of test analysis.
- Second option – through the requirements submodule, you can track the Test Execution status (the status of the entire project or just a specific sprint).
Firstly, we’ll have a look at Requirements as a sub-module. The user must complete 3 steps or import a template with similar data.
- Create folder
- Create master requirement
- Create child requirement
In the main table you’ll find basic functionalities:
Filters and table settings in a specific folder
Other functionalities that work with requirements are: create, edit, add a child requirement, delete and clone
The folder serves for a better orientation and clarity of the group of requirements. For a better overview, you can organise your requirements into folders just as you do on a computer.
Create a master requirement
The master requirement, which contains one or more child requirements, defines the bigger part of the project (for example: if you want to create specific modules such as storage, project or campaign, you have to define the basic functions of these modules).
When creating the master requirement, you must fill in each required field (marked in red):
- Location – folder, name
- Basic information – (short) description
- Author, owner
- Requirement status
- Attachments & links
If you need to implement something into the application, here is where you can define every important step of this change.
The child requirement contains every detail of the demand. It’s assigned to the master requirement (for example: in the master requirement we defined the storage creation. In the child requirement we define the buttons in the main menu such as export, import, show, delete, etc.). In addition, we can create a child requirement for every button.
In this template you have to fill in required fields too and after that you can create the requirement:
Location – folder, master requirement, name
Basic information – (short) description
Attachments & links
Here you can define more detailed information regarding the functionalities of an emerging application and its better development.
Adding, Cloning, Editing & Deleting a requirement
These functionalities are located on the right side of the requirement list. For all functionalities except for Delete, you’ll see a template similar to the one used when creating a requirement.
- The functionality to add child requirement looks like a blue plus and its form is the same as the child requirement creation form.
- Cloning a requirement has the same form as the requirement creation, but in addition there are some pre-filled fields (just fill in the name and change some information if you need).
- The edit form is also the same; there are just two additional lines – the difference and the type of change. These fields must be filled in if you change important requirement information.
Export & Import
Other useful functionalities are export and import. These two features are useful when saving or loading application requirements. The functionalities work with .xlsx documents. To import a document, you must use a document with a specific template (click here for download).
The main table shows the latest and current version of the requirements. If the master requirement is edited, the status of all assigned child requirements is changed to “Not approved”. If the child requirement is edited, the status of all assigned TCs (test cases) will also change. The version will be changed if the adjustment is large enough.
Master requirement details
You can see a dashboard with detailed information after clicking on the name of the requirement name. Here you can clone, edit, delete and add requirements. These functionalities are described above.
On the right you can see the requirement detail. After clicking on “test case count” and “issue count” you’ll see the sub-modules “test coverage” and “issues“.
On the main page (dashboard), you can see other sub-modules, which includes also “Child requirements“. Here you can see a list of all assigned requirements. You can also add, clone, edit, or delete child requirements (these functionalities are described above).
The table with the list can be adjusted by using filters or table settings.
The “test coverage” sub-module contains statistics concerning the assigned test cases (TC). For this feature, you need to know how the test analysis, test plan, and test execution modules work. You then create a child requirement where you can make test coverage settings.
1. Test analysis setting:
When creating or editing a test case, you can set options for assigning a requirement by completing 4 fields (folder, master requirement, child requirement, and child requirement version). After that, you can assign a test case. Now if you check the “test coverage” sub-module, you won’t see any assigned test cases.
2. Test plan setting:
Once you have created a test plan and test sprint (click “here” for more information), you can edit or create test cases that you assign to the requirements in the test plan and sprint. Then check the “test coverage” sub-module to see the number of assigned test cases in the “test case count” and “coverage status count” columns (usually in a grey box).
3. Test execution setting:
If you’ve completed the previous two steps, you can click on the test execution module (click “here” for more information) and find the test sprint to which you have assigned a requirement. When you evaluate it, its status is changed. You’ll then be able to click on the “test coverage” sub-module. In the “coverage status – count and percentage” column, you’ll see the statistics on the assigned test cases (each case is classified by its current status).
For example: There are 5 test cases in the test execution that have been assigned to the requirement. One of the cases will be marked as “passed”, the other two will be in the “failed” status and the last 2 will be in the “not completed” status. Then open the “test coverage” sub-module. The column ”test coverage – count” will have 4 fields with different colours. In the green field – there will be the number 1 (the number of test cases passed), in the red field – there will be 2 (the number of test cases failed), in the yellow field – there will be 2 (the number of test cases not completed), and in the grey field there will be 0. In the “test coverage percentage” column, you’ll see 20% (the percentage of test cases passed).
In this module you can see a table with basic settings. Issues that are assigned to requirements are displayed here. You must set more information in the issues module in order to connect them.
Add issues into requirements
If you’re in the “Issues” module, you can create or edit issues. In the template for creating or editing, there is a section for connection with requirements. You fill in the folder, master and child requirement, and child requirement version. After this step, you can return to the issues sub-module in the master requirement, where you can see the edited or created issues.
Click on the sub-module to see the folder page. When you create a master / child requirement, a folder with the same name is automatically created and connected with the requirement.
Click on one of the folders to see the attachment gallery. You can delete or download them using bulk actions. By clicking on any of the attachments you’ll see detailed information regarding the attachment and from this window you can download or delete it from the requirement.
Use the delete button to cancel the connection between the requirement and the attachment; however the file won’t be deleted.
Another functionality is the “back” button. Click this button to see the “Attachments” sub-module. The last functionality is “add a file”. Click this button to see the window (image on the right). The first item to fill in is a folder in which you select one of the created folders in the file module (for more information about the files click “here”) and then you can select a file from your computer. The file will be added to the requirement and files at the same time.
The “history” sub-module records all changes made to the requirements. A new table is created for each requirement, where you can see the history of the master and child requirements. The current version can be changed by this sub-module using the “delete” action.
In this sub-module, the delete function is important for you to change the requirement’s current version to the previous version or delete the requirement:
If you delete the last version (which is current), the previous version becomes current version.
You can delete the previous version (not the current one) and after deleting it you’ll see the same version as before.
After all versions are deleted, the requirement will be deleted. When you delete a requirement, the child requirement is also deleted.
Here you can see one or more tables. You can compare it with the sub-modules history or attachments. A table entry will be created for each requirement. You can also work with table settings. Here you can see a list of links that are connected to specific requirements. Links can be edited or deleted.
The last function is to add a link – here you add a link and a description.