Julien Herr
Julien Herr
@Jenf01 Your approach is good, and trying to fix is appreciated. Sadly, the fix you proposed will break servers in production and cannot be merged. As said by @fnkbsi something...
This is supposed to work and it is covered by a test: https://github.com/testng-team/testng/blob/master/testng-core/src/test/java/test/name/ITestSample.java Could you try with a `ThreadLocal` like the sample?
That sounds more like a reporter issue. We need to check.
Duplicate issue of #100
@razvanphp They are indeed: Which OCTT test case are you referring to exactly? https://openchargealliance.org/wp-content/uploads/2025/09/CompliancyTestTool-TestCaseDocument.pdf
@razvanphp It makes sense that the 1.6 core test cases validate the initial command only. The challenge comes when you aim to validate both specifications, but so far I haven’t...
Good catch. I hadn’t reviewed the file in enough details. BTW, I don’t see any test case in the list that appears to cover the `L01.FR.20` rule.
There is no expected exception in listener interfaces: you are supposed to manage exceptions in the listener implementation. But TestNG can do better and the expected behavior from listeners should...
Yes. The documentation should be updated. But I don't see good reason that explains the failure here.
Sure but I remember we catched exceptions from listener with a warning. Why not here?