[SUREFIRE-522] Classes located in src/test/java are treated as JUnit tests if they contain the name Test

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.4.3
• Environment: Ubuntu
• Assignee: Carlos Sanchez Gonzalez
• Reporter: Kristoffer Moum
• Created: 01/Oct/08 09:05
• Updated: 11/Jun/10 05:50
• Resolved: 11/Jun/10 05:50

Description

Having recently upgradet to 2.4.3 I realise that all classes whose name conforms to the above described pattern are being treated as JUnit test classes, meaning that if the class isnt scoped public, it does not provide a default construct and it does not contain a test method, it will be reported as containing failed tests, i.e.:

Tests in error:
initializationError0(com.mycompany...TestMethodConfiguration)
initializationError1(com.mycompany...TestMethodConfiguration)
Tests run: 246, Failures: 0, Errors: 2, Skipped: 0

The methods initializationError0 and 1 do not exist in the class obviously.

Surefire didn't use to treat classes based on naming conventions unless the class name ended with "Test".

Issue Links

• duplicates: SUREFIRE-482 Surefire tries to run JUnit4 tests that contain no @Test annotations