home.social

#xunit — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #xunit, aggregated by home.social.

fetched live
  1. I my daily work I'm maintaining a #dotnet software containing ~5K unit tests including #WPF view model tests.

    Most of the work they do is #async, started by 'AsyncRelayCommands'. This means waiting and asserting state changes is also async. Therefore #xunit tests are waiting often for `ManualResetEventSlim' to fire triggered by 'INotifyPropertyChanged' events.

    I have wrapped this nicely in some lines of code which will result in test code being easier on the eyes in my opinion. Maybe this is useful someone else?

    For details see:

    github.com/wgross/property-cha

  2. I my daily work I'm maintaining a software containing ~5K unit tests including view model tests.

    Most of the work they do is , started by 'AsyncRelayCommands'. This means waiting and asserting state changes is also async. Therefore tests are waiting often for `ManualResetEventSlim' to fire triggered by 'INotifyPropertyChanged' events.

    I have wrapped this nicely in some lines of code which will result in test code being easier on the eyes in my opinion. Maybe this is useful someone else?

    For details see:

    github.com/wgross/property-cha

  3. I my daily work I'm maintaining a #dotnet software containing ~5K unit tests including #WPF view model tests.

    Most of the work they do is #async, started by 'AsyncRelayCommands'. This means waiting and asserting state changes is also async. Therefore #xunit tests are waiting often for `ManualResetEventSlim' to fire triggered by 'INotifyPropertyChanged' events.

    I have wrapped this nicely in some lines of code which will result in test code being easier on the eyes in my opinion. Maybe this is useful someone else?

    For details see:

    github.com/wgross/property-cha

  4. I my daily work I'm maintaining a #dotnet software containing ~5K unit tests including #WPF view model tests.

    Most of the work they do is #async, started by 'AsyncRelayCommands'. This means waiting and asserting state changes is also async. Therefore #xunit tests are waiting often for `ManualResetEventSlim' to fire triggered by 'INotifyPropertyChanged' events.

    I have wrapped this nicely in some lines of code which will result in test code being easier on the eyes in my opinion. Maybe this is useful someone else?

    For details see:

    github.com/wgross/property-cha

  5. @xunit @bradwilson Is there already a date, when #Xunit v2 will no longer be supported (will no longer receive bug fixes or security fixes)?

  6. @xunit @bradwilson Is there already a date, when #Xunit v2 will no longer be supported (will no longer receive bug fixes or security fixes)?

  7. @xunit @bradwilson Is there already a date, when #Xunit v2 will no longer be supported (will no longer receive bug fixes or security fixes)?

  8. @xunit @bradwilson Is there already a date, when #Xunit v2 will no longer be supported (will no longer receive bug fixes or security fixes)?

  9. @bradwilson I saw your issue about #JetBrainsRider not supporting @xunit v3 with Microsoft.Testing.Platfrom v2

    With #dotnet 10 how would a minimal project using MTP v2 and #xunit v3 look like now.

    Like this?

    github.com/bitbonk/rider-mtp-v

    Or do I still need the xunit.v3.mtp-v2 package or even the bool msbuild properties
    TestingPlatformDotnetTestSupport or UseMicrosoftTestingPlatformRunner

  10. @bradwilson I saw your issue about #JetBrainsRider not supporting @xunit v3 with Microsoft.Testing.Platfrom v2

    With #dotnet 10 how would a minimal project using MTP v2 and #xunit v3 look like now.

    Like this?

    github.com/bitbonk/rider-mtp-v

    Or do I still need the xunit.v3.mtp-v2 package or even the bool msbuild properties
    TestingPlatformDotnetTestSupport or UseMicrosoftTestingPlatformRunner

  11. @bradwilson I saw your issue about #JetBrainsRider not supporting @xunit v3 with Microsoft.Testing.Platfrom v2

    With #dotnet 10 how would a minimal project using MTP v2 and #xunit v3 look like now.

    Like this?

    github.com/bitbonk/rider-mtp-v

    Or do I still need the xunit.v3.mtp-v2 package or even the bool msbuild properties
    TestingPlatformDotnetTestSupport or UseMicrosoftTestingPlatformRunner

  12. @bradwilson I saw your issue about #JetBrainsRider not supporting @xunit v3 with Microsoft.Testing.Platfrom v2

    With #dotnet 10 how would a minimal project using MTP v2 and #xunit v3 look like now.

    Like this?

    github.com/bitbonk/rider-mtp-v

    Or do I still need the xunit.v3.mtp-v2 package or even the bool msbuild properties
    TestingPlatformDotnetTestSupport or UseMicrosoftTestingPlatformRunner

  13. Apparently #tunit runs a lot more in parallel compared to #xunit.

    It also uses source generation so test discovery is a lot faster.

    #dotnet

    youtube.com/watch?v=S11Moa7kfP

  14. Apparently runs a lot more in parallel compared to .

    It also uses source generation so test discovery is a lot faster.

    youtube.com/watch?v=S11Moa7kfP

  15. Apparently #tunit runs a lot more in parallel compared to #xunit.

    It also uses source generation so test discovery is a lot faster.

    #dotnet

    youtube.com/watch?v=S11Moa7kfP

  16. Apparently #tunit runs a lot more in parallel compared to #xunit.

    It also uses source generation so test discovery is a lot faster.

    #dotnet

    youtube.com/watch?v=S11Moa7kfP

  17. I just spent 4 hours writing #XUnit tests to prove a point. Constructive pedantry!

  18. I just spent 4 hours writing #XUnit tests to prove a point. Constructive pedantry!