Skip to main content
Skip table of contents

Tie out Testing procedure using Compare tool

Pre-requisite for Regression Tie outs

Environments: QA needs at least 2 environments with one on existing code and other on new code.
URLs: One with existing code as old URL, one with new code with v10 added.
If Hosted: Devops can give us the Prod Config and Latest Prod DB.
If on premise: Get the Prod Config and Latest Prod DB info from the Client for the Origin Backup/DB
Queries to run: Run the attached queries to get the list of processes and assets being run heavily.
Assets: Get the name of the complex Assets (at least 2) and process to perform Tie outs on.
Files: Corresponding Load files for the above assets (volumes and analysis)
Browser: Get the bowser from the client.
Reports: Get the list of core reports to be tested.
Interfaces: Either get that from Client or you can get them from Pivotal or JIRA.(Search for client stories with design specs we designed for them)
UAT test scripts: Client test plan to make sure we cover those in QA.
Notes:
Get the training for How to DB backup and restore DB
How to take backup of DB
https://wenergysoftware.atlassian.net/wiki/x/CIB4F  

Example Template for the DevOps ticket.
Origin Backup: wepltprod on FTP
Do you need a code deploy? YES
What version of the code do you need? Develop-MT for http://enlink-project2.we.local/users/sign_in
7.0.11.enlink for http://enlink-clone2.we.local/users/sign_in

Approver: Harish
Client live? Yes
Origin DB: FTP Backup
Destination environment: Project boxes
Config: (attach the yml file received from client for on premise clients for new environment request only)

Once the environments are set up follow the below steps.

Ø  Export the results from the above query and analyze the data.

Ø  Make sure all the processes are run and all type of imports are considered in tie out testing.

Ø  Get them verified by the client for confirmation.

Ø  Get the imports for the confirmed assets.

Ø  Upload the multiple imports from the Asset process control page for a selected Accounting and Prod date. Take the latest available dates.

Ø  Update the imports with dates and check for format errors before uploading.

Ø  Maintain a tracker sheet with Asset names, Process, Screens to check and update the same.

Ø  Run the process as per tracker for each asset after uploading and verifying the loaded data is clean.

Ø  Download the grids with appropriate filters in CSV format from both boxes in a folder in your local.

Ø  Login to WinSCP and export the files to server. (video is available on how to use the WinSCP and comparison Tool).

Ø  Run the respective command to compare.

Ø  Below is the example for in and out of tolerance after comparison

image-20250121-061108.png

Ø  When there are no rows out or tolerance and all rows are in tolerance then it’s a PASS.

Ø  If there are any rows for out of tolerance there is deviation.

Ø  Check for those records in the UI in both boxes by filtering for them.

Ø  When there are records found in older version only, but all are zeroes, then it’s a PASS as in new version the 0 values records are suppressed. This could be reason for mismatch in row count in the UI.

Ø  When there are records found only newer version or older version, but all are non zeros, then it is a FAIL and needs investigation.

Please refer the below KT recordings to use comparison tool and understand data flow at high level for Preliminary Investigation.

Tie out testing

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.