How to run some code before running tests, then again when they all finish?

Unity Engine
,
1

I run my automated tests in the editor. There’s some state I’d like to change for the duration of my test run, but I’d also like to revert this state when these tests finish.

No matter how many tests I run, or in which assemblies, or how the test runner is started, I want to:

  • Run some code exactly once before any tests are run or initialized
  • Run some different code exactly one when all tests and other cleanup are finished, canceled, or otherwise interrupted

How can I do this with the Unity Test Framework?

2

Try IPrebuildSetup and IPostbuildCleanup.

3

I have tried this. The PrebuildSetup seems to work just fine, even the PostBuildCleanup is running, but. What I want to achieve is to set the Active Scene to an Empty scene before running the EditorTests.Then set it back after all tests have already run.

If I try to OpenScene or LoadScene or even Close/RemoveScene they do not seem to work.

Do you have an easy way to set this? Because always setting the scene to an empty one by hand is a bit tedious.

Thanks.

4

That’s what I thought, but it doesn’t seem to be working the way I’d hope. I want my Prebuild/Postbuild handlers to run on a per-assembly level. However, given the following code…

using CorundumGames.Tests;
using UnityEngine;
using UnityEngine.TestTools;

[assembly: PrebuildSetup(typeof(ProfileHandler))]
[assembly: PostBuildCleanup(typeof(ProfileHandler))]

namespace CorundumGames.Tests
{
    public sealed class ProfileHandler : IPrebuildSetup, IPostBuildCleanup
    {
        public void Setup()
        {
            Debug.Log($"Setup({GetHashCode()})");
        }

        public void Cleanup()
        {
            Debug.Log($"Cleanup({GetHashCode()})");
        }
    }
}

…the two Debug.Log statements are never called when applied at an assembly level. This class is defined in an assembly called Common.dll, which contains no tests but has code shared by Runtime.dll (Play Mode tests) and Editor.dll (Edit Mode tests).

If I apply this handler to Editor.dll and Runtime.dll, nothing happens. However, if I apply it directly to the test fixture classes then it prints out those statements as expected. Am I doing something wrong, or is this a bug?

5

Wait, so do you want the code to run “exactly once,” or do you want it to run once per-assembly?

Maybe you want SetUpFixture?

6

Technically I want it to run exactly once (rehardles, but once per assembly would be good enough since my tests are only in two assemblies. As long as I can be sure that the SetUp/TearDowns aren’t stacked (i.e. I want SetUp → TearDown → SetUp → TearDown, not SetUp → SetUp → TearDown → TearDown).

It sounds like you could use more info about what I’m trying to do.

I’m using a framework called Trimmer to manage build configurations for my project. These build configurations let me build slightly different versions of the same project, and they can vary in pretty much any way I want them to (including/excluding specific assets, #define symbols, player settings, etc.). These configurations are represented as assets called BuildProfiles. They can even be used to affect the editor; exactly one is enabled in the editor at a time.

I want to do the following:

  • Prepare a special BuildProfile used for running in-editor tests (e.g. using certain game configurations), rather than for producing a standalone build.

  • When I run a test, I want the test profile to become active before the tests start.

  • When the test run finishes for any reason (successfully, with errors, canceled, etc.), I want the build profile that was previously active to be made so again.

I could do this once per test fixture, but then the SetUp/TearDown pair would run for each fixture, right? Changing the build profile is an expensive operation. Also, I might simply forget to keep the attributes up to date. I have around 30 fixtures, but I’m about to do a major rewrite of my test suite.

7

I see. I do think a SetUpFixture outside of any namespace is probably your best bet, then - I think it’s your best option for running code that is before/after multiple other fixtures. You’d have to have one in each of your assemblies, but they could both call into shared code.

8

I can do that? Huh. I’ll be damned. I’ll give this a try and report back. Thank you!

1 Like