Missing option and missing issue

[NathanRanallHolt]

[Enter feedback here] Where's the test pattern of creating a second SQL Server database that at least duplicates the structure of the production database? I think that should at least deserve a mention. Also if you're really pushing testing in production, what about the problem of corrupting production data?

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 5bda9745-35bb-81d2-4b57-7fbb8879eb71
• Version Independent ID: 5bda9745-35bb-81d2-4b57-7fbb8879eb71
• Content: Choosing a testing strategy - EF Core
• Content Source: entity-framework/core/testing/choosing-a-testing-strategy.md
• Product: entity-framework
• Technology: entity-framework-core
• GitHub Login: @roji
• Microsoft Alias: avickers

[roji]

@NathanRanallHolt we certainly don't recommend running tests against your production database instance, only against your production database system. In other words, if you're using SQL Server in production, this would mean testing against a separate SQL Server instance that isn't used in production. Typically that instance would be spun up on the developer's own machine (or as part of the CI process) for running tests.

[ajcvickers]

Note from triage: consider making it more explicit that the documentation does not advocate testing against a production database.