abp-testing

Inherit from your project's ApplicationTestBase, resolve the service with GetRequiredService, and call its methods directly against a real SQLite in-memory database. Assert results with Shouldly, such as result.Name.ShouldBe or Should.ThrowAsync for exceptions.

ABP recommends integration tests over unit tests. Tests run with real services and a fresh in-memory database per test, so internal services are not mocked and behavior is verified end to end.

Implement IDataSeedContributor with ITransientDependency and insert entities through repositories in the SeedAsync method. Use static Guid constants for test entity IDs so tests can reference seeded records deterministically.

Call context.Services.AddAlwaysAllowAuthorization() inside the ConfigureServices override of your test module. This bypasses permission checks so application service tests can run without configuring test users and roles.

Yes, use NSubstitute in ConfigureServices to create substitutes such as Substitute.For<IEmailSender>() and register them with AddSingleton. Only external services should be mocked; internal services use real implementations.

Wrap the test logic in CurrentTenant.Change(tenantId) to switch the ambient tenant context, then assert that repository or app service queries return only records belonging to that tenant.