Based on this poll, we will be removing support for Visual Studio 2019 and out-of-support versions of Visual Studio 2022 from `xunit.analyzers` sometime before the final 2.0.0 release.
Based on this poll, we will be removing support for Visual Studio 2019 and out-of-support versions of Visual Studio 2022 from `xunit.analyzers` sometime before the final 2.0.0 release.
What version of Visual Studio are you using with xUnit.net? [ ] VS 2019 [ ] VS 2022 (< 17.8) [ ] VS 2022 (>= 17.8) [ ] VS 2026
We just shipped Core Framework v3 4.0.0-pre.81, Analyzers 2.0.0-pre.40, and VS Adapter 4.0.0-pre.4.
This release adds several new analyzers and fixes many bugs, especially related to Native AOT support.
https://xunit.net/releases/v3/4.0.0-pre.81
https://xunit.net/releases/analyzers/2.0.0-pre.40
https://xunit.net/releases/visualstudio/4.0.0-pre.4
Do you write custom TraitAttribute-derived attributes? Do you think they'd be useful in the core framework? If so, chime in with your suggestions here: https://github.com/xunit/xunit/discussions/3537
We just shipped Core Framework v3 4.0.0-pre.33, Analyzers 2.0.0-pre.9, and VS Adapter 4.0.0-pre.3.
This prerelease build adds support for Native AOT, in addition to bug fixes.
https://xunit.net/releases/v3/4.0.0-pre.33
https://xunit.net/releases/analyzers/2.0.0-pre.9
https://xunit.net/releases/visualstudio/4.0.0-pre.3
I have an older legacy project where integration tests isn't set up and would be quite complex to do, so using "unit tests" mechanics via substitutes and executed call checks - it works, but a bit cumbersome to write and maintain, but still loads better than manually testing complex import flows.
Finding a failing test 🚨, coming back from the ☕️ break, feels just so ✅ .
- I know where I left off
- I know what to continue with
- I get back into the flow within seconds
- no need to search and analyze the git history
- it 💡 enlightens me and lets me continue where i left off
also when doing hashtag#PHP 😎