From 937fe86acf4a44ea63fc3339a044cf1bacdb9630 Mon Sep 17 00:00:00 2001 From: Ma Liming Date: Fri, 14 Nov 2025 09:48:48 +0800 Subject: [PATCH] Fix typo in integration tests documentation Fix #24172 --- docs/en/testing/integration-tests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/testing/integration-tests.md b/docs/en/testing/integration-tests.md index dce7813e45..c87d270747 100644 --- a/docs/en/testing/integration-tests.md +++ b/docs/en/testing/integration-tests.md @@ -350,7 +350,7 @@ There are multiple overloads of the `WithUnitOfWorkAsync` method that you can us ## Working with DbContext -In some cases, you may want to directory work with the [Entity Framework's `DbContext` object](https://learn.microsoft.com/en-us/dotnet/api/system.data.entity.dbcontext) to perform database operations in your test methods. In this case, you can use `IDbContextProvider`service to obtain a `DbContext` instance inside a unit of work. +In some cases, you may want to directly work with the [Entity Framework's `DbContext` object](https://learn.microsoft.com/en-us/dotnet/api/system.data.entity.dbcontext) to perform database operations in your test methods. In this case, you can use `IDbContextProvider`service to obtain a `DbContext` instance inside a unit of work. The following example shows how you can create a `DbContext` object in a test method: