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 this project, you will write a unit test that tests the behavior of a class that models banking transactions. To frame your state of thinking in designing the unit tests, we’ve provided an assessment rubric.  It will help indicate whether the principles that were taught in this section have been considered and applied.

# Self assessment rubric

| **I have...**  |**Emergent**   | **Satisfactory**| **Excellent**   |
| - | - | - | - |
|**Excluded control logic in my tests**   | There was extensive use of control logic in tests. | There was limited use of control logic in tests.  |There was no use of control logic in tests.   |
|  |  |  |  |
|**Chosen a concise and consistent naming convention**   | Inconsistent, verbose, and non-descriptive naming was used.  | A somewhat concise and consistent naming convention was used.  | A concise and fully consistent naming convention was used.  |
|  |  |  |  |
|**Ensured maximum test coverage**   | Not all methods were covered/tested. | All methods were covered/tested but some didn't test all possible inputs.|  All methods and all input behavior was tested.  |
|  |  |  |  |
|**Limited my tests to non-trivial code**   | Test cases were developed for all trivial code.  | Some test cases were developed for trivial code.  | No test cases were developed for trivial code.  |Structured my tests according to the AAA principle.
|  |  |  |  |
|**Striven for one assertion per test**   |All test cases have more than one assertion.   |Some test cases have more than one assertion.   | Each test case has one assertion.  | | 
| **Utilized code coverage tools**   |No code coverage exercise was performed.| Code coverage was performed. In the event, branch coverage was shown to be below 100%, no corrective action was taken.   | Tests were checked with a code coverage tool and had a 100% branch coverage.

# Project code

In your own environment, copy the following application code and write unit tests that fully test this application code. You may also use the widget below to write and run your tests:



Apply what you have learnt about the foundations of unit testing by completing the project in this lesson.

Challenge: Test Using Best Practices

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

Challenge: Test Using Best Practices

Introduction

Self assessment rubric