Version 2021.2.1

Release Notes (Release Date: 2021-08-17)

We've introduced a new way of signing in, providing a unified experience across all products. In addition, users with multiple Swiftest subscriptions can choose the subscription when signing in.
Users can choose whether web browsers should remain open when a text execution fails. This user preference is editable via the Tools/ Options dialog.
The Project, Scenario, and Test names were added to the Create Action screen so that users can see which test they are updating.
The Project, Scenario, and Test names were added to the Execute Test screen so that users can see which test they are executing.
There are now four new "built-in" Datastore items, allowing you to create actions that compare values with "Blank", "Null", "Empty", or "Zero".
The log file output for the Swiftest Command-Line now gives feedback if you're missing the "-command" argument.

Swiftest now supports E1 Orchestrations via the new Run Orchestration action. See the relevant how-to guide for more information on how to configure the software for your environment.

We've made various performance improvements around executing tests to make the application more responsive and prevent hanging.
When working with actions in a test, copying a group into itself was possible, causing an infinite loop and rendering the test unusable.
When saving a test queue execution containing a large test execution, the application would time out waiting for the test execution to be saved.
When editing a group action, the flyout was abnormally large, with a horizontal scrollbar at the bottom of the window.
Under certain circumstances, an "Unexpected Error" pop-up would be displayed when running a queue containing a test that a user didn't have permission to access. The queue now correctly skips that test and then fails gracefully.

Previously, the application would crash when copying old actions that didn't yet have E1 APPL, FORM, and VERSION values.
Under certain circumstances (when multiple items existed on a page with the same name but different HTML IDs), the "Form/Row Exit Sub-Menu" action would fail.

When using the API to create a Repository with a duplicate name, the API would respond with a generic HTTP 500 error. It now responds with a more descriptive message.
Data in a repository datastore could previously not be updated.

To read the previous release notes, for version 2021.1, click here.
To read the next release notes, for version 2021.3, click here.