In Functional test mode, the tests fully exercise all aspects of the selected devices and their associated device drivers.
In Functional test mode you can run a single test in to verify the functionality of a single device, or run multiple tests on all system devices for full system verification.
For thorough testing, the tests use a significant portion of the system resources. For this reason, do not run critical applications on the system or use the system for production purposes while testing in Functional test mode.
In Functional test mode, tests expect all system resources that are associated with the device to be available for testing. If the test cannot access a device, it registers a failure. The tests do not economize on runtime, but focus on achieving complete coverage and thoroughly exercising the device.
SunVTS does not verify that the system is in a safe offline state for Functional mode testing. You must be sure that your applications and the SunVTS diagnostic will not compete for system resources. For more information regarding runtime considerations refer to the SunVTS 3.0 User's Guide.