Gain insights into unit testing principles, and delve into configuring and using NUnit. Discover how to write effective tests, maximize coverage, and elevate your testing projects.

Dockerfile.tar.gz

Iteration1

Iteration2

AssertTrueExample

AssertTrueExercise

AssertNullExample

AssertNullExercise

GeneralJob

WebAppWithoutTest

MSTest

XUnit

ConsoleWithoutTest

GeneralJobFIX

WebAppWithoutTestFIX

WebAppWithoutTestNIAZ

NiazSolution

Industry, employers, startups, and amateur developers are increasingly looking towards unit testing their software. Unit testing is one of the most reliable ways to find and keep software bugs at bay, thus reducing costs and development pains. Developers working with the .NET framework are overwhelmingly turning to NUnit to meet their unit testing needs.

In this course, you’ll learn the principles of unit testing, and in the process, learn to configure and use the NUnit testing framework. Given that the course places an emphasis on principles, these skills are transferable to other unit testing frameworks. Alongside these, you’ll also get hands-on experience with projects and exercises that provide ample opportunities to learn how to design effective tests in the NUnit framework.

At the end of the course, you’ll be able to quickly write unit tests that maximize logical coverage, test complex applications, and better organize your testing projects—setting you up as a natural leader in your organization.

Mastering Unit Testing Principles with NUnit

## Introduction

In his book, _Working Effectively with Legacy Code_, Michael Feathers says "The adage, if it ain't broke, don't fix it doesn't necessarily apply in the case of technology. Projects continually require alterations, updates, and enhancements."

Whenever a change is made in code, it may break existing functionality. ​​If these changes result in breaking existing functionality or in degrading the quality of the code, the code undergoes software regression. **Software regression** is a type of software bug where a feature that has worked before stops working. These bugs happen through changing existing code and typically, the developer misses these bugs.

## Code change rationale

If there is a probability that software regression occurs after a change is made, the natural question then is: why change the software? In reality, software always changes, even software that has reached a very high level of maturity. This concept is illustrated below:


# Introduction

In his book, _Working Effectively with Legacy Code_, Michael Feathers says "The adage, if it ain't broke, don't fix it doesn't necessarily apply in the case of technology. Projects continually require alterations, updates, and enhancements."

Whenever a change is made in code, it may break existing functionality. ​​If these changes result in breaking existing functionality or in degrading the quality of the code, the code undergoes software regression. **Software regression** is a type of software bug where a feature that has worked before stops working. These bugs happen through changing existing code and typically, the developer misses these bugs.

# Code change rationale

If there is a probability that software regression occurs after a change is made, the natural question then is: why change the software? In reality, software always changes, even software that has reached a very high level of maturity. This concept is illustrated below:


Learn the dangers of software regression and interact with sample code to know how a software regression bug is introduced.

Fundamentals of Unit Testing

Testing Conditions With Classic And Fluent Assertions

Making Unit Testing More Effective

Unit Testing Code with External Dependencies

Conclusion

Appendix - Unit Test Project Organization and Console Setup

The Perils of Software Regression

Introduction

Code change rationale