Running Gauntlet tests in "Test" configuration

I’m a bit new to all of this but has anyone run Gauntlet Tests in -config=Test before? Pretty much any example of Gauntlet I can find uses -config=Development.

I ask this because when I use config=Test, the test gets stuck (though when I use Development), it works. The test I am using currently is the UE.BootTest test.

When running in Development the game launches and then shuts down shortly after. However, when using Test as the config, it never exits out of the game (only until there is a timeout). It simply launches the game and it stays on the first thing that a player would see if they were to launch the game in a shipping mode.

I’ve also tried changing the buildcookrun -config option to tbe Test as well but the same result persists.

It seems like Gauntlet is not being initialized when in Test configuration? This line is from Development and is missing from the Test logs.
image

Just wondering if anyone has gotten Gauntlet to run under the Test configuration before.

Seems that Test configuration skips logging and the Gauntlet BootTest looks for that line in the logs. Since it was missing, the BooTTest got stuck.

Hi @SteamedBun ,
we are currently working on a new framework for automated testing and will release this plugin on Github in a few weeks.
It will also use Gauntlet and we plan to support test builds.
Would you be interested in testing the plugin?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.