2 Why We Need Model-Based Testing

180 Modeling Systems with Structured State
CommitComplete action
If a Commit action is pending and there are no conflicts, then the repository is able
to incorporate the proposed changes. The successful update is represented by the
CommitComplete action.
partial static class User
{
static Set NextVersion()
{
return new Set(Repository.currentRevision,
Repository.currentRevision + 1);
}
}
static bool CommitCompleteEnabled(string user, int newVersion)
{
return IsUser(user) && CommitPending(user)
&& conflicts[user].IsEmpty
&& newVersion == (revisions[user].IsEmpty
? Repository.currentRevision
: (Repository.currentRevision + 1));
}
[Action]
static void CommitComplete([Domain("Users")] string user,
[Domain("NextVersion")] int newVersion)
{
Map userRevisions = revisions[user];
}
version = version.Override(user, newVersion);
revisions = revisions.Override(user,Map.EmptyMap);
commitPending = commitPending.Remove(user);
Repository.Commit(user, "Check in", userRevisions);
In later chapters we will show how the model of revision control system can be
used to predict behavior. For now, let’s just consider one scenario.
If you look at the scenario given above in Section 10.4.1, you may notice that
user bob had other ways to resolve the conflict. We can use the model to enumerate
what the possible outcomes might have been. These are shown in Figure 10.1. The
more free ebooks download links at:
http://www.ebook-x.com