Check the sanity of a project at design time

The Sanity Check dialog displays existing alerts:

on a test design: Project Sanity Check, or
on the User Path validation: Execution Sanity Check

It makes it possible to identify potential inconsistencies of scenario components in their logical and hierarchical structure fix them and deliver a high-quality scenario or launch a feasible test.

Issues raised are classified in two levels: warning or blocking.

Icon	Meaning	Description
	Warning	The project contains errors.
	Blocking	The User Path validation cannot be launched.

The Project Sanity Check wizard is displayed when:

opening a project
selecting the Tools > Project Sanity Check command
checking out, updating, and canceling a collaborative project

The Execution Sanity Check dialog lists and depicts the errors and warnings detected:

Description describes the nature and the cause of the notice.
Resolution gives a link, when available, to access the defective scenario component.

The Refresh button must be clicked to update the list whenever changes are brought to the test design. The Execution Sanity Check dialog is non-modal, making it possible to check and fix issues at the same time.

For more information about the Execution Sanity Check wizard, see Check the test sanity before execution.

Solve missing elements in a project at design time

When designing a test scenario, the Project Sanity Check wizard may raise the following issues about missing elements.

Message	`File not found in variable X`
Description	In the project, variable X is configured to call a file that is not available.
Resolution	Variable X must be modified, as described in Create a variable.

Message	`File not found in binary POST request X`
Description	In the project, binary POST request X is configured to call a file that is not available.
Resolution	Request X must be modified, as described in POST requests with binary content.

Message	`Modifications in Javascript X have not been applied`
Description	In the project, a Logical action is an X JavaScript file that fails to execute.
Resolution	X JavaScript file must be modified, as described in JavaScript.

Message	`Missing channel in request X`
Description	A WebSocket action X requires a WebSocket channel which is missing to establish the connection to the WebSocket server.
Resolution	A WebSocket channel must be created as described in Create a WebSocket channel.

Message	`File not found for JavaScript library X`
Description	An X JavaScript library file required by a Virtual User script is missing in NeoLoad.
Resolution	The JavaScript library file must be created or specified as described in JavaScript libraries.

Solve collaborative project inconsistencies at design time

Sharing components of a project among different team testers may bring a number of inconsistencies when opening, publishing, updating, or reverting a collaborative project with the collaboration server. The Project Sanity Check wizard may raise the following issues about missing elements in a collaborative project.

For more information about collaborative projects, see Design collaborative projects.

Message	`Missing Virtual User X in Population Y`
Description	In the collaborative project, Population Y is configured to use a Virtual User X that does not exist.
Resolution	Population Y must be modified, as described in Configure a population or the missing Virtual User X must be recreated, as described in Create a User Path.

Message	`Missing Population X for Scenario Y`
Description	In the collaborative project, scenario Y is configured to use X population that does not exist.
Resolution	Scenario Y must be modified or missing population X must be recreated, as described in Populations

Message

Missing Population X in policy Y for scenario Z

Description

In the collaborative project, scenario Z uses Y population which is missing.

Or scenario Z uses Y population which requires a missing X population.

Resolution

Missing Y population must be recreated, as described in Populations.

Or the runtime parameters of Y population must be modified or the missing X population must be recreated, as described in Populations.

Message	`Missing server X in request Y`
Description	In the collaborative project, Y request refers to X server that does not exist.
Resolution	X server must be recreated, as described in Servers or the Y request must be modified, as described in HTTP requests.

Message	`Missing Server X in monitor Y`
Description	In the collaborative project, Y monitor refers to X server that does not exist.
Resolution	X server must be recreated, as described in Servers or the Y monitor must be modified, as described in Configure a monitor.

Message	`Duplicated Load Generator: X`
Description	In the collaborative project, the same Load Generator X is declared twice.
Resolution	The Load Generator duplicate must be renamed or removed, as described in Zones and Load Generator hosts.

Solve license issues at design time

When designing a project, the Project Sanity Check wizard may display the following license issues.

For more information about NeoLoad licenses, see Missing license.

Message	`Your license does not permit saving commercial projects. Please change your license`.
Description	The current evaluation license makes it possible to only view the design and results of the project because the project was created with a commercial license. No change can be saved. No test can be started.
Resolution	A commercial license must be installed to work on the project. For more information, see Manage licenses or contact Tricentis.

Message	`The X module is enabled for your evaluation only. It must be purchased as an option in the commercial version`.
Description	The project uses a module provided in the free trial version which will require a commercial license in the future.
Resolution	The module used must be included in the future commercial license. For more information, contact Tricentis.

Message	`Your license does not permit to save collaborative projects. Please change your license or save the project with another name`.
Description	The project cannot be saved as a collaborative project because the Collaboration module is unavailable on the machine.
Resolution	A collaborative license must be installed or the project must be saved locally as a regular non-collaborative project. For more information, see Design collaborative projects.