...

Once you we have piloted the test, you we will likely have found some minor things to change, and perhaps even a few major ones. The great part of this is that you we get to fix your the test before your our real audience sees those mistakes.

Depending on your the testing tool, you we may be able to edit the existing test, or you we may need to duplicate it and edit the new copy.

...

If your the tool lets you us edit the existing test, you we can make your our changes right there.

Most changes can be done without consequences, but we should be careful about two things:

• Editing the tree can affect your the task answers.
  If you we make structural changes to your the tree, we should make sure that your the task answers are still correct. For example, if you we move a topic in your the tree, and it was an answer to one of your the tasks, you we should update the task answer accordingly.
  
  For more on revising the tree and your tasks, see Chapter 14 - Revising and retesting.
  
  
• Delete any pilot data you’ve collected.
  If you we plan to use the same test instance for your the real study, be sure to we should delete the data collected during the pilot testing. However, if the data came from representative users and you we didn’t make any substantial revisions to your the test after piloting, you could we can keep this data to join the “real” data you’ll we’ll be collecting later.
  
  
  

Some tools don’t let you us edit a test that has been launched. So if you we launched your a test for purposing of piloting, you’ll we’ll need to duplicate it first, then edit the newly created duplicate.

This has the advantage of keeping a revision history (of sorts) in case you we want to go back to a previous version to check something or to grab an older version of a task’s wording (for example).

Because you’re we’re revising (and eventually launching) the newly created duplicate, you we don’t have to worry about deleting pilot results; they’ll be attached to the previous copy, not the new one.

...