2 Why We Need Model-Based Testing

146 Testing Closed Systems
Compile the stepper to a library. Reference the implementation in the compilation:
csc /t:library /out:Stepper.dll ˆ
/r:Server.dll /r:Client.dll ˆ
/r:"%DEVPATH%\NModel.dll" ˆ
Stepper.cs
8.4 Test execution
To execute a test suite, invoke the test runner tool ct, naming the stepper and the test
suite. You do not need to name the model program; all of the information needed
from the model program is already represented in the test suite. This command
executes the test suite generated from the contract model program (Figure 8.1). 3
ct /r:Stepper.dll
/iut:ClientServerImpl.Stepper.Create /testSuite:ContractTest.txt
When we execute this command, all of the tests succeed:
TestResult(0, Verdict("Success"), "",
Trace(
Test(0),
ServerSocket(),
... etc.
ClientClose()
)
...
... etc.
...
TestResult(5, Verdict("Success"), "",
...
)
)
Next we execute the test suite generated from the client/server contract model
program composed with the scenario machine (Figure 8.2):
ct /r:Stepper.dll /iut:ClientServerImpl.Stepper.Create ˆ
/testSuite:ScenarioTest.txt
3 A complete command reference for ct appears in Appendix B.3.
more free ebooks download links at:
http://www.ebook-x.com