This issue seems to be similar to SUREFIRE-1452. The fix was only applied for TestNG.
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows *From: *Tamás Cservenák <[email protected]> *Sent: *Wednesday, February 22, 2023 12:19 PM *To: *Maven Users List <[email protected]> *Subject: *Re: unexpected behavior between inheritance and -dtest with surefire Howdy, unrelated to your question, and unsure if this is intentional from your side, but Maven user properties (like the "test" is) on CLI should be set using "-Dtest=foo" (uppercase letter D) and not "-dtest=foo" as you wrote. HTH T On Wed, Feb 22, 2023 at 5:43 PM DJ Kim <[email protected]> wrote: > Hi there, > > Yesterday I posted a question about -dtest. > > > > To give a bit more of a context. I have a child class that extends parent, > and I would only like to run -dtest=childclass#MethodinheritedfromParent. > Unfortunately, the surefire executed all the test cases inherited from > parent (unexpected behavior) and omits test from child class (expected). > > This feels like a bug. Any help is greatly appreciated. > > Thank you, > > Kim > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows >
