Closed MedadRufus closed 2 years ago
I will be happy to work on the code and solution implementation
Wow, thanks for the detailed issue. Yeah I figured the day may come where some stdout will confuse my regex parser 😉 I am having some days off so every help is welcome. If you find a way to not clutter the output directory with the xmls it would be a perfect solution. But if not it still is the best approach. You could base of your work from the latest branch feat/addingLogger
Thanks, I will experiment with a solution this week.
Just discussing the solution. What if we treat the junit xml output as a temp file, and delete it after the test adaptor has all the info. Will that be a good practice? That will ensure no file clutter.
I have yet to see what the output looks like though.
Yeah was thinking about that too. I was afraid that people are using these files and we would delete them. But yeah would be the way to go
First of all, many thanks for developing this convenient tool to work with vs code. I am currently using the latest version of CppUTest v4.0 and CppUTest-Test-Adapter 0.1.12.
The problem arises when some debug text is printed out while running the test. For example, the CppUTest adapter incorrectly parses the following output and marks as failing:
Conversely, the following output is correctly parsed, with no extra text inbetween:
I suggest 3 solutions: