Finding whether the NUnit GUI already reloaded the assembly

20 Jun 2011 1 mins NUnit, Test Driven Development (TDD)

When I’m fixing bugs found by unit tests it’s quick process – run test, spot the problem, fix it, build, run again. The problem is, that often, during the build I switch to other window and then to NUnit GUI. And then I don’t know whether the assembly with tests was already reloaded (and hence contains the fix) or not. So I often reloaded it again, just to be sure a.k.a wasting time.

But today I found a way to distinguish that. When the tests are done, the progress bar is at 100% (and has some color based on result of the test run). After (automatic) reloading, the progress bar is at 0% (so no color).

Easy, isn’t it?

Jiří Činčura is .NET, C# and Firebird expert. He focuses on data and business layers, language constructs, parallelism, databases and performance. For almost two decades he contributes to open-source, i.e. FirebirdClient. He works as a senior software engineer for Microsoft. Frequent speaker and blogger at www.tabsoverspaces.com.