Upcoming Event
Why Should Developers Automate?
onlineautomationtestingdotnetqamicroservicesunit-testingfunctional-testingclean-architectureevent-driven
🏢By: InnoIT•Event: InnoIT Tech Talks 2025
📅 May 7, 2025
- 🕒 🇺🇸 Eastern Time (ET) — 12:30 PM
- 🕒 🇺🇸 Central Time (CT) — 11:30 AM
- 🕒 🇪🇸 Spain (CEST) — 06:30 PM
- 🕒 🇦🇷 Argentina (ART) — 01:30 PM
Back to Talks
Event Details
📍
Location
Online - Spain
Barcelona, Spain
🌐
Language
English
🏢
Event
InnoIT Tech Talks 2025
📅
Date & Time
May 7, 2025 — Shown above in your local time zones 👆
Coming soon!
🏷️
Format & Topics
online
automationtestingdotnetqamicroservicesunit-testingfunctional-testingclean-architectureevent-driven
About this Talk
Real-world examples show how spending just one extra hour automating tests after a feature can save days of bugs, frustration, and lost money later.
This session dives into a .NET microservice, but the concepts apply across architectures — monoliths, desktop apps, and more. (Code is in C#, but the ideas work in any language.)
It explores how developers can write E2E automated tests🤖 to validate APIs and event-driven workflows using real infrastructure. The setup spins up a microservice with Docker 🐳, connects it to a test project that runs inserts, updates, deletes, and verifies HTTP status codes, database states, and event bus triggers.
This developer🧑💻-focused automation complements QA processes, catching bugs earlier, boosting confidence, and reducing back-and-forth in the delivery cycle.
The result is faster⏱️ delivery🚀, fewer misunderstandings😵 between Dev and QA, and major cost savings 💸💸 by detecting issues before they reach production.
A real-world solution with working code, real infrastructure, and a practical model for testing integrated systems early and effectively.
This session dives into a .NET microservice, but the concepts apply across architectures — monoliths, desktop apps, and more. (Code is in C#, but the ideas work in any language.)
It explores how developers can write E2E automated tests🤖 to validate APIs and event-driven workflows using real infrastructure. The setup spins up a microservice with Docker 🐳, connects it to a test project that runs inserts, updates, deletes, and verifies HTTP status codes, database states, and event bus triggers.
This developer🧑💻-focused automation complements QA processes, catching bugs earlier, boosting confidence, and reducing back-and-forth in the delivery cycle.
The result is faster⏱️ delivery🚀, fewer misunderstandings😵 between Dev and QA, and major cost savings 💸💸 by detecting issues before they reach production.
A real-world solution with working code, real infrastructure, and a practical model for testing integrated systems early and effectively.
