Appearance
AireAssert Release Notes
Version: v1.3.6
Release Date: 23 September 2026
✨ New Features
- Inline Warnings for Unknown Form Controls (AA-677)
- Image Upload Control Support (AA-720)
- Configurable Subject Alias (AA-886)
- Added security.txt for Responsible Disclosure (AA-1000)
- Improved Unsaved Changes Warnings (AA-1014)
- Notification for Unsynced Repository Changes (AA-1023)
- Log Levels for Test Results (AA-1028)
- Faster, More Efficient Saving (AA-1041)
🐞 Bug Fixes
- Fixed Incorrect Form Submission Status (AA-995)
🔧 Tasks
- Cleaner AireForms Logs in Test Results (AA-1034)
- Cleaner AireFrame Logs in Test Results (AA-1035)
- Removed Noisy Action/Page Log Entries (AA-1036)
- More Readable Log Ordering (AA-1037)
- Clearer Error Messages in Logs (AA-1038)
- Improved Log Formatting (AA-1039)
- Removed Redundant Test Start/Finish Log Entries (AA-1040)
- Real-Time Filename Updates (AA-1047)
Detailed Changes
✨ New Features
Inline Warnings for Unknown Form Controls (AA-677)
Description
The test editor now underlines form control references (labels or IDs) that don't exist in the form's test map, in addition to the existing syntax-error squiggles.
What this means for you
When writing or editing a test, you'll immediately see a warning underline if you reference a form control that doesn't actually exist on the form, helping you catch mistakes before running the test.
Image Upload Control Support (AA-720)
Description
Test steps can now interact with image upload controls on forms.
What this means for you
You can now write and run tests that cover forms with image upload fields.
Configurable Subject Alias (AA-886)
Description
AireAssert can now read a tenant's configured Subject alias (for example "Patient" or "Student") from AireFrame, and commands that reference "Subject" will accept the configured alias instead, including its plural form.
What this means for you
If your organisation refers to subjects by another name, you can write your tests using that same terminology instead of always saying "Subject".
Added security.txt for Responsible Disclosure (AA-1000)
Description
A security.txt file has been added, following the industry-standard format, giving security researchers a clear, standard channel for reporting vulnerabilities.
What this means for you
There's now a clear, recognised way for security researchers to report any vulnerabilities they find, helping issues get reported and fixed responsibly.
Improved Unsaved Changes Warnings (AA-1014)
Description
The unsaved changes dialog now offers a "save and continue" option, and it's clearer which files and folders have unsaved changes. This also addresses cases where navigating to and from the manage repositories screen could otherwise leave a test running against an old, unsaved version.
What this means for you
If you have unsaved changes, you can save and continue in one step, and you can see exactly which files or folders still have unsaved edits.
Notification for Unsynced Repository Changes (AA-1023)
Description
AireAssert now notifies you when your repository has unsynced upstream changes, prompting you to sync.
What this means for you
You'll be alerted when there are upstream changes you haven't pulled yet, so you're less likely to work from an out-of-date test repository.
Log Levels for Test Results (AA-1028)
Description
Log entries now carry a level (debug, info, warning or error). Debug-level entries are hidden from the main User Logs by default, though still available under UI Test Logs, and each remaining line shows its level at the start, for example "Info: ...".
What this means for you
The main results screen shows only the log detail that matters to you, with warnings and errors clearly labelled so you don't have to hunt for them.
Faster, More Efficient Saving (AA-1041)
Description
Saving in the UI previously sent the entire test set to the test run manager and re-synced everything with git on every save. Saving now only sends changed data and communicates with git more efficiently.
What this means for you
Saving your changes should feel noticeably faster, especially on larger test sets.
🐞 Bug Fixes
Fixed Incorrect Form Submission Status (AA-995)
Description
A form submission was completing successfully, but AireAssert was reporting it as unsuccessful. This has been fixed so successful submissions are correctly recognised.
🔧 Tasks
Cleaner AireForms Logs in Test Results (AA-1034)
Description
Unnecessary AireForms log entries have been removed from the Test Results screen.
Cleaner AireFrame Logs in Test Results (AA-1035)
Description
Unnecessary AireFrame log entries have been removed from the Test Results screen.
Removed Noisy Action/Page Log Entries (AA-1036)
Description
Internal "### action" and "### page" log entries have been removed from the Test Results screen.
More Readable Log Ordering (AA-1037)
Description
Logs have been reordered to read more naturally, for example simplifying an entry like "### Action: First Name: Setting value to..." down to "First Name: ...".
Clearer Error Messages in Logs (AA-1038)
Description
Error logs previously included a raw error payload and full stack trace. These have been replaced with a concise, plain-language error message.
Improved Log Formatting (AA-1039)
Description
Log output, including embedded JSON, is now better formatted and easier to read, with improved presentation such as colouring and text wrapping.
Removed Redundant Test Start/Finish Log Entries (AA-1040)
Description
The "test started" and "test finished" log entries have been removed from the Test Results screen.
Real-Time Filename Updates (AA-1047)
Description
Renaming a test file now updates the filename shown at the top of the file immediately, rather than only updating the name in the file list.