Repository navigation
test: use Roslyn framework alongside focused unit tests - #56
ScottishTapWater wants to merge 16 commits into
Conversation
Licence compliance passedThe current ORT run passed. |
[Low impact] The reviewed changes appear safe to merge, with no new actionable issues established.
|
|
@codex review |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Breezy! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Use Microsoft.CodeAnalysis.Testing for analyser, code-fix and generator integration tests. Keep focused unit tests for plans, symbol readers, discovery and emitters, with exhaustive data matrices at those boundaries.
Retain semantic generator tests for inference, overload selection, nullable lifting, metadata and discovery across dependent operations. Execute their resulting compilations in memory to check numerical results alongside binding. Embedded C# uses formatted multiline raw strings.
Three fixtures prepare packages for archive inspection, delivery and A/B/C interoperability. Each packs its inputs once. Consumer projects retain separate feeds and caches. The A/B/C test checks shared type identity and downstream arithmetic across two independently packed producers.
The diff is confined to the two test projects and solution ordering. Production code and CI are unchanged. The test dependency Microsoft.VisualStudio.Validation uses recognised MIT licence metadata.
Validation: