You can only use --test filter when requesting execution of a single Test task. If you are requesting execution of multiple Test tasks via a lifecycle task (which the task called test in that project boils down to) then the filter is ignored. This is just how it works because gradle cannot figure out which task you want to apply the filter to if you requested execution of a task that depends on other tasks.
On Sat, Aug 8, 2020 at 3:06 PM M T <[email protected]> wrote: > Hey again good people. Noticed something weird. Hopefully I'm over > complicating matters. > So i forked the geb gradle example. > I've been developing my tests with the standard chrome/Firefoxtest task > with --test filter. No issue. > However, when using the test task, that depends on each driver task, the > filter is ignored. > Packages, class names, applying the filter in a doFirst closure--nothing > seems to work and filter correctly. Curiously, if the test task is called > via intelij config it works perfectly. > I fear that something that I haven't fully understand is happening here > and that's what Id like to figure. > Thanks in advance > > -- > You received this message because you are subscribed to the Google Groups > "Geb User Mailing List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/geb-user/319c9504-a448-48fe-9aa7-fe41e67e712fo%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "Geb User Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/CA%2B52dQQ%3DnoSL8PnLf-7YFTNH%2BdbSYMHqHhWpNuC7payfniu50g%40mail.gmail.com.
