Roman Alexis Anastasini

Using code generation for test automation – the fancy way

What if refactoring your API created a compile error instead of a runtime failure? Learn a powerful code generation strategy for safer, faster API tests.

Using code generation for test automation – the fancy way
#1about 3 minutes

Setting up NSwag for OpenAPI documentation in .NET

Replace the default Swashbuckle with NSwag to generate OpenAPI specifications for a new .NET web application.

#2about 3 minutes

Automating swagger.json generation on every build

Configure the project file to automatically run the NSwag command-line tool after each build to create an up-to-date swagger.json file.

#3about 4 minutes

Generating a typed C# client for the test project

Use the generated swagger.json file to automatically create a strongly-typed C# HTTP client within the test project.

#4about 4 minutes

Using the generated client for robust API-level tests

Write API-level tests that consume the generated client, ensuring that any API signature changes result in compile-time errors.

#5about 7 minutes

Testing DTOs, validation, and API error handling

Leverage the generated client and DTOs to easily test complex validation rules, serialization formats, and API exception handling.

#6about 4 minutes

Achieving high test coverage with API-level tests

Focusing on API-level tests provides high code coverage and confidence for refactoring while reducing the effort spent on traditional unit tests.

#7about 2 minutes

Key lessons learned from this testing approach

This approach requires writing precise controller code and evolving from slow Docker-based databases to faster in-memory databases for tests.

#8about 1 minute

Q&A: Why API tests can be more efficient than unit tests

API-level tests reduce the developer time spent writing and maintaining numerous small unit tests, especially as the codebase grows.

#9about 1 minute

Q&A: Managing code coverage targets and exceptions

Set a high but realistic code coverage target like 90-95% to avoid writing useless tests for unreachable edge cases.

#10about 2 minutes

Q&A: Automating checks for breaking API changes

A potential improvement is to add a CI step that tests the new API version against a client generated from a previous API version.

#11about 2 minutes

Q&A: Managing test state and database setup

Use the web application factory to manage test setup, such as spinning up an in-memory database and seeding it with data for each test class.

#12about 2 minutes

Q&A: Mocking external service dependencies in tests

Isolate the API under test by mocking external service calls through interfaces, reserving full integration tests for the CI pipeline.

#13about 3 minutes

Q&A: The accidental discovery of this testing workflow

The idea to use the generated client in tests originated from the initial goal of providing an easy-to-use client for other consumer APIs.

Related jobs
Jobs that call for the skills explored in this talk.

Matching moments

Moving from manual unit testing to automated generation
01:26 MIN

Moving from manual unit testing to automated generation

Are you still programming unit tests or already generating?

Demo of automating unit test generation and validation
03:33 MIN

Demo of automating unit test generation and validation

Rethinking Workflows in the Agentic Era

Generating code from specifications with modern tooling
06:44 MIN

Generating code from specifications with modern tooling

Specifications as the better way of software development

How AI is changing test generation and maintenance
04:01 MIN

How AI is changing test generation and maintenance

The 2025 State of JavaScript Testing

Using automation as a catalyst for team collaboration
04:09 MIN

Using automation as a catalyst for team collaboration

How to add test automation to your project: The good, the bad, and the ugly

Accelerating development by generating various types of tests
03:40 MIN

Accelerating development by generating various types of tests

GitHub Copilot Beyond the Basics - 10 Ways to Elevate Your Coding

Leveraging automation as a gift for development workflows
03:58 MIN

Leveraging automation as a gift for development workflows

Unlocking Seamless Collaboration: Design-First APIs for UI Components

Why code generation was chosen for the SDK
02:07 MIN

Why code generation was chosen for the SDK

Building a Friendly Kotlin SDK to Connect to JetBrains Space

Featured Partners

Related Videos

See all videos
How not to test 43:07

How not to test

Golo Roden

How will artificial intelligence change the future of software testing?45:24

How will artificial intelligence change the future of software testing?

Evelyn Haslinger

Why you must use TDD now!30:55

Why you must use TDD now!

Alex Banul

How To Test A Ball of Mud42:34

How To Test A Ball of Mud

Ryan Latta

Continuous testing - run automated tests for every change!47:22

Continuous testing - run automated tests for every change!

Christian Kühn

Are you still programming unit tests or already generating?29:31

Are you still programming unit tests or already generating?

Johannes Bergsmann & Daniel Bauer

Contract Testing - How do you tame an external API that constantly breaks your tests26:02

Contract Testing - How do you tame an external API that constantly breaks your tests

Vincent Hennig & Anupam Krishnamurthy

Testing .NET applications a Tool box for every developer29:13

Testing .NET applications a Tool box for every developer

Alexandre Borges

Related Articles

View all articles
DC
Daniel Cranney
Why Attend a Developer Event?
Modern software engineering moves too fast for documentation alone. Attending a world-class event is about shifting from tactical execution to strategic leadership. Skill Diversification: Break out of your specific tech stack to see how the industry...
Why Attend a Developer Event?

From learning to earning

Jobs that call for the skills explored in this talk.