Test a project before publishing

You may want to run a project through a testing phase to gain insight on how it will appear and behave once officially published. Should there be any problems, you will have the opportunity to troubleshoot or make appropriate modifications before tasks reach designated users.

There are two ways to test a project:

1. Create a Test Cycle project - a copy of a project with a small group of members to test all aspects of a project.
2. Perform a slow project launch - a procedural way to publish a project to verify tasks and emails with live data.

You can also use both methods for a very thorough testing sequence.

When do I create a test cycle?

Create a Test Cycle to verify:

• the effects of any significant modifications made to a project,
• task owner experience,
• rater experience,
• triggers based on a subject field or rater group,
• correct setup of a merged project,
• correct setup and implementation of custom field mapping in reports,
• correct setup of organizational hierarchies,
• email invitations and/or reminders,
• cross-project response piping,
• verifying the correct and expected functionality of any complex or highly customized process used in the project.