How does this differ from Respawn?

[lonix1]

How does this differ from Respawn?

[uladz-zubrycki]

@lonix1 It's a good observation that libraries do have a lot of similarities: both claim to help you to manage your test database by keeping it in a well-known and determined state. But while Respawn cares about data cleanup only, Reseed is focused on data restore as a whole, i.e not only is it able to delete the data, but also to insert it back.

Data needs to be specified in one or multiple data files (xml format only for now, see Data Providers documentation section for additional details) and is to be used by Reseed to generate sql insert scripts based on it.

Examples section should give you a better understanding of the idea.

Having said that, Reseed could also be used for the cleanup logic execution only, thus merely behave same way as Respawn.
This is how the configuration for this case might look like

SeedMode.CleanupOnly(CleanupDefinition.Script(
    CleanupMode.PreferTruncate(), 
    CleanupTarget.Including(f => f.IncludeSchemas("dbo"))));

I'd say that difference for cleanup-only case is that scripts generation behavior is slightly more configurable for Reseed, e.g you could use DELETE FROM, TRUNCATE TABLE or a mix of those for each table cleanup. On the other hand there also could be some features unique to Respawn, I haven't done a deep comparison yet.

Hope it helps and let me know if any additional clarification is needed.

[lonix1]

Thank you for the detailed answer! So Respawn is really for deleting whereas Reseed is for deleting and seeding. Basically it has more features.