2 Why We Need Model-Based Testing

24 Why We Need Model-Based Testing
using System;
using NUnit.Framework;
namespace ClientServerImpl
{
// Test fixture for remote instrument Server, Client, Temperature classes
[TestFixture]
public class Tests
{
#region [SetUp], [TearDown] methods (code not shown)
// Check Fahrenheit to Celsius conversion, one data point
[Test]
[Category("Convert")]
public void Convert32()
{
Assert.AreEqual(Temperature.ConvertToCelsius(32), 0);
}
// Check Fahrenheit to Celsius conversion, several data points
[Test]
[Category("Convert")]
public void ConvertMany()
{
Assert.AreEqual(Temperature.ConvertToCelsius(32), 0);
Assert.AreEqual(Temperature.ConvertToCelsius(98.6), 37);
Assert.AreEqual(Temperature.ConvertToCelsius(212), 100);
Assert.AreEqual(Temperature.ConvertToCelsius(212), 101); //Fail!
}
#region Other tests (code not shown)
}
}
Figure 2.9. Test fixture with test methods.
To write unit tests for NUnit, code a test fixture class that has test methods. Label
them with the NUnit [TestFixture] and [Test] attributes, respectively. Each test
method encodes a single test that can pass or fail; it calls a method (or methods) in
the IUT (the library or libraries under test) and checks the results. Call an NUnit
assertion, such as Assert.AreEqual, to check the results of each test. Our Tests
class is an NUnit test fixture for testing our remote instrument libraries (Figure 2.9).
Attributes supply programmer-defined information about a type or member that
is stored in the assembly, where it can be retrieved by another program. The
[TestFixture] and [Test] attributes defined in the NUnit library are used by the
NUnit test runner applications to identify the test classes and test methods in an
more free ebooks download links at:
http://www.ebook-x.com