ElasTest Release Notes v0.9.1

Patxi Gortázar (Universidad Rey Juan Carlos)


One year after starting the development efforts in the project we are shipping a new version which includes many important new features we’ve been developing during the last four months. This new ElasTest release, version 0.9.1, has brought some new features, along with a more stabilized core platform. The following is a list of the main improvements in the project:

  • Jenkins integration. You don’t need to abandon your CI tools. Use ElasTest straight from your Jenkins jobs (Freestyle or Pipeline). For instance, if you’re using Pipeline jobs, just wrap up your Pipeline in an elastest step, and you’ll be ready to use all the fancy features we bring to testers and developers, like managed browsers! See our advanced example for a more complex scenario.
  • TestLink integration. TestLink is the most widely used web-based test management tool and ElasTest provides integration with TestLink. With this integration now you can easily record videos and gather logs and metrics when manually running your tests.
  • New Docker images for browsers. We have been developing a new set of browser Docker images that brings the benefits of both Selenoid and Selenium docker images. These images are ready for some awesome features we will be developing in the following months, like changing browser resolution to adapt better to the desktop of our users.
  • Browser recordings can now be opened as a new tab or on a floating dialog.
  • Our powerful Log Analyzer now remembers previous configurations.
  • Generate your SuT on the fly with Commands Containers: a new Docker image can be generated on the fly, and this image will be run as the SuT.
  • ElasTest Command line options documented in its own subsection within the installation page
  • Changes in environment variables: the ElasTest endpoint for sending metrics from an external SuT has changed, and the ET_MON_LSHTTP_API environment variable is now available also for Test Support Services.
  • There are new environment variables available: ET_SUT_CONTAINER_NAME, ET_MON_INTERNAL_LSBEATS_PORT and ET_SUT_LOG_TAG. Those allows ElasTest to do a better job when identifying what’s coming from which SuT.
  • We have changed the name of the status for a TJob that has been stopped manually to STOPPED.

If you want to give it a try, follow our (brief) instructions here. If you already have ElasTest installed, update instructions can be found here in the Update section.

Please, if you find any issue, let us know by reporting it in our issue tracker using the template provided.

Do you want to support the project, and keep it going? Give us extra energy by starring the ElasTest repository!!