Performance improvements

Continuing our previous and on-going work, we're doing some architectual changes that will provide benefits across several different areas in future versions. Some of this improvements have been addressed in previous v3.1.x releases and v3.2.0 adds some more, including the calculation of the Test Plans overall status/progress bar, global and per-folder (in the Board).

The work we've done so far will allow us to provide additional improvements on several areas, which we'll be doing gradually.

Improving performance is an on-going effort, so expect additional enhancements to come in future versions.

Automation requires a lot of maintenance effort. There's the need of doing refactoring at many different levels, including at the specification level. This is even more true if you're adopting BDD and Cucumber. As your projects grow, the number of Cucumber Scenarios/Backgrounds will also increase, as will also the amount of Cucumber steps used by them.

Since (Cucumber) steps can, and shall, be used across different test specifications, you may need to do some refactoring on your existing steps in order to avoid duplicates and as means to foster reusability.

Thus, the Automated Steps Library provides one central place to see and manage all the Cucumber steps used in the context of some given project, allowing you to classify/label steps and refactor them (update, merge). You can even quickly identify the entities using those steps.

Steps are added automatically to the Automated Steps Library upon the creation/edition of Tests or Pre-Conditions. As soon as they're in the library, they can be used afterwards for easing the creation/updating of Cucumber Tests/Pre-Conditions, using autocomplete and filtering steps based on labels.

You can now be much more proeficient using the the enhanced editor for Cucumber based Tests/Pre-Condiitons, right inside Jira.

Learn more here.

xxx

Two new gadgets so you can easily track your QA progress in your Jira dashboards: Requirements List Gadget and the Overall Test Results Gadget .

The Requirements List Gadget provides an enhanced list of requirements, including hierarchical information (e.g. Epic > Story), along with completeness information and respective amount of Tests, analyzed in the context of some version or Test Plan. This information is similar to the one seen at the end of the page in the Overall Requirement Coverage Report whenever drilling-down on some requirements.

The Overall Test Results Gadget provides an overall overview of the status of some Tests, in the context of a version or Test Plan. Thus, you can see the amount of Tests currently passing or failing, using a pie chart or in a table layout.

Learn more about these and all other gadgets here.

?????

???

We know that the edition of Tests is quite dynamic; we also know that some users want to get notified upon changes of the Test/Pre-Condition specification while others don't.

Since Test cases are abstracted as Jira issues, you can also hav e

Thus, we have created a specific event that will be triggered whenever the specification of a Test/Pre-Condition is

In the Test Repository and in the Test Plan Board it's now possible to use a context action over a selected folder, or over some selected Tests, to view the related Test issues in the Issues search page, therefore enabling you to obtain the relevant Tests and do operations with them, if needed.

By the way, moving Tests to the Orphans meta-folder is as simple as using drag&drop.

You can now create Test Executions from the Test Plan Board and inherit, by default, the planning dates.

Also in the Board, creating Test Executions for Tests currently in some status, for a specific Test Environment, can now be done using the "Create Test Execution" over some folder.

Cloning Tests and Test Plans will also clone the related hierarchical information with them:

• whenever cloning and/or moving a Test to some other project, the folder is also created in the destination Test Repository.
• whenever cloning Test Plans, the Board information (i.e. the folder structure) is also cloned.

Learn more here.

A long awaited feature by Java teams was adding support for TestNG.

Now you can submit results from TestNG tests and get visibility of them in JIRA and in the related requirements.

Similar to what is provided for other formats, two REST API endpoints for TestNG are now provided.

We also provide a tutorial, Testing using TestNG in Java, so you can see how it works with a real example.

Learn more here.

Besides performance improvements on this report, you may now see the hierachical information of parent and sub-requirements (up to two levels).

So, if you have an Epic some related Story issues, you will be able to see their relation in the report and evaluate the traceability information for the Epic and also for each individual Story.

Besides this, we added built-in capabilities to make the Traceability Report now exportable to CSV, and include this hierarchical information of course.