@RunWith-based junit 4 tests are not executed anymore

Issue created

Thomas Mortagne created this issue on 14/Nov/24 16:29

Summary:	@RunWith based junit 4 test are not executed anymore
Issue Type:	Bug
Affects Versions:	15.2-rc-1
Assignee:	Unassigned
Components:	Development Issues only - Test
Created:	14/Nov/24 16:29
Priority:	Blocker
Reporter:	Thomas Mortagne
Description:	They seem to be executed in practice, but their result is completely ignored by Surefire... The regression has been introduced by ~~XCOMMONS-2653~~ (15.2RC1).

Changes by Thomas Mortagne on 14/Nov/24 16:29

Summary:	@RunWith based junit 4 test tests are not executed anymore
Fix Version:	16.10.0-rc-1
Fix Version:	15.10.14
Fix Version:	16.4.6
Description:	They seem to be executed in practice, but their result is completely ignored by Surefire... This impacts many rendering and filter tests. The regression has been introduced by XCOMMONS-2653 (15.2RC1).

Changes by Vincent Massol on 14/Nov/24 16:36

Summary:

@RunWith - based junit 4 tests are not executed anymore

	Thomas Mortagne on 14/Nov/24 16:29

	It seems to work as expected when adding `org.apache.maven.surefire:surefire-junit47` (which force using a provided designed for Junit 4 tests) but for some strange reason, it seems to break any test which relying on something located in xwiki-commons-tool-test-simple with error that suggests it's not put in the classloader at all.

This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)

If image attachments aren't displayed, see this article.