Features & Improvements
- We've made improvements to the Documentation.
- We have improved example projects and added new ones. The technologies used are Java JUnit5, Java JUnit4, Python, JS Jasmine, JS Protractor, Java Karate, Java Cucumber and Java Gauge.
- It is no longer necessary to specify the
--server-address=localhostwhen running on MAC or Windows (In docker for Windows, in Docker toolbox
--server-address=$(docker-machine ip)is still necessary).
- All active live sessions are now shown in Web Browsers section.
- A button to restore the demo projects has been added on the project card.
- ElasTest Jenkins Plugin has been updated to Java 8.
- A system of retries has been added to send the traces to ElasTest in the ElasTest Jenkins Plugin.
- The use of Suts managed by ElasTest is allowed now in ElasTest Jenkins Plugin.
- Logstash has been updated to 6.5.0 version (Logstash is only available in Elastest experimental mode)
- Now the tests can use a single browser for all the tests but the videos are associated with each test.
- Now the environment variables ET_SUT_PORT and ET_SUT_PROTOCOL are passed to the test container.
- The error on open Monitoring Config modal during the TestLink Test Plan execution has been solved.
- In LogAnalyzer, when "Reload Log" button is clicked the multiline log is maintained (if activated).
- If you open the Web Browsers page during the execution of a TJob that uses a browser, they no longer appear.
- Fixed problem when sending traces with characters without escaping in ElasTest Jenkins Plugin.
Features & Improvements
- Multi-configuration TJobs. Execute same TJob with different configurations, compare several executions and improve visualization with matrices and graphs (Basic Orchestration).
- New type of Sut: Use External Elasticsearch.
- Now the init/pull progress of the browsers is shown in the modal window.
- ElasTest Internal Error messages are now displayed on the results page of a TJob Execution.
- Ability to duplicate TJobs and Suts on the specific project page.
- Now the list of executions is reloaded when deleting a project in the Dashboard section.
- Automatic sync when TestLink is started manually and be ready to show projects directly instead of needing to re-navigate
- Now you can configure the ElasTest data folder at startup. If the folder is changed in future startups, the contents of the config folder must be copied if TL was reached at any time.
- TestLink and Jenkins credentials. The credentials will be the same credentials as those introduced for ElasTest. If it has not been entered, they will be created.
- Manually started browsers can now be opened in a new tab.
- Now it shows where the logs and metrics of a TJobExec are stored (MYSQL if it is mini or ELASTICSEARCH if it is experimental)
- Now the volumes created by the execution of a TJob are removed at the end of this.
- Error message on start ElasTest if main container (ETM) is exited. An error file is also generated in case the user wants to send it to the ElasTest team.
- The time conversion of the monitoring traces is now more efficient. It is calculated once per host name and only transforms if necessary.
- Now the connections to the WebSockets are reconnected automatically if the connection is lost.
- Automatic navigation to the results page when the execution of the test finishes.
- Problem with duplicate logs fixed.
- Automatic subscription to the Sut logs of a Jenkins execution.
- The problem with the generation of the Jenkins url when starting from the platform in experimental mode and as a server has been solved.
- Bug with the Nginx proxy image fixed. It did not receive the SIGTERM signal and ElasTest Platform took a long time to stop (until it gave a waiting time of 90 and stopped the proxy to force)
- Startup problems in Windows and MacOS has been solved. Now the volumes
/etc/timezoneare no longer binded to the
elastest/etmcontainer; instead ElasTest Platform is that requests it via HTTP and sends it as a parameter to the ETM.
- Both Jenkins and the ElasTest plugin are now correctly configured when Jenkins starts from the Platform.
- Problem with splitted log traces and without date has been fixed.
Improvement in requirements. We've been working on the high memory consumption requirements of previous versions, and this new version can be deployed on machines with 8Gb of RAM starting ElasTest in default mode
GUI improvements. Among other small improvements, it should be noted that more information is now shown to the user, such as the percentage of downloading a docker image, either from a tjob, a sut or a browser.
Improvements in Jenkins plugin. It is no longer necessary for the user to start dockbeat and filebeat to send logs and metrics to ElasTest, the plugin is responsible for it now.
Jenkins instance provided by ElasTest. You can use now a Jenkins instance provided by ElasTest, can be started on load ElasTest or later manually from the ElasTest GUI.
Improvements in TestLink integration. It is possible to configure a Sut so that ElasTest starts it every time a Test Plan is executed
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.