Interview Q&A

Short answer: Initial learning curve and mindset shift. Writing tests for complex scenarios or legacy code. Overhead in writing and maintaining tests. Possible resistance from teams unfamiliar with the practice.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: TDD relies heavily on unit tests as the foundation. It’s a process where unit tests are created first to define requirements, then production code is written to pass those tests.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: (Example) I wrote a simple calculator class using TDD: First, I wrote a test for addition, saw it fail, implemented Add() method, passed the test, then refactored. Repeated for subtraction, multiplication, etc., ensuring robust code with full test coverage.

Real-world example (ShopNest)

Arrange a cart with 2 items → Act Checkout() → Assert total and that payment was called once.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Testing frameworks: xUnit, NUnit, MSTest. Mocking libraries: Moq, NSubstitute. IDE support: Visual Studio’s Test Explorer. CI tools: Azure DevOps, GitHub Actions, Jenkins for automated test runs.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use mocking and dependency injection to isolate the unit under test, allowing tests to focus on behavior without relying on external resources.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Mock external dependencies. Keep tests focused and independent. Avoid I/O operations in unit tests. Run tests frequently during development.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: TDD writes tests before code, driving design and implementation. Traditional testing usually happens after coding, as a verification step. TDD promotes continuous testing and refactoring, while traditional testing may be more manual or batch-driven. Integration Testing

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Integration testing verifies that multiple components or systems work together correctly, unlike unit testing which tests individual units in isolation. It focuses on interactions between modules, databases, APIs, or external services.

Example code

Integration testing verifies that multiple components or systems work together correctly, unlike unit testing which tests individual units in isolation. It focuses on interactions between modules, databases, APIs, or external services.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: You write integration tests by creating test projects that exercise multiple components together, often involving real or in-memory databases, services, or APIs. You use frameworks like xUnit or NUnit and configure dependencies to mimic production-like environments.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: xUnit, NUnit, MSTest for test execution. Entity Framework Core InMemory provider or SQLite for database testing. TestServer in ASP.NET Core for testing web APIs. Tools like Respawn for database cleanup.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: You use a test database or in-memory database to run queries and verify data persistence and retrieval, ensuring the data layer works as expected without affecting production data.

Real-world example (ShopNest)

Arrange a cart with 2 items → Act Checkout() → Assert total and that payment was called once.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use separate configuration files or environment variables for tests, injecting connection strings and service endpoints specific to the test environment.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use test-specific databases or in-memory databases. Use transactions with rollback or database cleanup scripts between tests. Avoid connecting to production environments during tests.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Mocking/stubbing replaces external dependencies like web services or message queues with controlled test doubles to isolate the parts under test and control external behavior without invoking real services.

Real-world example (ShopNest)

When testing ShopNest’s order service, mock IPaymentGateway so tests do not call Razorpay.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Configure pipeline steps to run integration tests after build, using test runners, setting up test databases, and cleaning up after tests. Use containers or managed services to mimic production-like environments.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Leverage dependency injection to replace real services with test implementations or mocks. Use setup and teardown methods to initialize and dispose of dependencies per test.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: In-memory databases allow fast, isolated testing of data access code without a real database, making integration tests easier to run and maintain, but may lack certain behaviors of real databases (like relational constraints). Practical & Advanced Topics

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Typically, test projects mirror the structure of the production projects, organized by feature or layer. For example, you might have MyApp.Core.Tests, MyApp.Web.Tests, and MyApp.Data.Tests. Tests are grouped by functionality to keep code maintainable and discoverable.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use mocking frameworks like Moq to create mock implementations of service interfaces. For HTTP calls, tools like HttpClientFactory with a mocked HttpMessageHandler or libraries like RichardSzalay.MockHttp help simulate HTTP responses.

Real-world example (ShopNest)

When testing ShopNest’s order service, mock IPaymentGateway so tests do not call Razorpay.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Dependency Injection (DI) is a design pattern where dependencies are provided rather than created inside a class. DI makes testing easier by allowing tests to inject mock or fake implementations of dependencies, isolating the unit under test.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Best practice is to test private methods indirectly through public methods. If needed, internal methods can be exposed to test projects using InternalsVisibleTo attribute. Reflection can be used but is generally discouraged as it breaks encapsulation.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Mark test methods with async Task and use await to call asynchronous methods. Most test frameworks like xUnit, NUnit, and MSTest support async tests natively. [TestMethod] public async Task AsyncMethod_ShouldReturnTrue()

Example code

{
var result = await myService.DoWorkAsync(); Assert.IsTrue(result); }

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use assertion methods that expect exceptions. For example, in MSTest: [TestMethod] [ExpectedException(typeof(InvalidOperationException))] public void Method_ShouldThrowException()

Example code

{ myService.DoSomethingInvalid(); } Or in xUnit: await Assert.ThrowsAsync<InvalidOperationException>(() => myService.DoSomethingInvalidAsync());

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Test doubles are objects used in place of real components for testing. Types include: Dummy: Passed but never used. Stub: Provides canned responses. Mock: Verifies interactions. Fake: Working but simplified implementation. Spy: Records information about calls.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Stub: Provides predefined data to the test. Mock: Verifies that certain interactions happened. Fake: Has a working implementation, often simpler than production.

Real-world example (ShopNest)

When testing ShopNest’s order service, mock IPaymentGateway so tests do not call Razorpay.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.