Reducing Code Redundancy Between our Test Cases

Explore techniques to reduce code redundancy in NUnit unit tests by centralizing common Arrange steps in a Setup method. Understand how NUnit runs Setup before each test, enabling cleaner, more maintainable, and readable test methods focused on Act and Assert steps.

We'll cover the following...

Introduction
Demonstrating the problem
NUnit test process
Multiple setup methods
Applying setup to specific test methods
Conclusion

Introduction

Every test case requires the Arrange-Act-Assert steps. Most of the time, arranging data is the same between test methods. If this is the case, you will need to set up your test methods. Test method setup is the process of arranging data once so it may subsequently be used by various test methods.

Demonstrating the problem

Suppose you have an application code that contains a class called HundredMeterSprint. This class stores a list of sprint competitor times. These values represent the time taken to complete a hundred-meter sprint by various athletes. The class has the three following public methods:

AverageTime(line 17):

...

1.Fundamentals of Unit Testing

2.Testing Conditions With Classic And Fluent Assertions

3.Making Unit Testing More Effective

4.Unit Testing Code with External Dependencies

5.Conclusion

6.Appendix - Unit Test Project Organization and Console Setup

Reducing Code Redundancy Between our Test Cases

Introduction

Demonstrating the problem