In the realm of software development, unit testing has long been regarded as a vital practice for ensuring the quality and reliability of code. However, in a thought-provoking YouTube video titled “Unlearn Unit Testing”, Lemi Orhan Engin challenges some of the prevailing beliefs about unit testing. (The video is Turkish but an English subtitle is available 😃) He shares his personal experience, highlighting the pitfalls of excessive reliance on unit testing and shedding light on a more practical and efficient approach to testing software.

This article delves into the key takeaways from the video, providing valuable insights for developers seeking to optimize their testing strategies.

The Importance of Code and Testing Integration:

Lemi Orhan begins by recounting his earlier belief that every line of code should be tested, striving for the coveted 100% code coverage. However, he soon discovered that such an approach failed to uncover functional issues during deployment, leading to a critical realization. Code and testing are inherently intertwined, and separating them can undermine the effectiveness of the testing process. He emphasizes that testing is not merely an afterthought or a validation exercise; rather, it is an integral part of the design process, ensuring that code works as expected.

The software design is not complete until it has been coded and tested.

Testing is a fundamental part of the design validation and refinement process. -Jack W. Reeves

Clarifying Misconceptions about Unit Testing:

Unit testing, as Lemi Orhan explains, is not about trying to test every minute detail of an application or obsessively isolating every component for mocking. Instead, it serves as a means to design and improve code by systematically testing individual components in isolation. He dispels the notion that unit testing should make code unchangeable or unserviceable. In fact, well-designed code should become more robust and easier to test. Integration testing also plays a crucial role in validating the functionality of the entire system and business workflows.

Moving Beyond Traditional Testing:

Lemi Orhan argues that relying solely on traditional testing approaches, including unit and integration testing, is inherently flawed. While these methods have their merits, they often fall short of guaranteeing that an application will work as expected in all scenarios. Instead, he suggests focusing on user stories and their requirements to gain a clearer understanding of the application’s intended behavior. By adopting a behavioral standpoint, developers can craft tests that encompass the full range of expected outcomes and alternative behaviors.

Effective Isolation and Testing Strategies:

To facilitate effective testing, Lemi Orhan recommends isolating different parts of an application and testing them individually. This can be achieved by utilizing adapters to separate system components and employing fake implementations to test isolated sections. While test doubles like mocks and spies have their place, he advises against overusing or misusing them. He emphasizes the importance of writing tests for every entry and exit point in the application, ensuring comprehensive coverage.

Shifting Focus to Functional Testing:

Lemi Orhan suggests that unit testing should transcend individual classes or methods and instead focus on testing the flow of the business process. Integration testing, he argues, can be effectively replaced with functional testing, which allows developers to test different functionalities using mock frameworks. By adopting this approach, developers can achieve 80% code coverage or higher without relying extensively on integration testing. However, he acknowledges that in some cases, concrete testing may still be necessary for specific areas that require integration testing.

Conclusion

In the “Unlearn Unit Testing” video, Lemi Orhan Engin challenges conventional beliefs about unit testing and proposes a more effective approach to software testing. By integrating code and testing, clarifying misconceptions, focusing on user stories, employing effective isolation techniques, and embracing functional testing, developers can enhance the reliability and quality of their applications. Lemi Orhan’s insights encourage a shift in mindset, promoting a more pragmatic and comprehensive approach to testing that aligns with the dynamic nature of modern software development.

You can check his project in terms of unit and integration testing and how they are implemented.

Resource:

https://www.youtube.com/watch?v=pjx06exON7g