I'm working on integration tests using the Database with TestBox and have a working test (even wrapped in a transaction so changes are rolled back automatically), but I keep seeing references to calling

super.beforeAll()

or

super.afterAll()

in test bundles referenced in documentation and examples I'm reading that inherit from a Base Test Class (that inherits from the Testbox Base Spec). Can someone explain to me what this means: "This also helps parent classes enforce their setup methods are called by annotating the methods with

@beforeAll

. No more forgetting to call

super.beforeAll()

!" - from this page: https://testbox.ortusbooks.com/in-depth/life-cycle-methods/annotations I am not doing this (not calling super.beforeAll etc, anywhere), but my tests are working fine. Am I missing something or should I be calling that somewhere? When and where do you need to call the

super.[LifeCycleMethods]()

? My class inheritance: testbox.system.BaseSpec -> myBaseTestClass (initializes application variables/test setup and does not call super.beforeEach etc.)

Not parallel by default.

Ok, thank you. I kept seeing it everywhere and started to wonder if I needed it, but everything is working.

To be clear, you CAN run your tests in parallel, but you must be careful. Any tests that aren't thread safe or expect to run in a specific order may fail

Thanks for the call out. For now, I'd prefer tests run synchronously, so I'm glad that's the default. I'll take deterministic and easy to understand over faster in my case.

When you have an actual method called

beforeAll()

you • only can have one of them (duh) • you must call the

super.beforeAll()

or stuff won't work however, when you do this

@beforeAll
funnction someRandomMethodWhoCaresWhatItIsCalled() {
}

@beforeAll
funnction anotherOne() {
}

@beforeAll
funnction anotherOneBitesTheDust() {
}

you can • have as many before all methods as you like • none of them need to make any super calls since they don't actually override the base method

You may get another dollar from me 😄 Hmmm...good to know and ty for the example. So just to make sure I'm not shooting myself in the foot, if I have a BaseTest class that inherits from the TestBox BaseSpec and just sets up variables, but no

beforeAll

call, I have no need to call super.beforeAll() (pretty sure this is right), correct? However if I did have a beforeAll in my BaseTest class, does that mean I need to call super.beforeAll in it or in a constructor init in order to bring maybe a TestBox's BaseSpec

beforeAll

I'm inheriting from into the mix?

That is correct