Fix CI tests for most frameworks

[Shane32]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@Shane32 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 23 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 4783cc7 and c01462c.

📒 Files selected for processing (1)

• .github/workflows/wf-build-test.yml (1 hunks)

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fixtests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Shane32]

@gfoidl I'm still fighting CI scripts at every turn. Apparently only the .NET Core 2.1 tests were running previously. I think I got it this time. Lmk if you have any comments. I'm merging so I can run tests on my other PRs.

[gfoidl]

Unfortunately for CI the most reliable way is to just try it live. So far I don't know a good way to test it in DEV environment.