Skip to main content
ANVISoftware Solutions

Automated Testing

Intermediate12-16 hours4 modules13 lessons

Write tests that let you change code with confidence: unit, integration and API tests, test doubles, and what coverage really tells you.

Start the first lesson

Prerequisites

  • C# fundamentals
  • Basic ASP.NET Core or another application to test

Technologies

About this course

Tests exist so you can change code without re-checking everything by hand. That is the whole justification, and it is worth keeping in view, because tests written for any other reason tend to be the ones teams delete.

This course starts with a single unit test and builds up through test doubles, integration tests that use a real database, and API tests that exercise a running application.

It also covers what to leave untested. Tests that assert implementation details rather than behaviour make refactoring harder, which is the opposite of the point.

Course roadmap

All 13 lessons are written and available.

Module 01

Testing Foundations

Why tests exist, and what a good one looks like.

4/4 ready
  1. 01Why Testing MattersExplain what tests actually buy you, and use that to judge whether a given test is worth writing.12 min
  2. 02Your First Unit TestCreate a test project, write a test, and run it.16 min
  3. 03Arrange, Act, AssertStructure tests so a failure points to a single cause.14 min
  4. 04AssertionsAssert precisely, and write failure messages that explain themselves.16 min

Module 02

Isolating What You Test

Replace awkward dependencies, and know which kind of replacement you need.

3/3 ready
  1. 01Test DoublesDistinguish stubs, mocks, fakes and spies, and pick the right one.16 min
  2. 02MockingReplace a dependency without coupling the test to implementation detail.17 min
  3. 03Test DataBuild readable test data that makes the scenario obvious.15 min

Module 03

Integration and API Testing

Test the wiring, not just the pieces.

3/3 ready
  1. 01Integration TestsTest against real infrastructure to catch wiring mistakes.20 min
  2. 02Testing an APIExercise a running application over HTTP, including failure paths.20 min
  3. 03End-to-End TestsCover critical journeys without building a slow, brittle suite.18 min

Module 04

Testing in Practice

Organise the suite, read coverage honestly, and keep it green in the pipeline.

3/3 ready
  1. 01Organising a Test SuiteName and group tests so failures are easy to interpret.16 min
  2. 02Coverage, HonestlyUse coverage as a hint and explain what it cannot tell you.16 min
  3. 03Tests in the PipelineRun tests on every change and keep them reliable.18 min

Projects for this course

Intermediate

Employee Management API

A production-shaped web API: validated, paged, documented, secured, backed by a real database and covered by tests.

25-35 hours

On completion

What you should take away

  • Tests buy you the freedom to change code, and that is how to judge whether one is worth writing
  • Test behaviour, not implementation, or refactoring becomes harder instead of easier
  • Integration tests catch the wiring mistakes unit tests cannot see
  • Coverage measures execution, not correctness

Recommended next course

Software Architecture

Structure systems deliberately: layering, SOLID, clean architecture, patterns, and honest guidance on when each is the wrong choice.

Continue to Architecture

Have a project worth talking through?

Tell us what you're building or what's slowing your current system down. We'll give you a direct read on scope and approach.

Start a ConversationExplore Our Services