Stop Mocking Everything: A Practical Guide to Integration Testing | Matt Wicks

📞 Contact us: https://bit.ly/4fAFrVx

In this interview from NDC Sydney, Matt Wicks chats with Jimmy Bogard about what integration tests should really look like in modern .NET applications. They unpack the difference between fast tests, slow tests, and really slow tests, and explain why true integration tests should focus on real dependencies rather than brittle mocks or heavily abstracted code. Jimmy shares lessons from long-running client projects, including how teams moved from slow, sequential test suites to fast parallel execution by writing tests with fewer hidden assumptions. The discussion covers database cleanup strategies, why mocking databases often leads to false confidence, when unit tests are still valuable, and how overusing patterns like repositories and unit of work can actually get in the way. They also explore how tools like Test containers, Respawn, and .NET Aspire fit into the picture, plus where AI may help developers in future. If you want practical advice for writing reliable, maintainable tests that reflect real-world behavior, this conversation is packed with insights.

00:00 | Introduction to integration testing at NDC Sydney
02:00 | Why brittle unit tests pushed teams toward integration tests
04:03 | Parallel test execution and cutting suite times dramatically
06:03 | Hidden test assumptions that break parallelization
08:00 | Structuring tests and framework trade-offs
10:06 | Why mocking databases leads to false positives
12:02 | Rethinking the testing pyramid and when unit tests matter
14:01 | Repositories, unit of work, and avoiding unnecessary abstractions
18:03 | Testcontainers, real dependencies, and cloud-friendly setups
23:01 | .NET Aspire, orchestration, and the future of integration testing

🌐 About SSW: https://linktr.ee/SSWTV

🔗 Links:
LinkedIn:   / ssw
Twitter:   / ssw_tv
Facebook:   / ssw.page
Instagram:   / ssw_tv
Tiktok:   / ssw_tv

👋 Get in touch:
Get in touch:
Matt Wicks – SSW Solution Architect
About: https://www.ssw.com.au/people/matt-wi…

#dotnet #integrationtesting #unittesting #softwarearchitecture #cleanarchitecture #testautomation #testcontainers #aspire #devops #jimmybogard #ndcsydney #sswtv

V1 – Bahjat

About the speakers

Matt is an elite SSW Solution Architect who runs the Newcastle office. Matt stands out in the tech landscape as a certified Scrum Master, an Octopus Insider, and is GitHub accredited. From the early days when .NET 2 was still in beta, Matt has been capitalizing on the full potential of the Microsoft stack, coding his way to ingenious solutions that deliver significant business value.

Microsoft Teams Etiquette: Simple Habits That Make Meetings Better | Adam Cogan

Whether you’re working remotely or in the office, small habits can make a huge difference in Microsoft Teams meetings. In this video, Adam Cogan shares practical etiquette tips to help meetings run more smoothly—from introducing people who join the room, to announcing yourself when joining a call, using screen sharing respectfully, and ending meetings with a recorded summary that can automatically create a Product Backlog Item (PBI).

These simple communication habits improve collaboration, reduce confusion, and make hybrid meetings more inclusive and productive.

Treat Your Code Like Uranium | Adam Cogan

Adam Cogan shares a striking story comparing two World War II factories—one ordinary, one handling uranium—and the surprising lesson that the uranium workers lived longer because they followed disciplined, risk-aware practices. He connects that idea to software teams: the best outcomes come from careful habits like automated tests, telemetry, pull requests, retrospectives, shared rules, and good tools. The message is simple: treat software delivery with the same respect as dangerous work, and you’ll reduce stress, avoid chaos, and get better results.

3 Tips for Better Video Recordings | Adam Cogan

Great coaching can dramatically improve how you present, communicate, and learn. In this video, Adam Cogan shares 3 practical coaching tips that SSW uses every day—from onboarding and role plays to improving video delivery. He explains why having a coach matters, why immediate interruption beats delayed feedback, and how repeating corrections helps lock in better habits.

TinaCMS + Fumadocs: Bring Visual Editing to Your Docs | Hark Singh

Discover how to connect Playwright with AI agents and unlock powerful workflows.

Stop Using 👍 Wrong in Teams | Adam Cogan

A quick communication tip from Adam Cogan: don’t use 👍 as a catch-all response when someone assigns you a task in Teams, Slack, or Google Chat. In the example Adam gives, if a task will take about five minutes, a thumbs up is too ambiguous because it does not clearly say whether you’ve read it, agree with it, are doing it now, or will do it later. Instead, use 👍 for agreement, 👀 to show you’ve seen the task and are actively working on it, and then replace 👀 with ✅ once the task is done. It is a small change, but it removes ambiguity and cuts down unnecessary follow-up messages.

How to record a done video in SSW | Sylvia Huang | SSW Rules

Sylvia Huang from SSW shares her SSW Cultural Exchange experience from Hangzhou, China to Australia

4 Essential Sales Tips for Engineers | Adam Cogan

Not a salesman? No problem. Adam Cogan shares 4 practical tips to help engineers navigate sales meetings with confidence. Learn how to stop “selling” and start solving, how to talk numbers without the awkwardness, and why being transparent about your process wins more clients.

Do you explain why you’ve deleted or updated an appointment? | Adam Cogan | SSW Rules

Ever wonder why a meeting was moved or cancelled? Adam Cogan explains the “Secret Ingredient” to professional scheduling: always include a version history and reason for change at the top of your appointments. Improve clarity, keep a record of changes, and hold participants accountable with this simple SSW Rule.

Chat first before changing others’ code | Adam Cogan

Changing someone else’s code? Don’t just dive in! Adam explains why it’s important to check the source history and talk to the original developer before making changes. A quick chat can save headaches and keep everyone on the same page. Perfect advice for devs working in teams!