Skip to content
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

204 No Content stubbed response not being handled #1

Closed
abraramin opened this issue May 6, 2020 · 4 comments
Closed

204 No Content stubbed response not being handled #1

abraramin opened this issue May 6, 2020 · 4 comments

Comments

@abraramin
Copy link

abraramin commented May 6, 2020

I am using SystemTestingTools Version 1.3.6 . I used the recorder function to capture a 204 responce (as suggested in the project README). Then I intended to use this captured response as stub for component tests. This is what the response looks like:

METADATA
...

REQUEST
...

--!?@Divider: Any text BEFORE this line = comments, AFTER = response in Fiddler like format

HTTP/1.1 204 NoContent
Server:Microsoft-IIS/10.0
X-Powered-By:ASP.NET
Date:Tue, 05 May 2020 03:41:23 GMT

There is no response body (as expected). I am using ResponseFactory.FromFiddlerLikeResponseFile("/path/to/stubfile")

I get the following exception:
System.ArgumentException : File is not in the right format, please consult https://github.com/AlanCS/SystemTestingTools/

Modifying the captured response and using null as response content is my workaround for now.

@AlanCS
Copy link
Owner

AlanCS commented May 6, 2020

theoretically fixed in https://www.nuget.org/packages/SystemTestingTools/1.3.7, please confirm

@abraramin
Copy link
Author

I'm still getting the same error using 1.3.7 😕

@AlanCS
Copy link
Owner

AlanCS commented Aug 17, 2020

Sorry it took so lon @abraramin, but I de-prioritized it as there as a workaround.
it should be fixed in version 1.3.10; let me know !

@AlanCS
Copy link
Owner

AlanCS commented Nov 21, 2022

closing due to no further feedback

@AlanCS AlanCS closed this as completed Nov 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants