-
Notifications
You must be signed in to change notification settings - Fork 183
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
Add recording file location #6517
Conversation
Some tests have a need to parse data out of their recordings. When playback is started for a disk based recording, include a new header x-recording-file-location on the response which points to the recording.
…g, so `Assert.NotNull` will not catch bugs.
[InlineData("recordings/TestStartRecordSimplé_nosave.json", "request-response")] | ||
[InlineData("recordings/TestStartRecordSimple.json", "")] | ||
[InlineData("recordings/TestStartRecordSimpl�.json", "")] | ||
[InlineData("recordings/TestStartRecordSimplé.json", "")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed this - VS must have "helped." Should this get reverted?
tools/test-proxy/Azure.Sdk.Tools.TestProxy.Tests/PlaybackTests.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Resolve the test and I'll approve. I see where you're coming from.
Co-authored-by: Scott Beddall <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @billwert
There are tests in the Java repo which parse the recording files for various reasons. Add a header on the response of playback start to share that location.
I also noticed that the tests were using the wrong assertion for headers, so I changed it to check for string empty/null. (Even null is unnecessary - could be a test against
String.Empty
if you prefer.)