Re: NB 11.3 + Gradle 6x + integrationTest and Test File (ctlr-f6)

[Laszlo Kishalmi <la...@gmail.com>]

I'd recommend to add an improvement request into JIRA. I do not think 
that it can be solved in 11.3, some cumbersome workaround could be 
overriding the test action.

Unfortunately 12.0 is almost ready so most probably this can be released 
in August or some daily builds.


On 4/30/20 11:54 AM, Fred Welland wrote:
> The older G4NB plugin had smarts or something such that it looked at 
> pathing of where a test file was and adjusted the gradle invocation 
> accordingly.
>
> So for example, a Spock spec in: 
>  src/test/groovy/com/blah/blah/SomeSpec.groovy
>
> would invoke gradle a bit like like:
>
> ./gradlew   tests --tests com.blah.blah.SomeSpec
>
> And if the Spock spec was here: 
> src/integrationTest/groovy/com/blah/blah/OtherSpec.groovy
>
> would invoke gradle a bit like like:
>
> ./gradlew   integrationTest  --tests com.blah.blah.OtherSpec
>
> Basically, it seemed to do some simple matching of the path against 
> tasks in the build file and away it went.
>
> Can the 11.3, using builtin gradle support support this kind of 
> behavior?   If so how?
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
For additional commands, e-mail: users-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: NB 11.3 + Gradle 6x + integrationTest and Test File (ctlr-f6)

[Fred Welland <fr...@gmail.com>]

Thanks!

Just here:  https://issues.apache.org/jira/projects/NETBEANS/issues  ?   I
have to make an account?   (didn't see add issue button)

FWIW:   Got a reasonable solution that ties me over for now:  made a Task
and just hard coded a specific spec name to that.   It mostly works; and
available right click menu; so speeds up repetitive work on a specific
spec.   Note: the ${selectedClass} macro wouldn't expand for me.  Having
that work, would have been like 3/4ths what I need.  The other 1/4, and
this has probably been missing forever:  comprehensive macro & ide
automation feature triggerable by hot-keys.




On Thu, Apr 30, 2020 at 8:04 PM Laszlo Kishalmi <la...@gmail.com>
wrote:

> I'd recommend to add an improvement request into JIRA. I do not think
> that it can be solved in 11.3, some cumbersome workaround could be
> overriding the test action.
>
> Unfortunately 12.0 is almost ready so most probably this can be released
> in August or some daily builds.
>
>
> On 4/30/20 11:54 AM, Fred Welland wrote:
> > The older G4NB plugin had smarts or something such that it looked at
> > pathing of where a test file was and adjusted the gradle invocation
> > accordingly.
> >
> > So for example, a Spock spec in:
> >  src/test/groovy/com/blah/blah/SomeSpec.groovy
> >
> > would invoke gradle a bit like like:
> >
> > ./gradlew   tests --tests com.blah.blah.SomeSpec
> >
> > And if the Spock spec was here:
> > src/integrationTest/groovy/com/blah/blah/OtherSpec.groovy
> >
> > would invoke gradle a bit like like:
> >
> > ./gradlew   integrationTest  --tests com.blah.blah.OtherSpec
> >
> > Basically, it seemed to do some simple matching of the path against
> > tasks in the build file and away it went.
> >
> > Can the 11.3, using builtin gradle support support this kind of
> > behavior?   If so how?
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: users-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>