In a real-world solution, you might have separate projects for tests and source. Make a new C# class library project targeting '.Net Framework.' Name it NCrunch.UnitTestDebugging. With a formula like that, what can possibly go wrong? Let's put the code together and see what we come up with. Here's the formula for calculating FVA: FVA = CF * (((1 + i)^n-1)/i)

The code won't work perfectly, and we'll have to figure out why. Once we've written the tests, we'll start writing the code. We'll use xUnit to write data-driven unit tests.ģ. We'll need to test a few conditions against expected values the execution of the function is the same for each case.

Your account will grow to FVA (future value of annuity) after n years.Ģ. You invest CF ( cash flow ) dollars per year and earn i interest each year, compounded annually. Your retirement account is one kind of annuity. We'll unit test a method that computes the future value of an annuity. Doing is learning, after all! Here's the gist of what we're going to do:ġ. Please, feel free to copy this source code locally. I'm going to build out an example so you can follow along. Let's start by setting up an example and walking through it.

You can debug a unit test in Visual Studio by following this simple guide. So you've got to debug the unit test.Īs you'll see in this post, debugging unit tests isn't so different from debugging any code. The next day, you've got failing tests like the ones described in Peter Morlion's post, only you don't know why. But let's be honest, it happens! One day you're humming along nicely with your tests. Given that one goal of test-driven development (TDD) is never to touch a debugger, it seems like an oxymoron to debug a unit test.

Visual studio code c++ unit test