BeforeAll and AfterAll in Automation Spec?

Development Programming & Scripting C++
, , , ,
1

I have an automation spec which tests a component.
To test the component, I create a new world, spawn an actor, add the component to the actor in BeforeEach method.

All that happens for every test which slows tests down.

I wanted to know if there are functions that run before all tests and after all tests.

That way, I can create the world, use that world for all tests, and then destroy the world when all tests are done.

2

Try this, it shows how to group unit tests into a container so you can do setup/takedown tasks in each container rather than for every test:

1 Like
3

I’m already using it (I’m even mentioning it in the title).
It doesn’t have a function that runs before and after all tests.

4

Pretty sure my comment here was incorrect. Removed to avoid confusing others.

5

I’m also looking for a way to do this. My thought was to force BeforeEach and AfterEach to act like BeforeAll and AfterAll by only sometimes running their code blocks.

For BeforeAll, you can check whether it’s already been run by keeping a list of corresponding FString names, for example, so you only run it the first time it is encountered.

AfterAll is harder, because I don’t know how many tests to wait for until it should be called. I thought about having an It(“should clean up”) test as the very last test in that Describe() scope that calls the AfterAll code, but I don’t think the spec format guarantees the order of test execution.

6

So I’m fairly new to automation so I might be incorrect, but I believe a Before All could be done with a BeforeEach in a nested describe eg:

image
image1005Ă—568 66.3 KB

This seems to work as a before all for my tests, BeforeEach is run once for my first It function then not run again for the second It function. For a AfterAll, I read that latent Its will run after the AfterEach so, assuming you don’t have any latent tests, I’d have though you could use a Latent It (or possibly LatentAfterEach) to run after everything else. You could probably also nest a AfterEach with the last It function to run at the end again not 100%.
Don’t quote me I’m a noob :slight_smile: I had hoped putting the Before and After Each outside of the describe would work but doesn’t seem too :frowning:

7

this approach may work, but if you try to run “Should have loalded after the FPSMap” as a standalone test from the frontend, it won’t run your BeforeEach too! I’d avoid this approach.