Comparison questionMedium~7 min

Interview question

When would you use Testcontainers, SQLite, or EF Core InMemory for data-access tests?

Choose Testcontainers, SQLite, or EF Core InMemory

Chooses database test infrastructure by the provider behavior a test must prove.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

EF Core InMemory is useful for simple application logic that needs a lightweight store, but it is not relational and does not prove SQL translation, constraints, or transactions. SQLite is relational and fast, but its types, SQL dialect, and concurrency differ from SQL Server or PostgreSQL. Testcontainers runs the real database engine, so it is the strongest choice when provider behavior matters.

Full answer below

Practice focus

Provider fidelity, SQL translation, constraints, transactions, speed, setup cost, and layered suites.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
All three options can execute tests, but they do not provide the same evidence. Provider differences matter precisely where data-access defects tend to hide.
EF Core InMemory is useful for simple application logic that needs a lightweight store, but it is not relational and does not prove SQL translation, constraints, or transactions. SQLite is relational and fast, but its types, SQL dialect, and concurrency differ from SQL Server or PostgreSQL. Testcontainers runs the real database engine, so it is the strongest choice when provider behavior matters.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I use the lightest option that preserves the behavior under test. A repository-free domain rule needs no database. Basic persistence wiring might use SQLite if production-specific behavior is irrelevant. Queries, migrations, collations, indexes, rowversion, locking, and provider-specific SQL should run against the production engine, usually through a disposable container. Speed is managed through shared infrastructure and isolated data, not by replacing away the risk.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
A healthy suite can have layers: many pure tests, focused host tests, and a smaller but meaningful real-database suite. I pin the container image, run migrations exactly as deployment would, and capture database logs on failure. I share the container process when useful while isolating each test's schema or data. I do not call a container test perfect production parity; configuration, scale, permissions, and managed-service behavior may still need staging checks.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Treating EF Core InMemory as a SQL Server emulator.
Using SQLite for provider-specific migrations.
Starting a new container for every tiny assertion.
Assuming containers reproduce managed production services completely.

Red flagsCandidateSigns the approach is fragileSignals that an interviewer may treat as risky.Open details

Details

Queries pass in tests but fail translation in production.
Constraint and transaction behavior is never exercised.
The real-database suite is so slow that everyone skips it.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What does EF Core InMemory not model?
When is SQLite enough?
How would you keep container tests fast?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Go deeper

Practice the next layer of the same subject.

Retry Transaction Unit

Opening drill

Comparison questionMedium~7 min

Interview question

When would you use Testcontainers, SQLite, or EF Core InMemory for data-access tests?

Choose Testcontainers, SQLite, or EF Core InMemory

Chooses database test infrastructure by the provider behavior a test must prove.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Provider fidelity, SQL translation, constraints, transactions, speed, setup cost, and layered suites.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
All three options can execute tests, but they do not provide the same evidence. Provider differences matter precisely where data-access defects tend to hide.
EF Core InMemory is useful for simple application logic that needs a lightweight store, but it is not relational and does not prove SQL translation, constraints, or transactions. SQLite is relational and fast, but its types, SQL dialect, and concurrency differ from SQL Server or PostgreSQL. Testcontainers runs the real database engine, so it is the strongest choice when provider behavior matters.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I use the lightest option that preserves the behavior under test. A repository-free domain rule needs no database. Basic persistence wiring might use SQLite if production-specific behavior is irrelevant. Queries, migrations, collations, indexes, rowversion, locking, and provider-specific SQL should run against the production engine, usually through a disposable container. Speed is managed through shared infrastructure and isolated data, not by replacing away the risk.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
A healthy suite can have layers: many pure tests, focused host tests, and a smaller but meaningful real-database suite. I pin the container image, run migrations exactly as deployment would, and capture database logs on failure. I share the container process when useful while isolating each test's schema or data. I do not call a container test perfect production parity; configuration, scale, permissions, and managed-service behavior may still need staging checks.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Treating EF Core InMemory as a SQL Server emulator.
Using SQLite for provider-specific migrations.
Starting a new container for every tiny assertion.
Assuming containers reproduce managed production services completely.

Red flagsCandidateSigns the approach is fragileSignals that an interviewer may treat as risky.Open details

Details

Queries pass in tests but fail translation in production.
Constraint and transaction behavior is never exercised.
The real-database suite is so slow that everyone skips it.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What does EF Core InMemory not model?
When is SQLite enough?
How would you keep container tests fast?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Go deeper

Practice the next layer of the same subject.

Retry Transaction Unit

When would you use Testcontainers, SQLite, or EF Core InMemory for data-access tests?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper

When would you use Testcontainers, SQLite, or EF Core InMemory for data-access tests?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper