Horde Test Automation Tutorial

Introduction

The Horde Automation Hub surfaces individual and suite Gauntlet test results. Horde efficiently generates searchable metadata for streams, platforms, configurations, rendering apis, etc. The automation hub is used at Epic by QA, release managers, and code owners to quickly view and investigate the latest test results across platforms and streams. It provides historical data and views which drill into specific test events which can include screenshots, logging, and callstacks.

Prerequisites

• The Horde Server installed (see the Horde Installation Tutorial).
• A Horde Agent with AutoSDK configured (see Engine\Extras\AutoSDK\README.md in the Engine sources)
• The Horde Build example project configured (see the Horde Build Automation Tutorial).
• An Android phone or tablet added to the Device Manager (see the Horde Device Manager Tutorial).

Steps

1. The Horde example UE5 project includes a reference template for building, packaging, and testing the Lyra example game project. The build graph for this example is intended to be general purpose and extensible and is a good source of a real world graph used at Epic for automated testing.

   

   From the UE5 project stream view, select the Packaged Build category, and click New Build, and then select Packaged Lyra Build. Add the Android target platform and click Start Job

   

   Please note that the Device Manager URL field is for example purposes and you would generally set this in the related Gauntlet build graph configuration.

2. The job will build, cook, and run a Lyra Boot Test on the Android device, reserving it from the device manager during the process.

   

3. Once completed the test results will be availble in the Automation Hub which features finely grained filters and views that can cross compare platforms and streams.