This section discusses functionality tests and results. In particular, the tests answer the question of what happens on restart to iterations that have been previously answered but are not asked during this session.

The test project asks the respondent to decide if the final iteration has been asked. This makes it easier to run the test but may not be the prevalent scenario. Unexpanded loops can be useful for diary studies where a respondent completes one iteration of a loop each day or each time a product is used. To avoid entering previous iterations each time the study is entered, keep a CurrentDay variable and update it for each instantiation of the interview. This example creates an initial iteration of the loop and initializes CurrentDay on the initial pass through the interview. On subsequent restarts, it retrieves the CurrentDay value from off path data and creates a new iteration of the loop using that value.

There must be some indicator that the project is complete. For this example, we have used a question to check for project completion. More likely scenarios are that the interviewing interval has closed or if enough data had been collected. If more iterations of data (diary days for example) are required, terminate the interview with a Stopped signal to allow restart.

This is a general CopyOffPathQuestionData function that can be used whenever off path data may be required.

The HDataUnbound.mdd test project has been used to test when an iteration is created, filled, or cleared. The script logic is as follows.

In this test, steps 1 through 8 are the same as the previous test.

Timing out and restarting a survey from the URL has the same behaviour.

In this test, steps 1 through 8 are the same as the previous tests.