Get tested
It's important to get checked out by your doctor on a regular basis. It's just a best practice of life. However, when it comes to writing code, we need to account for many quirks and cover many different avenues of what needs to be tested. There are ways to streamline the process and make our tests more efficient. With that in mind, let's get going!
Helping hands
A good idea to keep you sane while writing test coverage is to create a helper class for yourself that will allow you to quickly insert your test data with the minimum or common fields that should be populated. An example of such a class is shown in the following code. Note that we don't actually insert the record in these methods; this is so that additional fields can be set or modified in the test method using the record before inserting them. This is useful if you are testing a specific attribute of a trigger, validation rule, or workflow. There is a method for each of the sObjects we interact with in our code from Chapter...
