• Fixed: Cancelled test jobs were too long. TestEngine did not create reports for such jobs.

• The Overview page now contains information only about not finished test jobs (running and in the queue) as well as the 5 most recent finished test jobs. You can find information about the finished test jobs on the Run History page.

• Now, you can enable JDBC connections directly in TestEngine’s installation wizard.

• We have improved the text of the error messages that TestEngine shows when it does not have a valid license or when users send a broken project.

• Now, you can remove test jobs from the web interface. Just click  next to the test job you want to remove.

• The Overview page in the web UI was updated:

  • The new Tags column shows which tags were used to run a test job.

  • Filters now are always visible, and you can filter jobs by tags as well.

  • Besides that, now, you can search for a specific test job by a string included in its project, author, status, type, or tag.

• A couple of bugs have been fixed:

  • TestEngine responded with 500 Internal Server Error when you sent GET /testjobs/{testjobId}/transactions.

  • TestEngine could not handle property expansions properly.

API Definition v.1.8.0 at SwaggerHub

• Now you can remove a single test job from the TestEngine database. To do this, use the DELETE method of the /testjobs/{testjobId}/delete resource. To learn more, see Remove Jobs.

• A number of security issues have been fixed.

API Definition v.1.7.0 at SwaggerHub

• Now, by default, TestEngine blocks JDBC connections in tests because they may expose sensitive information. Administrators can enable JDBC connections by using the Allow test steps connecting to databases using JDBC setting.

• Update the ReadyAPI dependency to 3.4.0.

  Starting from 1.14.0, TestEngine does not support Protection! License Server version 4.x. See Upgrade License Server to 5.x.

• Jenkins plugin improvements:

  • Now, you do not need to pack a composite project into a zip archive.

  • Now, you can run prioritized tests.

API Definition v.1.6.0 at SwaggerHub

• JSON reports now include information about passed assertions.

• Fixed: When TestEngine could not access the file, the error was not informative enough.

• Fixed: When a test contained the Properties test step that did not read properties from a file during a test, TestEngine posted an error.

API Definition v.1.5.0 at SwaggerHub

• The new PUT method of the /testjobs/{testjobId} resource modifies the priority of an existing test job.

• High-priority jobs are now marked with the  icon in the web UI.

• When you restart TestEngine, it reconnects to a floating sever automatically.

• The bug with losing the Environment parameter in the queued job has been fixed.

• A number of security issues have been fixed.

API Definition v.1.4.0 at SwaggerHub

• A number of security issues have been fixed.

API Definition v.1.3.0 at SwaggerHub

• The POST method of the /testjobs resource has a new parameter - priorityJob. Use it to run a test before other tests in a queue. To learn how to run test jobs, see Run Tests.

• Now, you can use the tag parameter for running test suites.

• Update the ReadyAPI dependency to 3.2.5.

API Definition v.1.3.0 at SwaggerHub

• TestEngine now supports security tests.

API Definition v.1.2.0 at SwaggerHub

• The bundled JRE for the Linux installer has been updated.

API Definition v.1.1.0 at SwaggerHub

• Back end:

  • Update the ReadyAPI dependency to 3.1.0.

  • Update the Java version to 11. If the zip distribution is used, a new Java version needs to be set up (Java 11 or later).

  • Stop using "testengine" as the default password. Instead, enter the password in the installer or as startup parameters. If no password is provided, a random password will be generated and printed in the console during the first startup. Old installations are not affected by this when upgrading.

  • The security fix of WebSocket tokens.

API Definition v.1.1.0 at SwaggerHub

• Front end:

  • Minor UI fixes.

• Back end:

  • It is possible to get a token and use it as a bearer token instead of using basic authorization.

API Definition v.1.1.0 at SwaggerHub

• Front end:

  • Minor UI fixes.

• Back end:

  • It is possible to install TestEngine as a Windows service.

API Definition v.1.0.4 at SwaggerHub

• Front end:

  • Minor UI fixes.

API Definition v.1.0.4 at SwaggerHub

• Front end:

  • Minor UI fixes.

• Back end:

  • Reports are in the PDF format.

  • Tuning of groovy script security.

  • The possibility of using a full URL in a transaction log.

API Definition v.1.0.4 at SwaggerHub

• Front end:

  • The third-party libraries have been upgraded to be up to date.

  • Minor UI fixes.

API Definition v.1.0.3 at SwaggerHub

• Back end:

  • The third-party libraries have been upgraded to be up to date.

• Front end:

  • Part of third-party libraries has been upgraded to be up to date.

  • Minor UI fixes.

API Definition v.1.0.3 at SwaggerHub

• Back end:

  • It is possible to specify a timeout for a job.

• Front end:

  • A better tooltip in the test jobs graph.

  • Redirecting when opening the application with no license present has been improved.

API Definition v.1.0.3 at SwaggerHub

• Back end:

  • Using ReadyAPI 2.8.2 internally.

  • A floating license can be installed even if the server is not listed in the Allowed connection targets.

• Front end:

  • The license section has moved to a separate tab.

  • Expose settings for database cleanup on the settings page.

API Definition v.1.0.3 at SwaggerHub

• Back end:

  • Automatic cleanup of test jobs.

  • Negative performance timing has been fixed.

• Front end:

  • Update the Settings UI.

  • Get a test job ID from the UI.

API Definition v.1.0.2 at SwaggerHub

• Back end:

  • Using ReadyAPI 2.8.0 internally.

  • The bug when installing a floating license after a trial one has been fixed.

  • In JUnit reports, canceled steps have been marked as failed.

  • The TestEngine version is now shown on startup and in /api/v1/version.

  • The API to clean up test results has been improved.

• Front end:

  • Save Server Settings on the Enter key.

  • Redirect to log in even from the 404 page when logged out.

API Definition v.1.0.1 at SwaggerHub

The initial version.

API Definition v.1.0.0 at SwaggerHub