2.12.1

2.12.1

Released April 26, 2022

Important Notes About This Final Build

macOS

For the macOS app it will not be able to download the Carbon and Automator zips after the .dmg is installed. We have provided a zip file with the application after Carbon and Automator are downloaded and working.

Unzip the application and move it into your Applications folder for macOS users.

You may receive code signature errors as things shut down as well. If you do you will need to accept the unverified publisher prompts and the build should continue to function.

Windows

The first time you start the Windows product, it may close the Window. In this case you just have to wait a few minutes and Test.ai should start working in the background. You can relaunch the Test.ai app from the Desktop icon after a few minutes and it should start successfully.

Non-standard Mode

Test steps with scripts that move the bot into non-standard mode will stop working soon, as they rely on a server that is being shut down and that part of the product cannot be run on a local bot machine. Please convert these steps to template matches if possible, as long as the bot captures a screenshot in standard mode a template match can be created. See the documentation repository that was provided for information on template match creation if you have questions.

Installation

macOS

Pre-install Steps (existing users only)

1. Quit test.ai if it is running and delete the old app from Applications.

2. Back up your test assets (back up the test_ai folder), either by pushing to a repository or compressing to a zip file.

3. Close any browser tabs with the test.ai GUI open and clear your browser cache.

4. If you are using a repository (git based as an example) switch to the main branch and run git clean -xdf. If not using a repository, delete the file name labeler_objects.json in the test_ai/apps/APP_GUID/lkg and the test_ai/apps/APP_GUID/lkg/data folders.

Install Steps

1. For the macOS app it will not be able to download the Carbon and Automator zips after the .dmg is installed. We have provided a zip file with the application after Carbon and Automator are downloaded and working. Download the macOS application: https://drive.google.com/file/d/1KhViXovYjA0prQGMPXOsNPq9cQ3fcAe9/view?usp=sharing

2. Unzip the application and move it into your Applications folder for macOS users.

3. You may receive code signature errors as things shut down as well. If you do you will need to accept the unverified publisher prompts and the build should continue to function. You may need to right click and choose open app to get the code signature prompt that allows you to move forward with installation.

Windows

Download the Installer

1. Download the Windows installer: https://drive.google.com/file/d/1fifjJi3LZa3lp87Es-xV1U3MP7bVWsBj/view?usp=sharing

Pre-install Steps (existing users only)

1. Quit test.ai if it is running by stopping the terminal session (control + c) and go to Apps & features to uninstall the old app.

2. Back up your test assets (back up the test_ai folder), either by pushing to a repository or compressing to a zip file.

3. Close any browser tabs with the test.ai GUI open and clear your browser cache.

4. If you are using a repository (git based as an example) switch to the main branch and run git clean -xdf. If not using a repository, delete the file name labeler_objects.json in the test_ai/apps/APP_GUID/lkg and the test_ai/apps/APP_GUID/lkg/data folders.

Install Steps

1. Double click the test.ai .msi and follow the installer prompts.

2. The test.ai Download Client will automatically be downloaded, installed.

3. When done you can click the optional Launch test.ai checkbox in the final installer dialog to start test.ai automatically when you click the Finish button. If you choose not to automatically launch test.ai, you can double click the test.ai app icon installed on the desktop or search for test.ai and click the application icon to start test.ai.

4. A terminal window will launch where test.ai is running. This may take a couple minutes and the terminal window may disappear (see Important Notes section above).

5. A browser tab or window with the test.ai GUI will open automatically when the product is ready for authentication and use.

6. By default the product is ready for Web automation. Follow the instructions at docs.test.ai to install the necessary components for Android testing.

📈 Enhancements

• When starting an Explore crawl or Test run, the browser to use can now be selected on the Start Explore and Run Tests pages.

• The Chrome browser can now optionally be run in “headless” mode, meaning the browser will not be visible or interfere with the user’s actions.

🛠️ Fixes

• The labeler_objects.json file should now be much smaller and the editor should load faster even for large data sets.

  • As part of this fix a new file named text_to_screens.json is generated that should be added to the .gitignore for anyone using a repository.

  • The new file is located at test_ai/apps/APP_GUID/lkg/data/text_to_screens.json please add the appropriate line to your .gitignore based on your repository.

• The “Set Dropdown” action now has an option for selecting the swipe direction for all mobile platforms.

• Toast messages on the data sharing setting page in Configurations should not pile up anymore.

• From the Test Results Detailed View page we should be able to see and access the fullscreen icon if we hover anywhere on the screen/card.

• Fixed a bug with the swipe action and it should now work again on every platform.

⚠️ Known Issues

• Web platform Set Dropdown interaction is not saving the correct data type (Index, Value, Text) in certain cases. This will save correctly if the Index or Value to use is entered into the text field first, then the Index or Value radio button is selected.

• File type validation messages are not triggered when adding app files via drag and drop. Supported file types are:

  • Android - .apk

  • iOS simulator - .zip

  • iOS physical - .ipa

• Newly created Template Matches do not display in Editor right away.

• Labeling a second element in an individual step in manual mode is taking longer than normal. The first label is applied very quickly. Try to only label one element per step in manual mode (may also happen in normal editor but that has been sporadic).