-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code coverage via trace files in txt format #144
Comments
There are no plans, yet. First I need to analyse the new format and see how we can find out what ESQL code has been executed. |
@ThomasPohl, I was looking into the new trace format and was able to parse it with below changes. In file TraceFileReader, changed PATTERN_REGEX to ".* at \((.), (\w+)\.\w+\).". Next change was in readLine function for identifying begin and end statement. int statementBegin = line.indexOf("'", line.indexOf("'", (line.indexOf("'") + 1) +1) + 1); These 3 changes allowed the new format to be parsed. Attaching the trace file generated by App Connect Enterprise v12. Is there a way to incorporate these changes keeping the plugin backward compatible. |
@abhi-malhotra Thanks for your suggestions. I made the regex a little more general. Now it should work for both plain text formats. |
@abhi-malhotra Parsing oof the new coverage-format is part of the current release candidate. It would be great if you could check, if it works for you. |
With App Connect Enterprise 11 onwards, user trace is generated as plain text format instead of xml. Plugin currently ingests trace in xml format for code coverage.
From App Connect Enterprise infocenter:
When trace is active, information is recorded in the user trace log files in plain text format.
https://www.ibm.com/docs/en/app-connect/11.0.0?topic=trace-user
Are there any plans to ingest traces in the new format?
The text was updated successfully, but these errors were encountered: