TestEngine バージョン履歴
1.19.0 (2021-02-11)
1.18.0 (2021-02-01)
-
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.
1.17.0 (2020-12-17)
1.16.0 (2020-12-03)
1.15.1 (2020-11-18)
-
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
1.14.0 (2020-10-22)
-
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.
-
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
1.13.0 (2020-09-23)
-
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
1.12.1 (2020-09-01)
-
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
1.11.0 (2020-07-02)
1.10.0 (2020-06-04)
-
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
1.9.1 (2020-05-06)
1.8.2 (2020-03-27)
1.8.1 (2020-03-19)
-
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
1.7.0 (2020-02-13)
1.6.0 (2020-01-15)
1.5.0 (2019-12-05)
1.4.0 (2019-11-20)
-
Front end:
-
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
1.3.0 (2019-11-06)
1.2.0 (2019-10-23)
1.1.0 (2019-10-09)
1.0.3 (2019-09-25)
1.0.2 (2019-09-13)
1.0.1 (2019-08-29)
-
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:
API Definition v.1.0.1 at SwaggerHub
1.0.0 (2019-08-13)
ページ トップに戻る