Applies to TM4J Cloud, last modified on July 20, 2020.

Check out what’s new for TM4J Cloud in 2020. Here are the changes we document:

New Features - Brand new functionality to help you improve your testing efforts.

Updates - Changes we’ve made, large and small, that we want you to be aware of.

Bug Fixes - Issues we’ve resolved to make TM4J work as designed.

July 16, 2020

New Features

Due to popular demand, we’ve introduced two new scorecard reports under the reporting section.

Test Execution Scorecard by Test Cycle 

Due to popular demand, we’ve introduced two new scorecard reports under the reporting section.

This report provides a test execution results scorecard broken down by test cycle, giving you a granular view of activity for each test cycle, including:

  • Percentage of test executions in each status.
  • Percentage of test executions completed vs remaining.
  • A comparison between the estimated and actual effort, and the variation between the values.
  • The number of Jira issues that are open and closed relating to the test cycle.

Test execution scorecard by test cycle

Test Execution Scorecard by Tester

This report provides a test execution results scorecard broken down by tester, giving you a granular view of activity for each tester, including:

  • Percentage of test executions in each status.

  • Percentage of test executions completed vs remaining.

  • A comparison between the estimated and actual effort, and the variation between the values.

  • The number of Jira issues that are open and closed relating to the test cycle.

Test execution scorecard by tester

Improvements

  • We added tooltips to the donut report in the Test Execution Results Summary report so that you can easily see the number of executions.

    Test execution results (summary)

  • We added scrolling to the Traceability Matrix report. 

Bug fixes

  • We fixed a bug with the Test Execution Results By Coverage report, where issue names overlapped if there were a certain number of issues included.
  • We fixed a bug where the gherkin syntax in the test player was not displayed correctly when using “call to test” steps.
  • We fixed a bug where users were unable to post the correct number of executions when using “call to test” in a test case.

June 30, 2020

Bug fixes:

  • We fixed an issue where the traceability matrix report was not printing any details.
  • We fixed an error in /tm4j/v2/automations/executions/cucumber when Cucumber step had other status like skipped or pending.
  • We fixed an issue where deleting all test case steps over multiple tabs leaved users with no steps.
  • We fixed an issue where the traceability report print contained invalid characters (PDF).
  • We fixed an issue where the new traceability report was failing with no filter selected.
  • We fixed an issue where the new traceability report only showed 50 issues, any others were hidden.
  • We fixed an issue where users were not able to delete the test case link to user story.

May 31, 2020

Bug fixes:

  • We fixed an issue where test cases did not load in test player sporadically.
  • We fixed an issue where deleted test plans still showed in reporting/gadgets.
  • We fixed an issue with the test execution results (detailed) report showing issues as null.
  • We fixed an issue where Excel export failed in Chrome.
  • We fixed an issue where users were not able to clone test cycle with custom field on test case steps.

April 30, 2020

Bug fixes:

  • We fixed an issue where the REST API returns 500 rather than 404 when making a request for a path that didn't exist.
  • We fixed an issue where users were unable to see more than 5 environments when performing quick execution.
  • We fixed an error when a test execution was looked by key (key duplicated).
  • We fixed an error where the test result custom field did not work in reports.
  • We fixed an error with creating test case via REST API using special characters.
  • We fixed an issue where users were unable to open test cases in Microsoft Edge.
  • We fixed an issue where the drag and drop for test steps inside test script wasn’t working.

February 10, 2020

Update: Removed Project Selector

Due to an increasing number of permissions issues and other irritating inconsistencies, we’ve removed the project selector. Now, if you’d like to switch projects, please use the Jira project selector.

While it rarely feels good to remove such a feature, we’re confident in the change thanks to many conversations with you, our customers.

February 5, 2020

New Feature - Four New Traceability Reports

Four traceability reports are now available in the primary reports section.

The traceability reports that were previously available as legacy reports also remain in the legacy section. However, the new reports have improved filtering and are more visually appealing.

New Feature - 16 New Gadgets

We added 16 new TM4J gadgets (for a new total of 18), which are now available for Jira dashboards.


Highlight search results