2 Why We Need Model-Based Testing

20 Why We Need Model-Based Testing
namespace ClientServerImpl
{
// Temperature sensor simulator
}
public class Temperature
{
static int i = 0; // index for cycling through simulated data
static double[] temperature = { 71.2, 71.3, 71.4 }; // simulated data
}
// Simulate acquiring sample from sensor, substitute for real sensor
public double Sample()
{
return temperature[i++ % temperature.Length]; // cycle through data
}
public static double ConvertToCelsius(double temperature)
{
return 5*(temperature - 32.0)/9;
}
Figure 2.6. Remote instrument temperature sensor class.
Each of our source files begins with the namespace declaration:
namespace ClientServerImpl
Every class (or other type) has a fully qualified name formed from the simple
name that appears in its declaration and the namespace where it is declared. For
example, Server is a simple name; the fully qualified name of our server class
is ClientServerImpl.Server. Namespaces and fully qualified names make it possible
to avoid name conflicts where other programs use the same simple names
(Server, etc.). The namespace declaration is optional but should be used in code
that you expect will be integrated into a larger system. The using statements identify
the namespaces of other types used in the source program, so we can use their
simple names (such as Socket) rather than their fully qualified names (such as
System.Net.Sockets.Socket). During development, it is typical (but not required)
to put files that declare different namespaces in different directories. This makes it
possible to use the (short) simple names also as file names, without fear of creating
file name conflicts.
2.5 Applications
Our two application programs Monitor and Logger (Figures 2.7 and 2.8) each contain
a main method that calls methods in our libraries. The applications provide the
more free ebooks download links at:
http://www.ebook-x.com