Overview

After the workflow of a program cycle has been built, it should be tested before publishing to the intended audience to ensure the program cycle will run as intended and that all components of the program cycle are correct.  

This document details the differences between Test Mode and Publish in Next.

Test Mode vs. Publish

When building a program cycle in Next, it is highly recommended that it be thoroughly tested before publishing it live to applicants.

Test Mode allows the program cycle to be live to program administrators, program staff, or any other individuals who are permitted to have access to the program cycle’s information before it goes live to the general audience.  What this means is that the program cycle will look and behave just as it would if it were taking live applications, but not be accessible to anyone that does not have the direct URL link.

In Test Mode, the complete workflow can be tested including accepting test applications, test reviewers providing feedback on the test applications, and setting up test awards.  The intent is to ensure that the program cycle is set up exactly as needed and intended before publishing.  

While testing, edits to the forms, workflow, and other elements of the program cycle can be made and then re-tested as soon as edits or changes are saved.  If edits or changes are discovered after the program cycle has been published, the process to make changes or corrections is a little more difficult and has some limitations, so be sure all testing is thorough and complete before publishing.  (Please see the article titled ➡️ How to Publish an Award Cycle for more information and limitations for publishing and unpublishing a program cycle.)

When a program cycle has been tested and all edits or changes have been applied, it is ready to be published.  After the Finish Testing button is selected, the program cycle cannot re-enter Test Mode.  Once published, all test data will be deleted and the program cycle will start fresh with actual applicant data.