Technical and Security Information for Whitelisting algoAI

TABLE OF CONTENTS

1. algoAI Whitelisting Overview

2. Purpose And Function

3. Security and Behavior Summary

4. Build Source and Integrity

1. algoAI Whitelisting Overview

Executable Name: algoAI.exe

Version: 5.0.1

SHA-256 Hash: b579438c5fe0b05458ea1d21c636aa0417ed54d1f44b6fe03fd1121f3da837af

File Location: ../ScriptGeneration_<timestamp>/AlgoAFScript_<timestamp>/

Note:

• This executable is unsigned and does not include embedded metadata.
• It is developed and maintained under strict internal version control.
• The provided SHA-256 hash is the authoritative method for verifying the integrity of the distributed file.

2. Purpose And Function

Purpose: This tool developed by AlgoShack, enables autohealing of test automation scripts and comes integrated with scripts generated through algoQA.

Usage Context: Will be triggered only when the autohealing flag in the script’s ApplicationSettings.xml is set to ‘True’.

Whenever a script fails due to locator issues, algoAI.exe relays the failure information to algoQA backend. This information is then processed to heal the failing locator and subsequently the ObjectRepository.yml of the script is updated. The updated locator information is also available in algoQA.

3. Security and Behavior Summary

4. Build Source and Integrity

Source Code Repository: Internal GitHub

Build Process:

• The executable is built using PyInstaller
• Only authorized engineers can trigger or modify builds
  
  

Integrity Verification:

• File integrity validated via SHA-256 hash.
• File verified clean via antivirus scan prior to release.
• File not downloaded from public sources – distributed only through internal channels.