2 Why We Need Model-Based Testing

144 Testing Closed Systems
}
}
}
}
// ... continued
case("ClientSocket"):
c.Socket(); return null;
case("ClientConnect"):
c.Connect(host,port); return null;
case("ClientSend"):
c.Send("T"); return null;
case("ClientReceive_Start"):
// c.Receive returns a double, not a string
return Action.Create("ClientReceive_Finish", c.Receive());
case("ClientClose"):
c.Close(); return null;
default: throw new Exception("Unexpected action " + action);
public void Reset()
{
s = new Server();
c = new Client();
}
// Factory method
public static IStepper Create()
{
return new Stepper();
}
Figure 8.5. Client/server: test harness (stepper) (2).
The DoAction method is the core of the test harness. It invokes the implementation’s
controllable actions, monitors the implemenation’s observable actions, collects
the output from the implementation, and checks the implementation against
the model.
To invoke each controllable action, the test runner passes DoAction a term that
represents the action. There is a case in DoAction for each action symbol. The code
in the case branch invokes the corresponding method in the implementation. In the
simple case where the action has no outputs, DoAction returns null.
more free ebooks download links at:
http://www.ebook-x.com