Executing the test

If other versions of logi.CAD 3 are started, exit all logi.CAD 3 versions. Then start the version of logi.CAD 3 in which you want to execute the test.
If the application has already been loaded onto the PLC (this is visible because of the execution state Running within the Instances view), disconnect from the PLC. Depending on the PLC, best practice is to execute the following actions as well:
1. In case of the built-in PLC: Stop and start the built-in PLC.
2. In case of another PLC: Terminate and re-start the →runtime system .
Only required for a →PIL-test :
1. Create a device object for a device configuration by which means you are going to address the target system during the PiL-test.
  
  Details: See "Creating a device object".
2. In this device object, enter the platform for the target system.
3. Save the device object.

Have the tests executed. This is possible either on the PC (without or with test coverage) or on the target system – as you require this test execution.

Test execution	Command to be selected
→SIL-test without test coverage	context menu of the test suite file, Test Framework and Run SiL-Test
SIL-test with test coverage	context menu of the test suite file, Test Framework and Run SiL-Test with Coverage
PIL-test	context menu of the test suite file, Test Framework , Run PiL-Test and the appropriate device If your target system does not support the PiL-test, contact logi.cals for more information.

Restrictions

See "Restrictions when using the test frameworks" for restrictions when executing a test suite.

Result of the test execution: The console displays the progress and the result of the test execution. After the execution, links are displayed (e.g. a link to a test report) while the appertaining files can be found in the folder where the test suite is located (e.g file report.html for the test report).

If the test is repeatedly executed, the files for the test execution are overwritten.
Workaround 1: If you want to keep the files for a test execution, move the files to a different folder and/or rename them so that they have unique names. Example: The test report report.html becomes report_180329_1.html.
Workaround 2: If you want to have an overall test report for several test suites, select these test suites within the same project and select the appropriate command for the test execution. Result: The tests are executed for all selected test suites. Subsequently, the test report report.html contains the information on the test execution of these test suites.

As additional information for the SiL-test: The Build Log view informs you whether the application has been built successfully or not. (In this context, "whether the application has been built" means " whether the test has been executed" here.)