You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2018/08/26 04:35:00 UTC

[jira] [Comment Edited] (YETUS-21) patch to a unit test should only trigger that unit test

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

Allen Wittenauer edited comment on YETUS-21 at 8/26/18 4:34 AM:
----------------------------------------------------------------

-00:
* a first stab at an implementation for maven

This is kind of a dumb implementation that I'm sure someone else could do better... but the gist of it is:

1. if the user passed us a list, then test-patch does that functionality
2. if not, check if we are in patch mode (or at least not qbt)
3. if so, then see if the user patched a file in src/test/java that really is a java file with a (public) class in it.
4. If so, then add that file to an array as well as add the class to the test list
5. after all is said and done, if the # of changed files == the # of test files was found above, then assume that test-patch only needs to run those classes.




was (Author: aw):
-00:
* a first stab at an implementation for maven

> patch to a unit test should only trigger that unit test
> -------------------------------------------------------
>
>                 Key: YETUS-21
>                 URL: https://issues.apache.org/jira/browse/YETUS-21
>             Project: Yetus
>          Issue Type: Improvement
>          Components: Test Patch
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>            Priority: Major
>             Fix For: 0.9.0
>
>         Attachments: YETUS-21.00.patch
>
>
> A great optimization would be to determine if only a unit test was patched and run just that unit test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)