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

Throwing exceptions is a way for a method to tell its caller that it has operated outside normal operating parameters. Normal and exceptional operations are defined by the method and its API documentation. Application code consists of code that runs without raising exceptions as well as code that raises exceptions during execution. Ideally, test cases for both should be written.

## Normal and exception test case development

Normal and exception test cases are both written using asserts. When writing test cases, it is convenient to first define normal test cases followed by exception test cases.

**Normal test cases** are test cases that test for behavior that does not throw exceptions.

**Exception test cases** are test cases that test for scenarios where exceptions are thrown.

## NUnit exception asserts

The following syntax is used to test for exceptions:



# Introduction

Throwing exceptions is a way for a method to tell its caller that it has operated outside normal operating parameters. Normal and exceptional operations are defined by the method and its API documentation. Application code consists of code that runs without raising exceptions as well as code that raises exceptions during execution. Ideally, test cases for both should be written.

# Normal and exception test case development

Normal and exception test cases are both written using asserts. When writing test cases, it is convenient to first define normal test cases followed by exception test cases.

**Normal test cases** are test cases that test for behavior that does not throw exceptions.

**Exception test cases** are test cases that test for scenarios where exceptions are thrown.

# NUnit exception asserts

The following syntax is used to test for exceptions:



Find out how to assert exceptions within the application code.

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

Asserting Exceptions

Introduction

Normal and exception test case development

NUnit exception asserts