Avo Assure - User Guide v24.2

Avo Assure - User Guide v24.2 Avo Assure - User Guide v24.1 Avo Assure - User Guide v23.1

Avo Assure - User Guide v24.2

Avo Assure - User Guide v24.2 Avo Assure - User Guide v24.1 Avo Assure - User Guide v23.1

Getting Started with Avo Assure
- Commence Avo Journey
- Support & Learning Sphere
Introduction to Avo Assure
Avo Assure Architecture
Avo Assure Installation Requirements
- System Requirement
  - Server Requirements for Avo Assure Installation
  - Client Side Requirement
- Browser Requirement
Administration
Working with the Avo Assure Platform
Avo Intelligence (Gen AI)
- Generate AI Test case by Uploading Requirements Document
Utilities
- Encryption
- Data Table
Integrations in Avo Assure
Actions

Powered by GitBook

On this page

Syntax
Usecase/Example

Was this helpful?

Actions

Generic

File and Folder Actions

Compare Files

PreviousBeautify NextCompare Inputs

Last updated 3 days ago

This Action resides under the @Generic Element Name and directs the Avo Assure Client to compare the contents of specified files (.txt, .xml, .json). It calculates and saves the "number of differences between files" in the output variable.

Syntax

Input: <Filepath-Original File>; <Filepath - File to Compare>;<Selective/All(Optional)>

Note: By default, the final argument in the above syntax is "all" and will store all file’s content in the Output variable and if final argument is written as ‘Selective’ then Output variable will display selective data of file.

Output: <Dynamic Variable>;<Dynamic Variable>(Optional)

Usecase/Example

Scenario: Configuration File Validation in a Software Release

When you are User for a software product that undergoes regular updates. After each release, it’s essential to verify that the configuration files in the new version match the expected baseline configuration to ensure no critical settings were altered or removed.

Files to Compare: After a new release, you have two configuration files to analyze:

Expected Configuration File: expected_config.json

Actual Configuration File: actual_config.json

Expected Result: The actual configuration file should match the expected configuration file exactly, confirming that no unauthorized changes were made during the release process.

Output: The resulting count of difference between the two files being compared is stored in the {result} output variable as, which can be utilized for display or other purposes.