Scenarioo Release Notes

WIP Version 6.0.0

Frontend Modernisation

Breaking Changes and Backwards Compatibility

TODO Currently no breaking changes are known - please list here if any.

  • Maybe Elasticsearch Upgrade ??

Supported Scenarioo Format

  • The used Scenarioo Data format is still version 2.1. You can safely use Scenarioo 5.0 with the same data format as before and do not have to upgrade the used Scenarioo writer library to use the new Scenarioo viewer version.
  • The internal format has not been changed either, so you do not even have to reimport your builds that have been imported with the previous version in the data directory. All build and comparison data will still work with the new version.

Fixed Issues

See complete List of Fixed Issues in this Release.

Known Issues

See List of Known Issues on GitHub.

Feedback and Support

Don't hesitate to open new issues if you find a bug or problem, or have feedback or questions: https://github.com/scenarioo/scenarioo/issues/new?labels=feedback

Version 5.0.2

Bugfixes

Version 5.0.1

Bugfixes

Version 5.0.0

Scenarioo Standalone Runner

Small Fixes and Improvements

Breaking Changes and Backwards Compatibility

  • Changed Configuration of password for secured REST API calls: The security mechanism for secured REST endpoints (e.g. to upload a build via REST call) has changed. Therefore the password for these rest endpoints needs to be configured differently. For more details, please refer to the Migration Guide on how to adjust this configuration when migrating.

Apart from this small config change there are no other breaking changes.

You can still deploy Scenarioo as a WAR to your Tomcat, although this is not needed anymore by using the new standalone deployment, as mentioned above.

Supported Scenarioo Format

  • The used Scenarioo Data format is still version 2.1. You can safely use Scenarioo 5.0 with the same data format as before and do not have to upgrade the used Scenarioo writer library to use the new Scenarioo viewer version.
  • The internal format has not been changed either, so you do not even have to reimport your builds that have been imported with the previous version in the data directory. All build and comparison data will still work with the new version.

Fixed Issues

All issues fixed in this release: List of Fixed Issues.

Known Issues

Please visit our List of Known Issues on GitHub.

Feedback and Support

Don't hesitate to open new issues if you find a bug or problem, or have feedback or questions: https://github.com/scenarioo/scenarioo/issues/new?labels=feedback

Version 4.0.1

Bugfixes

  • #751 - Sharing Step Screenshot Sharing screenshot images through direct links with other applications works again, also the share this page dialog shows the correct link again.

Version 4.0.0

Feature "Diff Viewer Plus"

Improvements to the Diff Viewer for Visual Regression Testing:

Feature "Configuration"

  • The data directory can not be configured through the config UI anymore (for security reasons)
  • The data directory can now be configured through an environment variable or in the context.xml file of the web server (or just by directory mapping on the docker container, similar to before).
  • The configuration file of Scenarioo is now stored in the data directory. Make sure you move your old config.xml file to the data directory.
  • See Migration Guide for more detailed explanations.

Features "Small Improvements & Fixes"

Further small improvements and bug fixes:

Breaking Changes and Backwards Compatibility

  • Changed configuration of data directory location: you need to setup your data location and the configuration file as explained in the Migration Guide. This can not be configured through the frontend anymore.

  • Internal format of comparisons between builds (DiffViewer feature) has changed: after an update to the new version you will see no calculated comparisons on old builds anymore and need to reimport those builds for which you want to calculate and see comparisons again. See step 3 in Migration Guide.

  • Full Text Search needs Elasticsearch Version 5: we upgraded the full text search feature to use Elasticsearch 5.6.9. If you want to use that feature your have to configure a compatible Elasticsearch server and a cluster name as described in Full Text Search Setup Guide

  • Some undocumented REST endpoints for the frontend have slightly changed: in case you used these services you have to adjust the usage:

    • /builds/reimportBuild/{branchName}/{buildName} is now /builds/:branchName/:buildName/import

Apart from that there are no breaking changes.

The Java Writer Library in use is still version 2.1 which is still compatible with Java 6 and upwards. Also the internal format version is not increased (still 2.1) so that your existing documentation data does not even have to be reimported after the upgrade and will continue to work with the new version (except for the comparisons).

Fixed Issues

All issues fixed in this release: List of Fixed Issues.

Known Issues

Please visit our List of Known Issues on GitHub.

Feedback and Support

Don't hesitate to open new issues if you find a bug or problem, or have feedback or questions: https://github.com/scenarioo/scenarioo/issues/new?labels=feedback

Version 3.0.0 and Earlier

See https://github.com/scenarioo/scenarioo/releases

results matching ""

    No results matching ""