Best approaches for testing

Every company has its way of testing software. Whether it’s manually or automated, it’s a requirement for developers. Developers are becoming more than just people who type code. We’re required to design, write, test, debug, document, build, and deploy software.

Automating tests using a CI/CD approach is where companies can save time and provide consistent stability and quality when releasing software to the public.

In this section, we’ll cover the standards of why testing is important, how to avoid the 100% test coverage myth, what AAA is and why it’s a great approach for unit tests, how to avoid writing a unit test library, large unit tests, and unnecessary mocks. We’ll also learn about why tests have the added benefit of documentation, how to identify slow integration tests, when to write a unit test, and how to avoid testing .NET code.

Why do we write tests?

While some believe testing starts with...