How do you handle setup and teardown in xUnit tests?

Short answer: Use the constructor for setup code. Implement IDisposable interface for teardown (cleanup) code. Example: public class DatabaseTests : IDisposable

Example code

{
public DatabaseTests()
{ // Setup } [Fact] public void TestMethod() { }
public void Dispose()
{ // Cleanup }
}
For shared context across multiple tests, use class fixtures or collection fixtures.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.