|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
Announcements
Chapters
Services
Feature Zones
|
Note: This is an unedited contribution. If this article is inappropriate,
needs attention or copies someone else's work without reference then please
Report This Article
IntroductionPerhaps many of you use NUnit. It's a great tool. But sometime ago I wanted to make benchmarking and then I discovered Zanebug. Since I get involved in the project, and now I want to introduce to some of the features that makes Zanebug a better alternative to NUnit. CompatibilityZanebug is compatible with NUnit, so you can work with it or Nunit at minimun effort. Just change your references. BenchmarkingZanebug introduces the Repeat attribute for methods, its works in this way: using Adapdev.UnitTest;
[TestFixture]
class TestClass
{
[Repeat(100)]
[Test]
void TestCase()
{
MethodToBenchmark();
}
}
This way your code will iterate 100 times. Zanebug will report the time elapsed and the resources used in the GUI. Method Setup and TeardownIn NUnit you have Setup, and TearDown attributes, that do initialization and termination code for the TestFixture. A nice feature of Zanebug is Method specific setups and teardowns: [TestFixture]
public class TestFixture
{
// Runs once at the beginning of SimpleTest only
[TestSetUp("SimpleTest")]
public void SpecificTestSetUp()
{
// setup code
}
// A Test
[Test]
public void SimpleTest()
{
// test code
}
// Runs once at the end of SimpleTest only
[TestTearDown("SimpleTest")]
public void SpecificTestTearDown()
{
// teardown code
}
}
This feature is very useful and I missed on NUnit. GUIThe graphical user interface of Zanebug is more friendly and has more information than NUnit.
Even, you can monitor system performance
Get ZanebugThere is a lot more on this tool, I suggest you to visit zanebug web site: www.adapdev.com/Zanebug. Sean McCormack has been doing a great job with this tool and you should try it.
|
||||||||||||||||||||||