You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no SAX Parser for results in TestNG.
This is important as currently large test suites (>1k tests) will either fail or have difficulty generating test results thanks to all test parsing being done in memory.
It is not too difficult to write one, and the default Reporter classes do not provide the necessary api to be easily inheritable.
Additionally, the whole reporter system is wasteful, this system should be re-architect-ed to allow runnning reporters as part of a report loop with shared resources.
The text was updated successfully, but these errors were encountered:
Am working on a Fix, current strategy is to use JAXB and add a separate Reporter class that uses org.testng.xml.jaxb generated classes. I have generated an xsd from the provided dtd, and generated the necessary classes, working on creating a modified reporter and testing the new reporter class.
ping @cbeust@juherr - I am not sure as to what needs to be done here. Would either of you please let me know a bit more in-detail on what is being expected ?
As I understand it, it is a feature request for the reporter api where we should not store all the result in memory but call listeners on the fly.
It is something I've already tried without success.
I think we should find a way because reporters are often the root cause of perf issues with huge suite.
There is currently no SAX Parser for results in TestNG.
This is important as currently large test suites (>1k tests) will either fail or have difficulty generating test results thanks to all test parsing being done in memory.
It is not too difficult to write one, and the default Reporter classes do not provide the necessary api to be easily inheritable.
Additionally, the whole reporter system is wasteful, this system should be re-architect-ed to allow runnning reporters as part of a report loop with shared resources.
The text was updated successfully, but these errors were encountered: