integration-tests · git:20261102.5ba4ece · 2026-11-02 · sha256 4e098c61d7eadfad
integration-tests git:20261102.5ba4eceA
Immutable. This exact content never changes and is served at /api/v1/blob/4e098c61d7eadfad.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_vbg4mwnpae4mbc6h/4e098c61d7eadfad79ad0fe3ad7a5e780cf55b302d768aa8e7f377065714d276.json
Then /plugin install integration-tests@markdownregistry-vbg4mwnpae4mbc6h in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
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) | `Data Source=Tests-{Guid};Mode=Memory;Cache=Shared` with sample data on |
## Steps
1. Repository tests: make the test class `sealed` and `IDisposable`, create `private readonly MovieReviewsTestDatabase database = new();` and dispose it. Use `this.database.Repository`, and `this.database.Context` to find known rows.
2. Find rows by their known values, not by position.
3. For time-dependent results, assert against `this.database.TimeProvider`.
4. Presentation tests: create a new application host per test class instance, pass settings in through its constructor, and make real requests. Assert the status code, then the body.
5. Override settings in memory through the host's `settings` dictionary. Never edit appsettings files for a test.
6. The details of this template's application host are in `presentation-integration-tests`.
## Example
```csharp
// 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 `IClassFixture` or `ICollectionFixture`.
- Write to `movie-reviews.db` or any file.
- Depend on test order.
## Check
``` bash
dotnet test tests/Infrastructure.Tests.Integration
dotnet test tests/Presentation.Tests.Integration
```