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
I have not found any way to pass characters like #9, #13, #10 as part of a string in the parameters for test cases. This is needed when I am testing a routine to remove these and want to use parameterized tests. I can write individual tests without parameters and code it as part of the text, but it would be good to do something like
In the routine to test handles a number of valid control characters, and it would be nice to have a test for each do with parameters. Just can't work out how to do it.
I have tried adding " around the string, but the " characters become party of the parameters.
The text was updated successfully, but these errors were encountered:
Thank you @vincentparrett. I had tried various combinations, but that one I had missed. The only one I am now having issues with is #0, which obviously is quite a special character. It is just the code I am porting (and testing) is from c++. Not sure if I will ever see #0 in this project, but I would ideally like to have it working. The set of characters I am removing are #0#9#10#11#12#13#32. The actual code is in fact working, which is the goal (so the tests are not needed for now, but we should always have our tests ready for code changes... :-).
I have not found any way to pass characters like #9, #13, #10 as part of a string in the parameters for test cases. This is needed when I am testing a routine to remove these and want to use parameterized tests. I can write individual tests without parameters and code it as part of the text, but it would be good to do something like
In the routine to test handles a number of valid control characters, and it would be nice to have a test for each do with parameters. Just can't work out how to do it.
I have tried adding " around the string, but the " characters become party of the parameters.
The text was updated successfully, but these errors were encountered: