2 Why We Need Model-Based Testing

Overview 27
// Client requests one temperature sample, server responds
[Test]
[Category("ClientServer")]
public void LogOneSample()
{
const int port = 8000;
const string host = "127.0.0.1"; // localhost
string received, command = "T"; // get temperature sample
double temperature = 212;
double response;
Client client = new Client();
Server server = new Server();
server.Socket();
server.Bind(host,port);
server.Listen();
client.Socket();
client.Connect(host,port); // Connect before Accept is OK
server.Accept(); // Accept after Connect does not block
client.Send(command);
received = server.Receive();
server.Send(temperature);
response = client.Receive();
Assert.AreEqual(command, received);
Console.WriteLine("Server sent {0,5:F1}, client received {0,5:F1}",
temperature, response);
Assert.AreEqual(temperature, response);
client.Close();
server.CloseConnection();
server.Close();
} // LogOneSample
Figure 2.10. Test method for client/server scenario.
method’s behavior. But many methods are not state-independent. This introduces
complications, as we shall now see.
2.8 A more complex scenario
We would like to write tests that exercise more of the behavior exhibited by the
applications. Our test method LogOneSample tests the smallest realistic run: the
client requests one temperature sample and the server responds (Figure 2.10).
more free ebooks download links at:
http://www.ebook-x.com