Integration testing – it’s not a choice, it’s a no-brainer!

by Jul 25, 2023

Integration testing – it’s not a choice, it’s a no-brainer!

Seems like these days I’m all about integration testing. 📝🔍

Yeah, unit tests? They’re alright but, man, do they fall apart when something changes. Brittle like a stale cookie! They got their use though, especially with complex stuff that needs untangling.🕸️

End to end tests? They’re cool. They let you see the system doing its thing, but boy, they lose me when something goes wrong. 🤷‍♂️ Drives me up the wall! Sometimes, I just let ’em be (‘oh, that one breaks all the time’) – fixing ’em is like solving a Rubik’s cube blindfolded. 🙄

Enter the unsung hero, integration tests! 🥳🍾 For me, they’re the golden ticket. They give you the best bang for your buck. They hit that sweet spot; they’re high-level enough to check if the system’s good to go, and low enough to spot what went south with a decent debug. 👀💡

So, which is your ‘go-to’ testing method, and why?

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more