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

Software code is split into two parts--- application code implements the actual software features and test code includes the tests that test the behavior of the application code. There are two ways to approach writing test code. One involves writing test code after application code, known as the test after development approach. This approach is the most natural and the one which all newcomers to testing will tend to perform at first.

Another testing approach entails writing tests before writing the application code. This is known as the test-driven development approach.

## Test-driven development

**Test-driven development (TDD)** entails writing test code before the application code, as shown in the figure below:


# Introduction

Software code is split into two parts--- application code implements the actual software features and test code includes the tests that test the behavior of the application code. There are two ways to approach writing test code. One involves writing test code after application code, known as the test after development approach. This approach is the most natural and the one which all newcomers to testing will tend to perform at first.

Another testing approach entails writing tests before writing the application code. This is known as the test-driven development approach.

# Test-driven development

**Test-driven development (TDD)** entails writing test code before the application code, as shown in the figure below:


Learn the test-driven development approach and the benefits it brings to your development process.

Test-Driven Development

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

Test-Driven Development

Introduction

Test-driven development