Wash, rinse, repeat

The same principle applies to modifying the type of data in the page classes. As an example, the custom date tokens could be passed like this:

Set JOURNEY="host <today+7>"; yarn ch15
const match = journey.match(/(<.+>)/);
const dateToken = match ? match[0] : "";
Helpers.setValueIfExists(dateField, dateToken);

Now, we have a date token extracted from the journey value. The token is passed to dateField, if it exists, and set to next week’s date. If there is no token, the date is set to an empty string, which the method will return immediately as there is nothing to do.

At this point, we have covered all the processes of a non-deterministic engine. New pages will be reported in the results and must be added to extend the path coverage. If a page is never encountered in a particular path, it does not stop the test. If an error is encountered, it is reported. If the path gets stuck, it is also reported. The data and the...