Klaros-Testmanagement 4.4.3 released

Klaros-Testmanagement 4.4.3 released - Klaros-Testmanagement

We are pleased to announce the release of Klaros-Testmanagement version 4.4.3.

This is a hotfix release that adresses a performance problem introduced in release 4.4.3.

The 4.4.x release of Klaros-Testmanagement focuses on issue management system and requirements management system integration and includes more than 8 new features and over 29 improvements and bugfixes over 4.3.x. Changes include:

Synchronization of requirements from remote requirements management systems (RMS) is now possible. Instead of duplicating existing requirement definitions by hand, you can now synchronize with an external JIRA 4.3 project (or newer). Custom JIRA-fields are supported as well as file attachments.

Besides Jira, Mantis, Bugzilla and Redmine, the integrated Issue Tracker of GitHub is now also supported for remote issue tracking.
The Enterprise Edition of Klaros-Testmanagement now ships with a RESTful API that enables developers and users to read data from Klaros using a REST client.
Customizable Reports for Issues and Jobs
GoogleTest, TESSY, JsUnit, JBehave, gtester and embUnit join our constantly expanded list of test result formats.
From JIRA 7.0 onwards (resp. 6.0 when using Atlassian Cloud), two of JIRAs remote APIs (XML-RPC and SOAP) are being turned off. To be still compatible, Klaros-Testmanagement now supports JIRAs REST-API.
You can now filter for testcase-categories and testsuite-categories while you're creating jobs from testcases or testsuites.
It is now possible to show user defined property values during manual test execution! For example, if you write %sut:build-number% in the description of the test case, it will show the build number of the system under test the executing user is testing on instead.