[
https://issues.apache.org/jira/browse/SUREFIRE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated SUREFIRE-1526:
------------------------------------------
Labels: features refactoring (was: features)
> Allow the Maven Surefire Plugin to be used to test non-java projects
> --------------------------------------------------------------------
>
> Key: SUREFIRE-1526
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1526
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.22.0
> Reporter: Devin Owens
> Priority: Major
> Labels: features, refactoring
>
> My Company uses a custom language that we've written a unit test framework
> for in Java. We would like to be able to run those tests as part of our maven
> build process and the Maven Surefire Plugin with out unit test framework as a
> test provider seems to be the best option, but the Maven Surefire Plugin
> looks for a java test file in src/test/java or a testng xml file before
> invoking the provider in AbstractSurefireMojo.execute(). Since the tests that
> our provider runs are not java tests this means that our tests can't be run.
> If there is not already a supported way of doing this I would recommend
> making checking for the existence of tests the responsibility of the test
> provider.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
