Release Manual

    Upgrade instructions

    For upgrade instructions, refer to Upgrade XL TestView.

    Important: If you plan to skip versions when you upgrade, ensure that you read the version-specific upgrade notes for each intermediate version. You may be required to perform manual actions as part of the upgrade.

    XL TestView 1.4.0

    XL TestView 1.4.0 release notes

    New features

    • [TES-336] - Make the reports available for super sets
    • [TES-405] - Support Microsoft .trx file format for functional (unit) test results.
    • [TES-412] - REST import for test results
    • [TES-715] - Introduce 'other' state for functional test results
    • [TES-805] - Make REST API for passive test specifications
    • [TES-889] - Make REST API for projects
    • [TES-913] - Allow XL TestView data folder to be relocated
    • [TES-917] - Improve details report: layout and filtering
    • [TES-928] - Make REST API to query available qualifications and test tools

    API Change

    • [TES-888] - Change 'source' metadata into 'ciSource' for functional result events
    • [TES-965] - Added hasTestRuns() to TestRunsRepository API

    Improvements

    • [TES-618] - Improve performance of test specification loading page
    • [TES-734] - Always check test result location during import via wizard
    • [TES-857] - Allow setting of qualification in import wizard
    • [TES-992] - Shorten test specification name in overview

    Bug fixes

    • [TES-801] - Improve feedback when import fails
    • [TES-881] - Test run overview report should not show qualification when no qualification is configured
    • [TES-884] - Spinner does not stop when editing a test specification set
    • [TES-948] - Report button is shown even if the only (first) import fails and no test-runs are available
    • [TES-966] - Ensure test result full name (hierarchy) is unique
    • [TES-974] - Durations report colors in selects do not match graph
    • [TES-979] - Karma unit result parser should add "class name" to the hierarchy

    XL TestView 1.4.0 upgrade notes

    Upgrade Java version

    XL TestView 1.4.0 requires Java SE Development Kit (JDK) 8. Java 7 is no longer supported.

    Configuration changes

    The configuration property xlt.elasticsearch.data is deprecated and now ignored. The original property would only relocate the test results data directory but not the configuration data. XL TestView now has a configuration property xlt.data that can be used to relocate both the test results and configuration data. The test results and configuration data directories will be created beneath this directory. This way it is possible to move all data outside the normal program directory.

    Karma test result parser

    The Karma test result parser now includes the "classname" property in its hierarchy. This makes the (Jasmine) tests read more like sentences.

    API changes

    REST API

    A public REST API is now available for managing projects, managing test specifications, and importing test results.

    The endpoint /api/v1/qualifications?testSpecification=[id] has been deprecated. Use /api/v1/projects/[project-id]/testspecifications/[test-specification-id]/qualifications instead.

    Importing tests with duplicate names no longer allowed

    XL TestView has to be able to uniquely identify tests over time in order to do reporting and qualification. Therefore it enforces the fully qualified test names (a.k.a. "hierarchy") to be unique when importing test results.

    If you're using a test tool that allows duplicate naming, ensure that fully qualified test names are unique.

    Test results that have already been imported are left untouched.

    Important: make sure this is not an issue before you upgrade.

    Event structure

    The 'source' property in functional test results has been renamed to ciSource. This property is set when importing data from Jenkins via the XL TestView Jenkins plugin.

    TestRunsRepository

    The new method boolean hasTestRuns(String testSpecificationName) returns true if the given test specification has at least one complete test run.