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

Testing Infrastructure for Cohosting #10603

Closed
6 tasks done
davidwengier opened this issue Jul 10, 2024 · 1 comment
Closed
6 tasks done

Testing Infrastructure for Cohosting #10603

davidwengier opened this issue Jul 10, 2024 · 1 comment
Assignees

Comments

@davidwengier
Copy link
Contributor

davidwengier commented Jul 10, 2024

TODO:

@davidwengier davidwengier self-assigned this Jul 10, 2024
@davidwengier davidwengier added this to the 17.12 Preview 1 milestone Jul 10, 2024
davidwengier added a commit that referenced this issue Jul 17, 2024
Part of #9519 and
#10603

This was fairly straight forward too, though adding MVC files to the mix
found a bug in our test data, which is kind of humorous.

I decided not to copy all of the semantic tokens tests we have, but
rather just create something reasonably all-encompassing. The core
engine is shared so both sets of tests exercise it anyway.
davidwengier added a commit that referenced this issue Jul 17, 2024
Part of #9519 and
#10603

This time I did copy the existing tests, because everything was inline
so it was easier.
davidwengier added a commit that referenced this issue Jul 18, 2024
Part of #9519 and
#10603
Requires dotnet/roslyn#74402

Removes a little more dodginess in the cohosting tests by actually using
the `RazorPinnedSolutionInfoWrapper` for solution checksums, just like
the real OOP services.
davidwengier added a commit that referenced this issue Jul 19, 2024
Part of #9519 and
#10603

After this, all cohost endpoints have test coverage 😁
@davidwengier
Copy link
Contributor Author

Moved future work to a separate issue, as they are longer term goals. Closing this as completed.

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

1 participant