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.3

    XL TestView 1.4.3 release notes

    New features

    • [TES-1054] - Aggregated bar chart report for test specification sets

    Bug fixes

    • [TES-1039] - Performance of qualification from Elasticsearch to JCR upgrade degrades exponentially
    • [TES-1043] - Improve robustness of upgrade process around Elasticsearch

    Improvement

    • [TES-1040] - Small performance improvements
    • [TES-1050] - Upgrade windows service wrapper
    • [TES-1052] - Improve labels on Y-axis of the duration report

    XL TestView 1.4.2

    XL TestView 1.4.2 release notes

    Bug fixes

    • [TES-1036] - Rendering issues on Internet Explorer

    Improvement

    • [TES-1037] - Cleaned up demo project test materials

    XL TestView 1.4.1

    XL TestView 1.4.1 release notes

    API Change

    • [TES-986] - The '.' in the keys of the performance test result properties were replaced with '_'

    Bug fixes

    • [TES-1004] - Durations report should not fail on functional results without duration
    • [TES-1005] - TestRun overview should not fail on functional results without duration
    • [TES-1012] - When importing results via REST, a duplicate hierarchy exception should not result in 500 error
    • [TES-1013] - Handle duplicate test results in jUnit/TestNG/Cucumber by merging them
    • [TES-1026] - Executable test specifications create an extra empty failed run
    • [TES-1028] - Some demo projects do not run on Microsoft Windows

    Improvement

    • [TES-450] - Service scripts for Windows and Unix
    • [TES-702] - Support Active Directory authentication
    • [TES-1003] - Functional result @duration is not sufficiently checked
    • [TES-1009] - Make ES upgrader batch size configurable
    • [TES-1025] - Improve logging for Elasticsearch

    XL TestView 1.4.1 upgrade notes

    Duplicate test results merging

    The TES-966 bug fix in XL TestView 1.4.0 had bigger impact than expected. This bug fix enforced that all test results in a test run would be unique with respect to the hierarchy. This enforcement was too rigorous. In XL TestView 1.4.1, all test results with the same hierarchy are merged into one 'merged' test result. The original events are stored on the @mergedEvents field.

    Performance Result Key Rename

    This API change is required in order to upgrade to newer Elasticsearch versions in future (major) versions.

    XL TestView 1.4.0

    XL TestView 1.4.0 release notes

    New features

    • [TES-336] - Make 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 layout and filtering in details report
    • [TES-928] - Make REST API to query available qualifications and test tools

    API Change

    • [TES-888] - Change 'source' metadata to 'ciSource' for functional result events
    • [TES-965] - Add 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
    • [TES-1030] - Upgrade FitNesse to 20151230

    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 xlt.elasticsearch.data configuration property is deprecated and now ignored. The original property only relocated the test results data directory but did not relocate configuration data. XL TestView now has a xlt.data configuration property that you can use 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 use 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: Ensure that 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 boolean hasTestRuns(String testSpecificationName) method returns true if the given test specification has at least one complete test run.

    Copyright 2015. XebiaLabs, Inc. All rights reserved