[ 
https://issues.apache.org/jira/browse/SUREFIRE-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010969#comment-17010969
 ] 

Tibor Digana commented on SUREFIRE-1743:
----------------------------------------

[~andyRokit]
Yes, you'r right that it is a needed feature and the development facilities are 
mentioned in the 
[comment|https://issues.apache.org/jira/browse/SUREFIRE-1698?focusedCommentId=16953638&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16953638]
 but there was not user's will to develop it in Surefire. Pls open a 
pullrequest in the GH and be motivated by the solution in the old provider 
{{JUnit4Provider}} and cover the feature by the unit and integration tests. The 
[feature 
matrix|https://maven.apache.org/surefire/maven-surefire-plugin/featurematrix.html]
 needs to be updated in the same project on GH.

> Allow custom listeners to request stop
> --------------------------------------
>
>                 Key: SUREFIRE-1743
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1743
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: Maven Surefire Plugin
>            Reporter: Andrew Neeson
>            Priority: Trivial
>
> Currently Surefire gives you the ability to [add custom listeners and 
> reporters|https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#Using_Custom_Listeners_and_Reporters].
>   However, those listeners do not have a hook on the Notifier which created 
> them.
> I would like to be able to create listeners which have the ability to request 
> that the test run is stopped (RunNotifier.pleaseStop) under specific 
> conditions.  These conditions are not currently covered by existing 
> mechanisms such as 
> [skipAfterFailure|https://maven.apache.org/surefire/maven-surefire-plugin/examples/skip-after-failure.html].
> Note:  I originally considered this as [a change to Cucumber 
> JVM|https://github.com/cucumber/cucumber-jvm/issues/1854], but I realise that 
> it's more generic than that (hence this ticket).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to