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

This lesson focuses on how a project directory’s structure and its contents are changed when a unit test project is added, along with descriptions of what the changes mean. This lesson does not provide an overview on how to set up a unit test project as this is covered in other lessons. We’ll look at what happens under the hood when a test project is created either through using an IDE or using the console.

The lesson will also provide an overview of the best practices for the test code project structure.

## Files generated upon the unit test project creation

Suppose you add a unit test project to your existing project containing the application code. The directory’s structure looks as follows:

```
/Solution/
    Solution.sln
    /ProjectApplication/
        Source Files
        ProjectApplication.csproj
    /ProjectTest/
        Source File
        ProjectTest.csproj
```

The creation of an NUnit project generates an empty source file for you to include your tests as well as a `ProjectTest.csproj` file. The `ProjectTest.csproj` file includes the following:


# Introduction

This lesson focuses on how a project directory’s structure and its contents are changed when a unit test project is added, along with descriptions of what the changes mean. This lesson does not provide an overview on how to set up a unit test project as this is covered in other lessons. We’ll look at what happens under the hood when a test project is created either through using an IDE or using the console.

The lesson will also provide an overview of the best practices for the test code project structure.

# Files generated upon the unit test project creation

Suppose you add a unit test project to your existing project containing the application code. The directory’s structure looks as follows:

```
/Solution/
    Solution.sln
    /ProjectApplication/
        Source Files
        ProjectApplication.csproj
    /ProjectTest/
        Source File
        ProjectTest.csproj
```

The creation of an NUnit project generates an empty source file for you to include your tests as well as a `ProjectTest.csproj` file. The `ProjectTest.csproj` file includes the following:


Learn how NUnit alters your existing project and learn to layout your application and test code.

Unit Test Project Structure

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

Unit Test Project Structure

Introduction

Files generated upon the unit test project creation