How to use Pre-Release
How to use Pre-Release
Introduction
It is advisable to have a separate environment to test the pre-release build.
Perquisites
Take a backup of Assets: Refer How to Backup and Restore Leapwork database article to take backup.
Make sure you remember your Leapwork admin password or create a new admin: Refer How to retrieve a forgotten admin user password article for more information.
Backup your database keys: Described in this article Database key backup.
Create a Test Environment
- You must have two separate machines: one for Studio and another for Controller and Agent.
- Make sure the above two machines are on the same network and firewall as your production environment.
Install and Restore Data
- Click on the link (Provide link) and download the pre-release build on Studio and Controller machine.
- Open Studio test machine and install Leapwork Studio.
- Install Controller and Agent on Controller Test machine.
- On the controller, start the test case restoring process by following this article.
- Stop the Leapwork Controller windows service.
- Replace all the Assets library.
- Start the Leapwork Controller windows service.
- Open Leapwork Studio and enter the Encryption key for DB. We are ready for testing.
What to Test
- Connectivity: There should be no connectivity issue between Studio, Controller, and Agent.
- Saving: Test should be able to save, and version history should be created.
- Export/Import: User should be able to import and export.
- Schedules: Schedule should work as configured.
- Test Execution: Test execution should be as per test definition (run Virtual web and desktop tests to verify).
- Test Data and elements: Test data is intact, and there is no change in Images, Web, and desktop elements.
- Subflows: Subflow should be intact, and there is no change in their versions.
Upgrade Production Environment
If all the above test results have the expected outcome, upgrade the build.
If you have any questions, contact our Priority Support.