演示文稿
integration-tests
How integration tests run against a real SQLite database - a private in-memory database per repository test, and a per-test application host with its own database for presentation tests. Use when testing the repository, migrations, startup wiring or a real request through the presentation layer.
LeanMeanCleanApps · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add LeanMeanCleanApps/CleanMinimalApi --skill integration-tests技能说明
name: integration-tests description: How integration tests run against a real SQLite database - a private in-memory database per repository test, and a per-test application host with its own database for presentation tests. Use when testing the repository, migrations, startup wiring or a real request through the presentation layer. metadata: scope: shared
Integration tests
The rule
Integration tests use the real database engine, built from the real migrations, and every test gets its own database. No test can see another test's changes, and nothing is written to disk.
| Project | Fixture | Database |
|---|---|---|
tests/Infrastructure.Tests.Integration | MovieReviewsTestDatabase | Data Source=:memory: held open for one test, with the hand-written test data (sample-data) and a FakeTimeProvider fixed at 2009-12-31 23:51:01 UTC |
tests/Presentation.Tests.Integration | The presentation layer's application host (a WebApplicationFactory<Program> in web templates, the Handler itself in Lambda) | Data Source=Tests-{Guid};Mode=Memory;Cache=Shared with sample data on |
Steps
- Repository tests: make the test class
sealedandIDisposable, createprivate readonly MovieReviewsTestDatabase database = new();and dispose it. Usethis.database.Repository, andthis.database.Contextto find known rows. - Find rows by their known values, not by position.
- For time-dependent results, assert against
this.database.TimeProvider. - Presentation tests: create a new application host per test class instance, pass settings in through its constructor, and make real requests (in Lambda, real calls to the handler). Assert the status code, then the body.
- Override settings in memory through the host's constructor, never by editing appsettings files or leaving environment variables set.
- The details of this template's application host are in
presentation-integration-tests.
Example
// tests/Infrastructure.Tests.Integration/Databases/MovieReviews/EntityFrameworkMovieReviewsRepositoryTests.cs
public sealed class EntityFrameworkMovieReviewsRepositoryTests : IDisposable
{
private readonly MovieReviewsTestDatabase database = new();
public void Dispose()
{
this.database.Dispose();
}
[Fact]
public async Task GetAuthorById_ShouldReturn_Author()
{
// Arrange
var repository = this.database.Repository;
using var tokenSource = new CancellationTokenSource();
var token = tokenSource.Token;
var author = this.database.Context.Authors.First(a => a.FirstName == "One");
// Act
var result = await repository.GetAuthorById(author.Id, token);
// Assert
_ = result.ShouldNotBeNull();
result.Reviews.Count.ShouldBe(3);
}
}
Don't
- Use the EF Core InMemory provider. It isn't relational and lets through queries SQLite rejects.
- Share one database across tests with
IClassFixtureorICollectionFixture. - Write to
movie-reviews.dbor any file. - Depend on test order.
Check
dotnet test tests/Infrastructure.Tests.Integration
dotnet test tests/Presentation.Tests.Integration