Code Squid

Unit Testing

On my first developer job, I wasn't given the time to write Unit Tests. In fact, in 6 years I wrote a grand total of three (3) Unit Tests. We had no manual or automated tests either.

My supervisor would test the code on his computer, then merge the code straight to production ... often, with disastrous results.

I learned to be fearful of code moving to production.

Then, on my next job I was told we "do the right thing, not the right now thing."

At the first client, I tested this Core Value. I was able to not only have coverage, but overlapping coverage that included tests to ensure that any defects found were covered.

For 180k lines of code, I had 2,800 Unit Tests.

This code went to production. Over the first year, we had three (3) defects reported ... and, two of those were missed requirements.

This success sold me on Unit Tests. I am a strong proponent of having a solid set of tests for any code.

I've never had a lot of tests cause any problems. In fact, the prove stability and ensure timely development of solid code.

Because of this, the first course I developed for Code Squid was React Unit Testing: https://code-squid.com/p/unit-tests-react

Two sections of this course are open to be previewed.

Please come and see if this course is for you!

Unit Tests - React Learn to confidently write Unit Tests for React