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

The Application code can contain millions of lines of code. Furthermore, the application code uses .NET and other libraries. Not using these libraries may significantly increase the application code size. Let’s also suppose that the application code contains numerous critical classes that are simple in design. Furthermore, the application code partly contains an interface and implementation between the classes. Not all these sections of code require testing. We’ll explore which sections require testing and which don’t.

## Classes and methods that don't require testing

The entire application codebase should be unit tested except for certain categories. These are detailed below.

### Libraries

Library classes do not require testing. For instance, there is no practical value in testing the `ToUpper` method of the `string` class:



# Introduction

The Application code can contain millions of lines of code. Furthermore, the application code uses .NET and other libraries. Not using these libraries may significantly increase the application code size. Let’s also suppose that the application code contains numerous critical classes that are simple in design. Furthermore, the application code partly contains an interface and implementation between the classes. Not all these sections of code require testing. We’ll explore which sections require testing and which don’t.

# Classes and methods that don't require testing

The entire application codebase should be unit tested except for certain categories. These are detailed below.

## Libraries

Library classes do not require testing. For instance, there is no practical value in testing the `ToUpper` method of the `string` class:



Distinguish areas of code that require testing from areas that don't.

Identifying the Application Code to Test

Identifying Application Code to Test

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

Identifying Application Code to Test

Introduction

Classes and methods that don’t require testing

Libraries