Mocks and testability

Most of the times, when we develop software, we rely on third party services to accomplish a certain outcome so that we don’t have to re-invent the wheel. However, this introduces a new level of complexity, especially around testability.

This post is based on a presentation I gave at the “Ministry of testing - Auckland” meetup. Mocking isn’t new, and there are lots of articles on the internet about it, but it is less frequent to see content about mocks in the context of a system testing or end to end testing. Hence, I am grateful for the opportunity to share my learnings about the topic.




Software engineer (JS | REACT | Node | AWS | Test Automation)

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

GCC vs. Clang/LLVM: An In-Depth Comparison of C/C++ Compilers

Kubernetes pods, It's all you know about.

Easing the access to Blockchain applications

Solution architecture diagram

GALAXY — Introduction

Operating Systems!

Information Theory’s application [in my world]

Prototype Design Pattern

Running Fish Shell in Arch Linux with WSL 2 and the new Windows Terminal

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ali Haydar

Ali Haydar

Software engineer (JS | REACT | Node | AWS | Test Automation)

More from Medium

Rage against the [HR] Machine

The Digital Divide

CS373 Spring 2022: Varun Nayak

You Need A COVID Contract