In a previous article, I weighted the pros and cons of writing our unit tests in Typescript (TS) when working on a TS project. In this article, I want to explain how to overcome the challenges of debugging TS unit tests, i.e. hitting a breakpoint in our TS code while executing a test.
The problem statement therefore is: How do we hit a breakpoint in a TS unit test while debugging our code?
In this article, I will contrast and compare two different approaches to writing your unit tests:
I am a professional in the Tech Industry; a software developer to be more precise. In the 9 years of my career, continuous learning has been a constant throughout.
The Tech Industry has a fast-developing ecosystem. For example, Kotlin came out of seemingly nowhere, and suddenly became the recommended language for developing Android applications; first-class support for Kotlin was announced at Google I/O 2017.
Soon after, in 2018, Google launched Android Jetpack. Within a time lapse of just over a year: