Introduce support for disabling JUnit Jupiter tests with SpEL expressions [SPR-14614]

[spring-projects-issues]

Tadaya Tsuyukubo opened SPR-14614 and commented

Status Quo

The JUnit Jupiter API in JUnit 5 currently provides @Disabled to disable tests; however, disabling of tests via this annotation is determined at compile time. Thus it's not flexible.

Another option is to use Assumptions within test methods, but it may not so intuitive since the logic resides in the method. Furthermore, the use of assumptions is not very reusable.

Proposal

For JUnit Jupiter and the Spring TestContext Framework, using SpEL expressions would provide a dynamic means for disabling tests.

Suggested API:

@DisabledIf("SpEL expression here")

Related Resources

• JUnit5 issue

---

Issue Links:

• Support @EnabledIf and @DisabledIf without loading ApplicationContext [SPR-14649] #19215 Support @EnabledIf and @DisabledIf without loading ApplicationContext ("is depended on by")
• Introduce support for enabling JUnit Jupiter tests with SpEL expressions [SPR-14644] #19210 Introduce support for enabling JUnit Jupiter tests with SpEL expressions

[spring-projects-issues]

Tadaya Tsuyukubo commented

pull request: #1144

codacy claming method scope in test..

[spring-projects-issues]

Sam Brannen commented

Tadaya Tsuyukubo, thanks for the PR!

But... I have no idea what you mean by "codacy claming method scope in test..". Care to expound? ;)

[spring-projects-issues]

Sam Brannen commented

Never mind: I found the codacy report you were referring to.

[spring-projects-issues]

Sam Brannen commented

Support for @DisabledIf("<expression>") has been pushed to master in GitHub commit 655097a.

An <expression> can be a property placeholder or a SpEL expression. See the Javadoc for @DisabledIf for details.