2 Why We Need Model-Based Testing

Systems with Complex State 209
# factory method of the stepper
/iut:BagImpl.Stepper.Create
# number of steps and runs
/runs:1 /steps:20
We can now execute ct @args.txt in a directory that contains the referenced
libraries and get the following output:
reward: 1 actions: Set(Count_Start(), Add("b"), Lookup_Start("b"),
Lookup_Start(""), Add(""), Delete(""), Delete("b"))
reward: 1 actions: Set(Count_Start(), Add("b"), Add(""), Delete(""),
Delete("b"))
reward: 1 actions: Set(Count_Start(), Delete(""), Delete("b"))
reward: 1 actions: Set(Delete(""), Delete("b"))
reward: 0.5 actions: Set(Count_Start(), Add("b"),
Lookup_Start("b"), Lookup_Start(""), Add(""), Delete(""), Delete("b"))
reward: 0.5 actions: Set(Count_Start(), Add("b"), Add(""), Delete(""),
Delete("b"))
reward: 0.5 actions: Set(Count_Start(), Add("b"), Add(""))
TestResult(0, Verdict("Failure"),
"Action ’Count_Finish(-1)’ not enabled in the model
Unexpected return value of finish action, expected: Count_Finish(0)
Unexpected finish action",
Trace(
Lookup_Start("b"),
Lookup_Finish(0),
Add("b"),
Count_Start(),
Count_Finish(1),
Delete("b"),
Lookup_Start(""),
Lookup_Finish(0),
Delete("b"),
Count_Start(),
Count_Finish(-1)
)
)
What is interesting to note here is the effect that the coverage function and the
reward functions have on the action selection process. Notice that all action symbols
are used k times before any of them is used k + 1 times.
more free ebooks download links at:
http://www.ebook-x.com