Hi, thanks for sharing this.

This isn't a use case we're currently testing for, so it's hard for me to be certain how NCrunch would behave when fed escape sequences inside test names. There are multiple layers of complexity involved here, including the test framework itself. It's quite possible that there is a layer deliberately mangling or removing the sequences to try and prevent downstream problems.

I've made a note for us to investigate how these cases get handled, to see if they need further attention. Generally though, I would recommend avoiding the use of any kind of escape sequence inside test case parameter data. This is because the parameter data is used to construct a part of the visible test name, which is rendered extensively through the UI, ranging everywhere from popups to HTML reports. Given the different rendering contexts, fonts and other considerations, it's hard to predict how different areas of the UI will behave when fed these sequences. If you need to use them for testing your code, I'd recommend declaring them inside test methods rather than using them as test case parameters.