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.3.0
XL TestView 1.3.0 release notes
New features
- [TES-381] - Support development of test result parsers
- [TES-56] - Support authenticating against an LDAP server
- [TES-621] - Allow using XL TestView without security
- [TES-587] - Configure XL TestView via xl-testview.conf
Improvements
- [TES-633] - Add documentation for the reports
- [TES-634] - Improved message when test results are available but not within the selected date range
- [TES-659] - Order list of test tools alphabetically in import wizard
- [TES-668] - Set description on all reports
- [TES-680] - Validate events before saving
- [TES-682] - Prevent parallel imports in the import controller
- [TES-747] - ZIP normal log files when rotating
- [TES-761] - Improve showcase data
Bug fixes
- [TES-658] - After session expires and user logs in again, return user to the same screen
- [TES-691] - Fixed issue with historical comparison details report and passed versus failed tests report
Limitations
- Horizontal scrolling of test run details in Safari does not work.
XL TestView 1.3.0 upgrade notes
System administration changes
The default amount of memory has been increased from 1GB to 2GB. Please update any custom server.sh scripts and /etc/default/xl-testview and /etc/sysconfig/xl-testview.
New test tool structure
In previous versions of XL TestView, test tools had generic implementations for various formats. For example, in the previous version, xUnit could support Maven Surefire, Ant, and TestNG generated formats.
As of XL TestView 1.3.0, this is no longer the case. Each test tool and the test result format to be parsed must be made explicit.
XL TestView will upgrade the test tool configurations in your existing test specifications to the new implementation of test tools. The upgrader cannot know which specific implementation it should choose if you were using a generic implementation (such as xUnit). In that case, you will see a warning in <XLTESTVIEW_HOME>/log/upgrade.log and XL TestView will use a default alternative.
By default, the log will show a warning for xUnit and JMeter. The upgrader will replace them with xlt.JUnit (Ant-type JUnit) and xlt.JMeterCSV (for CSV imports), respectively.
You will need to review your test specifications and ensure that the test tool being used is the correct one.
API changes
TestRunsRepository
The TestRunsRepository is injected into Python scripts as test_runs.
For consistency, the methods getPreviousRuns and getLaterRuns have been renamed to getPreviousTestRuns and getLaterTestRuns, respectively. Also, the ordering of the returned runs for getPreviousTestRuns is now ascending.
For all Python extension points, injected properties have been changed from camelCase to snake_case. For reports and qualifications, testRun changed to test_run. For reports, queryParameters has changed to query_parameters, startDate has changed to start_date, and endDate has changed to end_date.
Events
Various properties have been prefixed with @.
