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
Migrate to https://github.com/VerifyTests/Verify #10993
Conversation
} | ||
// git status --porcelain=2 --untracked-files=no -z | ||
IReadOnlyList<GitItemStatus> statuses = getAllChangedFilesOutputParser.Parse(statusString); | ||
await Verifier.VerifyJson(JsonConvert.SerializeObject(statuses)) |
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.
@SimonCropp could you give me a hint whether I missed something here? ApprovalTests produced "proper" json, and Verify appears to produce json-like output. Is there a way to retain the proper json format? And is there a reason why VerifyJson
uses .txt instead of .json for snapshots?
Thanks
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.
can u try UseStrictJson https://github.com/VerifyTests/Verify/blob/main/docs/serializer-settings.md#usestrictjson
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 for the tip, I'll give it a try.
With this PR, I cannot reproduce the project loading errors in MSVS any longer. 👍 Though the test discovery fails with the same errors yet:
Why does MSVS not find the NUnit3TestAdapter and the NUnit.ConsoleRunner although it is referenced in the solution? Adding explicit references results in warnings: The |
|
That's probably an oversight on my part... This needs to get fixed. |
I would try to repair the installation. ...or reinstall it completely. Though it's not very common these days, VS sometimes can go crook after an update. |
I have deinstalled VS, rebooted and installed it again: no improvement. BTW: The first build in VS failed with:
I could resolve this by running |
can i help ? |
Absolutely :) |
It looks like after I applied your suggestion to fix json, I didn't fix all the verified files. |
No description provided.