Our tests use string diffing library that uses ASCII text formatting to highlight text differences. Both visual studio and Rider display this correctly in their outputs, but NCrunch would display just stuff like this:
[48;5;21m1[49m|[48;5;0ma[49m[48;5;0mb[49m[48;5;0mc[49m[38;5;196;48;5;0m[39;49m[48;5;0m1[49m[48;5;0m2[49m[48;5;0m3[49m
[48;5;21m1[49m|[48;5;0ma[49m[48;5;0mb[49m[48;5;0mc[49m[0m [0m[48;5;0m1[49m[48;5;0m2[49m[48;5;0m3[49m
Remco NCrunch Developer
#17702
31 Oct 2024 22:57 UTC
Thanks for sharing this suggestion. We've actually wanted this ourselves for years, since we also use large trace outputs ourselves, and having the ability to colourise them would be really nice.
We made several attempts at it, but discovered it was actually much harder than we expected it to be due to the levels of optimisation around the text control used to show the trace output. We have an additional constraint that Rider and VS don't: We need to be able to perform a full refresh of the visible trace output without utilising the UI thread for more than 20ms on mid-range hardware. This is because under NCrunch, the tests are re-run while you're working in code, so having the window update itself in an expensive way can have a noticeable impact on the 'drag' inside the IDE.
Difficult is not the same as impossible, and there are potential solutions to this problem, but they require a lot of work, which makes it unlikely that we'll be implementing this.
We made several attempts at it, but discovered it was actually much harder than we expected it to be due to the levels of optimisation around the text control used to show the trace output. We have an additional constraint that Rider and VS don't: We need to be able to perform a full refresh of the visible trace output without utilising the UI thread for more than 20ms on mid-range hardware. This is because under NCrunch, the tests are re-run while you're working in code, so having the window update itself in an expensive way can have a noticeable impact on the 'drag' inside the IDE.
Difficult is not the same as impossible, and there are potential solutions to this problem, but they require a lot of work, which makes it unlikely that we'll be implementing this.
This could be SUPER helpful.
I and my team also suffers with NO RTF/HTML support in NCRUNCH trace output.
How we may donate, to get this feature.
I and my team also suffers with NO RTF/HTML support in NCRUNCH trace output.
How we may donate, to get this feature.
Post a reply
Log in to reply.