Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ServletTestExecutionListener is not enabled by default in abstract base test classes [SPR-11340] #15964

Closed
2 tasks done
spring-projects-issues opened this issue Jan 21, 2014 · 1 comment

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Jan 21, 2014

Sam Brannen opened SPR-11340 and commented

Status Quo

The ServletTestExecutionListener was introduced in Spring Framework 3.2 and is enabled by default when using the TestContext framework without specifying custom listeners via @TestExecutionListeners. However, the ServletTestExecutionListener has not been added to the default set of listeners for Spring's abstract base test classes.

Deliverables

  1. Prepend ServletTestExecutionListener to the set of default listeners in AbstractJUnit4SpringContextTests.
  2. Prepend ServletTestExecutionListener to the set of default listeners in AbstractTestNGSpringContextTests.

Affects: 3.2 GA

Issue Links:

  • #15971 Handle NoClassDefFoundError for TestExecutionListeners consistently in the TestContext framework

Backported to: 3.2.7

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jan 21, 2014

Sam Brannen commented

Resolved as described in the comments for GitHub commit 3370f8b (4.0.1) and GitHub commit 603d79a (3.2.7):

Include ServletTEL in abstract base test classes

The ServletTestExecutionListener is now prepended to the set of default
listeners in AbstractJUnit4SpringContextTests and
AbstractTestNGSpringContextTests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants