A test case is an event sequence.
A test suite consists of some test cases.
A test suite file is denoted by the test cases in it.
The test cases are represented by the event sequences,
where integers are used to denote the number of the events
(the event numbers are 0-based).
Also, to denote the feasibility of the test cases,
a boolean and a failure point is added for each test case.

The boolean means whether a test case is feasible or not,
and the failure point means the index of the event which
is not executed successfully because of the infeasibility
(notice that it is different from the failures caused by faults).
If the boolean is true, the failure point is equal to
the length of the test case.

We give two examples here.

Ex1:
1 2 0 4 5 true	5
The test case is (Event 1, Event 2, Event 0, Event 4, Event 5),
and it is feasible.

Ex2:
0 4 2 1 9 2 7 4 0 2 false	4
The test case is (Event 0, Event 4, Event 2, Event 1, Event 9,
Event 2, Event 7, Event 4, Event 0, Event 2). It is infeasible,
and the event at index 4, Event 9, is not executed successfully.
In another word, all the events before it, that is, (Event 0,
Event 4, Event 2, Event 1), can be executed successfully.

All the events are separated by a space.
The boolean is separated from the test case by a space.
The boolean and the failure point are separated by a tab space.
There are no leading or trailing spaces for any line in
a test suite file. The only empty line in a test suite file
is the last line.