`AbstractTestNGSpringContextTests` only provides `@BeforeClass` support, need `@BeforeSuite`

[snelson-gocognition]

Issue was opened on TestNG side, but this is a Spring specific issue (2019).
testng-team/testng#2191

spring-test/src/main/java/org/springframework/test/context/testng/AbstractTestNGSpringContextTests.java

Only provides @BeforeClass TestNG support.

I believe this would be better suited as a @BeforeSuite, so that Spring Context can load and initialize for setup that should happen before the entire test suite is running, rather than only once a test class is actually initialized.

I believe setting up the context in @BeforeSuite would provide all of the benefits that are gained from the @BeforeClass

[sbrannen]

Hi @snelson-gocognition,

Congratulations on opening your first GitHub issue ever! 👍

We are aware of the limitations of AbstractTestNGSpringContextTests with regard to @BeforeSuite vs. @BeforeClass lifecycle callbacks.

The crux of the issue is that AbstractTestNGSpringContextTests can only support one or the other. Thus, if you need @BeforeSuite behavior, you will need to create your own version of AbstractTestNGSpringContextTests or try out some of the tips given in the comments in #8750.

Furthermore, the TestNG Support Classes section of the reference manual provides the following tip.

These classes are a convenience for extension. If you do not want your test classes to be tied to a Spring-specific class hierarchy, you can configure your own custom test classes by using @ContextConfiguration, @TestExecutionListeners, and so on and by manually instrumenting your test class with a TestContextManager. See the source code of AbstractTestNGSpringContextTests for an example of how to instrument your test class.

In light of that, I am closing this as a:

• Duplicate of Should AbstractTestNGSpringContextTests use @BeforeSuite instead of @BeforeClass? [SPR-4072] #8750

Regards,

Sam