Julien Herr
Julien Herr
@krmahadevan I think the feature request is still valid but not its first implementation. BTW JUnit5 added the 1 instance by class feature, we can add the 1 instance by...
This feature is awesome and open a lot of new options. Well done 👍
It is not something nicely fixable from Steve: the specification doesn't say the way the data should be encoded and it will depend on the station itself. Some will accept...
@IsaakKrut I am uncertain if you will be able to test the modification. The desired outcome is for a warning message to be displayed if the test methods contain a...
`@Ignore` is supposed to disable `@Test` thanks to an internal listener. The only expected behavior is that `@Ignore` on a class will disable enabled `@Test` on methods but `@Test(enabled=false)` won't....
All the `@Ignore` logic is based on a listener. So, it sounds like an issue when listeners are involved. We should investigate and fix it on TestNG side.
>That was what my sample was trying to show. @krmahadevan Right! I didn't realize your sample already highlights similar behavior between `@Ignore` and `@Test(enabled=false)`. > only available from `onBeforeClass` in...
@krmahadevan @marcphilipp If it is possible, WDYT if we add an internal listener which notifies every discovered `ITestNGMethod`?
I can't be present but @krmahadevan knows everything :)
The problem is on `NioEventLoopGroup group = new NioEventLoopGroup();` and in my real-life usage, I'm not the one who calls it. Are you able to create a `NioEventLoopGroup`?