# IT:AD:XUnit #

<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}
* See also:
  * [[IT/AD/NUnit/]]
  * [[IT/AD/FluentAssertions/]]
  * [[IT/AD/Effort/]]
  * [[IT/AD/Pester/]]
  * [[it/ad/unit_testing/]]


</callout>


## Summary ##

By the same people who wrote NUnit.

They rewrote it to propose a new way to test, rather than break NUnit.

Should you switch? Probably not: millions of lines of code have been written using NUnit, so NUnit not going away.  If you are wed to Setup/Teardown, then it's probably not worth the effort to switch.  But if you are not using Setup/Teardown.




* Advantages:
  * Has a lot of traction (eg: used by Microsoft for their open source Asp.Net Core)
  * You don't need to decorate the class anymore -- any method decorated with `[Fact]` is good to go as a test.
* Considerations:
  * Doesn't have the Fluent methods that [[IT/AD/NUnit/]] had -- for that, you need to install [[IT/AD/FluentAssertions/]]
  * Doesn't have a concept setup/teardown. That's a key reason why porting old tests from [[IT/AD/NUnit/]] can be a challenge.