Progress windows show details of processing for both data loading and analysis processing. These progress windows show the steps and time of execution to give an indication of both progress and effort. you can use them to determine problems with certain data sets. Some sites have extensive loading processes, and the progress window can be used to determine issues with loading, or entertain you at least. You can turn them on or off.
Note: In most PlanTest production, data is loaded from a job control or scripted command line use, also using startup parameters to execute a full run of all automated tests . Therefore, data loading or test execution using the PlanTest menus is unusual and mainly for testing or for a specific case. We use the term ad hoc to describe such use.;
When PlanTest is started from job control, or the command line, data loading occurs prior to the initialization of the PlanTest UI and framework. This allows for data context signals to modify the PlanTest configuration. For some sites this is essential. You can toggle the progress window, but in most cases you will probably leave it on to gather feedback on the loading.
If auto-run is indicated in the startup parameters, PlanTest will perform a complete execution of all pertinent analytic tests once the data is loaded and the application UI is initiated - including the map loads. The progress window will give an excellent feedback on the detailed execution of all tests, allowing you to see problems prior to inspecting the test results.
Ad hoc data loading is a data load in-session using the Import menu. You may elect to show the Progress Window with this option.
Ad hoc analysis execution of all automated tests refers to arbitrary in-session execution using the Analysis menu. You may elect to show the Progress Window with this option.
You can elect to have the Progress Window close automatically when the tasks are complete.