Why This Course?
Discover the motivation for this course and what you will learn.
We'll cover the following
The word “testing” has always been a poor fit for pragmatic unit testing. The very word makes unit testing sound like something that is separate from coding, design, and debugging.
It’s not.
Why is it important?
Our programming language compiler/interpreter can verify that our source code is syntactically valid. Essentially, it confirms that the code makes at least some sort of sense according to the language’s syntax. However, the compiler can’t tell what our code does and thus can’t help determine if the code is correct or not.
Intended audience
Unit testing lets us specify what the code does and verifies that the code does it. Unit testing has grown into an amazing intersection of design, coding, and debugging.
If we haven’t gotten massive value from our testing yet, then this course will help remedy that. Whether you’re brand-new to the ideas we will discuss here or just trying to get the most benefit from unit testing, this course will help.
Prerequisites
This course assumes an intermediate understanding of Java and a basic sense of unit testing, external dependencies, and libraries.