Testing strategy for your ASP.NET Core micro-service
summary
Argues for a four‑layer strategy: unit tests for logic, integration tests that spin real databases in Docker and clean state between runs, service tests run with TestHost and fake external APIs via WireMock.net or MockServer, and a few targeted end‑to‑end or smoke tests only for business‑critical flows; recommends Pact for consumer‑driven contract checks across teams, warns about slow suites (examples of multi‑hour end‑to‑end runs), stresses deterministic, readable tests and automating setup/teardown so tests remain fast and reliable.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:49The complexity of testing micro services
- 4:28Different types of tests
- 11:07ASP.NET Core microservice architecture
- 13:42Example: unit test
- 17:20Example: integration test
- 23:06Setting environments for integration tests
- 25:04Testing with cloud based services
- 28:24Testing in the Cloud vs. using emulators
- 29:49Service tests
- 38:47Using BDD Frameworks
- 50:58Summery: Testing micro services
related talks
45mTesting Your Web Apps
54m.NET Testing Best Practices
43m.NET Testing Best Practices
58mTesting Strategy - New Model, Better Outcomes
45mBuilding a successful test automation architecture in a microservices environment
01h 02mTesting First - Getting The How
51mFallacies of Unit Testing
50mCreate Web APIs with ASP.NET Core Using Outside In TDD