Past Event
Why Should Developers Automate?
onlineautomationtestingdotnetqamicroservicesunit-testingfunctional-testingclean-architectureevent-driven
🏢By: Power Platform Bootcamp Buenos Aires•Event: Global Power Platform Bootcamp Buenos Aires 2025
📅 February 21, 2025
- 🕒 🇺🇸 Eastern Time (ET) — 10:50 AM
- 🕒 🇺🇸 Central Time (CT) — 09:50 AM
- 🕒 🇪🇸 Spain (CEST) — 04:50 PM
- 🕒 🇦🇷 Argentina (ART) — 12:50 PM
Back to Talks
Event Details
📍
Location
Online - Argentina
Buenos Aires, Argentina
🌐
Language
Spanish
🏢
Event
Global Power Platform Bootcamp Buenos Aires 2025
📅
Date & Time
May 7, 2025 — Shown above in your local time zones 👆
This event has already taken place.
🏷️
Format & Topics
online
automationtestingdotnetqamicroservicesunit-testingfunctional-testingclean-architectureevent-driven
About this Talk
In this talk 🗣️, we explore how developers can write E2E automated tests🤖 in their own language to validate APIs and event-driven workflows using real infrastructure.
We gonna spin up a microservice with Docker 🐳, connect it to a test project that runs inserts, updates, deletes, and checks responses (HTTP status codes, database state, and event bus triggers). Although we use a microservice example, this strategy applies to any type of system🤝.
This developer🧑💻 focused automation doesn’t replace QA, this complements it. While QA teams may use other tools for automation, these early-stage checks help catch bugs sooner, improve developer confidence, and reduce back and forth in the delivery cycle.
The result? Faster⏱️ delivery🚀, fewer misunderstandings😵 between Dev and QA, and significant cost savings 💸💸 by catching issues before they hit production.
So it's a real-world solution, not a theoretical talk with working code, infrastructure, and a model for testing integrated systems early and effectively.
We gonna spin up a microservice with Docker 🐳, connect it to a test project that runs inserts, updates, deletes, and checks responses (HTTP status codes, database state, and event bus triggers). Although we use a microservice example, this strategy applies to any type of system🤝.
This developer🧑💻 focused automation doesn’t replace QA, this complements it. While QA teams may use other tools for automation, these early-stage checks help catch bugs sooner, improve developer confidence, and reduce back and forth in the delivery cycle.
The result? Faster⏱️ delivery🚀, fewer misunderstandings😵 between Dev and QA, and significant cost savings 💸💸 by catching issues before they hit production.
So it's a real-world solution, not a theoretical talk with working code, infrastructure, and a model for testing integrated systems early and effectively.
