You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2016/09/19 22:26:20 UTC

[jira] [Assigned] (SUREFIRE-1235) generic/consolidated rapid test execution support needed

     [ https://issues.apache.org/jira/browse/SUREFIRE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana reassigned SUREFIRE-1235:
--------------------------------------

    Assignee: Tibor Digana

> generic/consolidated rapid test execution support needed
> --------------------------------------------------------
>
>                 Key: SUREFIRE-1235
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1235
>             Project: Maven Surefire
>          Issue Type: Wish
>    Affects Versions: 2.19.1
>            Reporter: Mark
>            Assignee: Tibor Digana
>
> Many IDEs have seemingly implemented their own rapid test unit execution infrastracture. Netbeans is still lacking, and I think for good reason.
> https://netbeans.org/bugzilla/show_bug.cgi?id=238543
> Instead of every IDE running its own rapid test execution infrastructure, I'd prefer maven, in particular the surefire plugin, to provide some solution to the problem.
> My proposal: do you know "mvn jetty:run"? It starts a jetty server and can be configured to scan the class path for changes. And it reloads when it detects them. Wouldnt that be a nice solution for surefire to provide rapid test execution? ie. provide some long running (non-terminating) mode where a) IDEs can trigger single test executions and b) it scans/listens to class path changes in order to re-run tests (optional).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)