We just shipped new prerelease versions of the core framework and the Visual Studio adapter.

- We've added new overloads of Assert.RaisesAny and Assert.RaisesAnyAsync
- We've made SerializationHelper public
- We've fixed potential analyzer errors for users of xunit.assert.source
- We've fixed a bug in the Visual Studio adapter that affected runner authors.

Release notes:

https://xunit.net/releases/v2/2.5.1-pre.33
https://xunit.net/releases/visualstudio/2.5.1-pre.15

#dotnet #csharp #fsharp #unittest #tdd

Welcome to the new home for xUnit.net on Mastodon! We thank you for joining us. 😀

Home page: https://xunit.net/

Source code: https://github.com/xunit

If you'd prefer to follow via RSS, you can find that feed here: https://dotnet.social/@xunit.rss

#introduction #dotnet #csharp #fsharp #unittest #tdd

We just shipped new prerelease versions of the core framework, the Visual Studio adapter, and analyzers.

There is one new analyzer, and two bug fixes in the core framework. There are no changes in the Visual Studio adapter other than picking up the new framework dependencies.

Please test these as they are likely to become the RTM versions.

Release notes:

https://xunit.net/releases/v2/2.5.1-pre.26
https://xunit.net/releases/analyzers/1.3.0-pre.19
https://xunit.net/releases/visualstudio/2.5.1-pre.11

#dotnet #csharp #fsharp #unittest #tdd

Have you noticed that code coverage numbers have dropped when you switched from a 2.4.x to 2.5.x build of `xunit.runner.visualstudio`? Are you inadvertently dependent on the fact that we used to load all assemblies on startup but don't any more? Take a look at this issue: https://github.com/xunit/visualstudio.xunit/issues/381#issuecomment-1682843556 #dotnet #csharp #fsharp #unittest #tdd

Unit-testing a web service in #Rust - by Julio Merino

https://jmmv.dev/2023/07/unit-testing-a-web-service.html

#UnitTest #WebService #Testing #SoftwareEngineering #RustLang

Since XCTest dose not support async expressions in its assert functions I released SwiftAsyncAsserts to fill that gap.

Write more readable testing code for your async APIS in Swift with SwiftAsyncAssert Swift package.

https://github.com/angu-software/SwiftAsyncAssert

#swift #xctest #asyncawait #unittest

We just shipped new prerelease versions of the core framework, the Visual Studio adapter, and analyzers.

There are a couple new analyzers, and a new feature in the Visual Studio adapter (in addition to bugs fixed).

Please test these as they're likely to become the RTM versions.

Release notes:

https://xunit.net/releases/v2/2.5.1-pre.20
https://xunit.net/releases/analyzers/1.3.0-pre.13
https://xunit.net/releases/visualstudio/2.5.1-pre.10

#dotnet #csharp #fsharp #unittest #tdd

We're going to ship another 2.5.1 prerelease next week. Make sure to let us know what should go into it with new/updated issues and discussions. #dotnet #csharp #fsharp #unittest #tdd

The move to feedz.io is complete. Note that only new package builds will go here; if you're currently using the MyGet feed for prerelease packages, please ONLY update to feedz.io when you're ready to take newer dependencies.

New package list: https://feedz.io/org/xunit/repository/xunit/search
New feed URL: https://f.feedz.io/xunit/xunit/nuget/index.json
Updated packages docs: https://xunit.net/docs/nuget-packages
Updated v3 alpha docs: https://xunit.net/docs/v3-alpha

#dotnet #csharp #fsharp #unittest #tdd

For the next prerelease build of `xunit.runner.visualstudio`, we are shipping the ability to pass all xUnit.net configuration items via RunSettings (as an XML file and/or via `dotnet test` command line switches).

The documentation page on how this works has just gone live: https://xunit.net/docs/runsettings

#dotnet #csharp #fsharp #unittest #tdd

Can anybody point me to a good resource explaining how to do automated integration testing with #microsoftGraph ? I've got a web app and want to be sure it does what I think it does before I unleash it on a production SharePoint site.

#integrationTest #unitTest #webdev #wootItLooksLikeItWorks

@glyph @itamarst By the way, I understand the concerns about #oop subclasses and generally am trying to avoid them nowadays. And of course avoiding multiple inheritance like the plague that it is. But they are still useful sometimes. For example, I will use a "TestBase" base class of the type I often employ to provide a toolbox of #unittest methods for multiple independent classes doing related things.

{tetthat} is great for automatic testing. Here are some tricks for the heavy user: https://blog.r-hub.io/2020/11/18/testthat-utility-belt/ #rstats #testing #unittest #testthat

We just shipped new prerelease versions of the core framework, the Visual Studio adapter, and analyzers.

Note: This v2 2.5.1 release is targeted primarily at fixing issues with the new assertion library.

This is also the first prerelease build that fixes the issues with package signature verification (NU3003 errors) that affected the 2.5.0 release.

Release notes:

https://xunit.net/releases/v2/2.5.1-pre.11
https://xunit.net/releases/analyzers/1.3.0-pre.6
https://xunit.net/releases/visualstudio/2.5.1-pre.4

#dotnet #csharp #fsharp #unittest #tdd

Should we use #coverage reports only for #unittest or also for integration and functional testing?

Should the test directory split into unit, integration and functional tests or should all tests in one root tests folder? (Both following the namespace rules)

#question #codequality

Have you also verified what happens when you call your method twice?🤓 ✌️

#Programming #UnitTest #Testing #Quality

Due to the code signing problems caused by the .NET Foundation switchover to the Microsoft Time Stamping service, we were definitely going to want to ship a 2.5.1 release.

We also expected there to be issues with the overhauled assertion library changes in 2.5.0. We've already fixed a few:

https://github.com/xunit/xunit/issues/2743
https://github.com/xunit/xunit/issues/2749
https://github.com/xunit/xunit/issues/2750
https://github.com/xunit/xunit/issues/2755

There will be a 2.5.1 prerelease this coming week for people to test.

#dotnet #csharp #fsharp #unittest #tdd

SoftwareDev.assert('no unit tests', INSANITY);

Passed: 1 Failed: 0

#SoftwareDevelopment #SoftwareEngineering #UnitTest #Testing #Quality #Insanity #TDD

Not every #python project I have worked on has 100% #unittest coverage, nor should they, as perfect is the enemy of good.

However, I enforce the use of coverage.py’s fail_under with two simple rules:
1. It can only go up in a merge request.
2. It must stay 1 or 2 percent under current coverage.

This allows some leeway which can be useful during refactoring, while ensuring coverage won’t decrease overall.

Writing a #UnitTest for each significant piece of my #Python code is a pain in the ass. Sometimes it feels like I spend most of my #programming time writing test code instead of the stuff I actually want.

But then I add a feature or optimize something and debugging is as simple as making various tests pass again and I’m glad to have invested all that time in the parallel universe of a well-built test suite.

It’s like wearing an N95 during a pandemic, except for your code instead of your brain.