|
Contents Previous: Reviewing and Copying Test Results |
Chapter 5
This chapter describes how to run one or more of the automated HCTS tests without running the entire test suite. You may want to run a particular test separately to perform additional stress testing on your hardware that is not done by the standard certification test suite.
The HCTS Custom Test Case Generation screen enables you to create and execute test scenarios based on a predefined list of tests. By customizing these tests, you can do the following:
Select runtimes for each test individually
Run several tests in parallel, sequentially, or both
Start multiple instances and iterations of tests
The following terms are used to discuss custom test case generation:
The command form contains the stress tests and associated parameters that you enter via the browser, for placement into a command file. Because the command form is readable by the test suite's HTML form generator, you can create and edit a command file using a GUI instead of having to understand the syntax of a test command in the command file.
The command file contains test commands and keywords in a syntax understood by the Solaris Test Automation Facility (STAF) engine. The command file to be processed is passed to the STAF engine, which reads the test commands, processes them, and begins the associated tests.
If no command files were previously created for this test system, only the Select test to add to Command Form pull-down menu and the Create Command Form Filename toggle button and text window are present on the Custom Test Case Generation screen, as shown in Figure 5-1. After you create a command form and return to this screen, more command buttons are displayed.
Figure 5-1 Custom Test Case Generation Screen
The following figure shows an example custom test screen.
Figure 5-2 FTP Stress Custom Test
The Select test to add to Command Form pull-down menu enables you to choose one or more tests to include in a command form. This list of tests is different for systems and for each type of controller.
See Automated Tests for lists of the tests that are available for you to run for systems, motherboards, and different types of controllers.
Make sure your system meets the general hardware and software requirements for all certifications stated in the Hardware Certification Test Suite Installation Guide and the specific requirements for the technology you are testing as stated in the appropriate test plans.
Note - Make sure the test system has the appropriate devices installed for the selected tests.
Use the command buttons to do the following:
Add tests to the command form, edit test parameters selected in the command form, or delete a command form
Edit or execute the command file
Use this button to create a command form and its associated command file. In the CREATE Command Form Filename text box, type the name of the new command form. Click the Continue button to edit the test parameters and insert the test into the command form. Before creating the command form, the test suite polls the system to see if the device required by the selected test is present. If it is not found, an error message is displayed.
The newly created command form receives the name you entered (with suffix .cfm) and is stored in the /opt/SUNWhcts/results/hostname directory. The resulting command file receives the name of the command form (with suffix .cmd) and is stored in the /opt/SUNWstaf/cmd-files/hostname directory.
After creating the command form, return to the Custom Test Case Generation screen. The new command form is now listed in the Select Command Form to Process pull-down menu. The associated command file is now in the Select Command File Function pull-down menu.
Use this button to add a test to a command form. Select the name of the command form from the Select Command Form to Process pull-down menu, and choose the test to be added from the Test Selection pull-down menu. Then click the Continue button to edit the test parameters and add the test to the command form. Before adding the test to the command form, the test suite polls the system to see if the device required by the test selected is present. If it is not found, an error message is displayed.
Whenever an addition is made to a command form, the addition is reflected in the associated command file as well. The command file is overwritten with the information in the new command form.
Use this button to edit test parameters or to delete a test from a command form. Select the name of the command form from the Select Command Form to Process pull-down menu. Then click the Continue button to edit the test parameters in the command form.
To delete a test from a command form, set the number of instances of the test to zero (0).
Whenever a change is made to a command form, the change is reflected in the associated command file as well. The command file is overwritten with the information in the new command form.
Use this button to edit test parameters or to delete a test from a command file. Select the name of the command file from the Select Command File Function pull-down menu. Then click the Continue button to edit the command file. A scroll box displays the contents of the command file, from which you can make edits. To use this function, you must know the syntax of the command file.
Note - When an edit is made to a command file, the edit is not reflected in the associated command form. Therefore, if you want the command file and the associated command form to stay in sync, edit both using the EDIT Command Form button.
Use this button to delete a command form. Select the name of the command form from the Select Command Form to Process pull-down menu. Then click the Continue button to delete the form. Whenever a command form is deleted, the associated command file is deleted as well.
Use this button to execute a command file. Select the name of the command file from the Select Command File Function pull-down menu. Then click the Continue button to execute the command file. After all tests have started, the Select Action screen is displayed. You can view the associated test reports and logs by clicking Review Test Status.
Note - Due to the increased load on the system caused by running the tests, there will be a noticeable delay in processing user input on the test system and browser.
If at any time you want to stop the executing tests, click Stop Tests in the upper right corner of the HCTS screen. See the information on Stop Tests in Usage Notes.
Select the total number of hours and minutes you want the HCTS stress tests to execute. This time must be at least 30 minutes. The default is one hour.
Select the total number of instances of the test you want to run. HCTS will start multiple instances of the test. If you select zero (0), the test will not execute.
When this button is selected, all test logs are retained when the tests complete. If this button is not selected, the test logs are only retained if one or more of the tests fail.
If you want the test suite to run tests sequentially, select this button after each test chosen. The test suite will then wait for a test to complete before starting the next test. If you want tests to be run in parallel, do not select this button, and the test suite will start tests one after another until it encounters a wait keyword or the end of the command file.
Type the host name or IP address of the second system on which you want to run the network test. See Hardware Requirements for requirements for host names.
Type the size of the USB hard drive that is on your system.
Type the host name or IP address of the ppp client. See Hardware Requirements for requirements for host names.
Type a serial port name that is on the tested system. For example, enter /dev/cua/a.
Type a serial port name that is on the ppp client. For example, enter /dev/cua/a.
Type the baud rate to be used. The default value is 38400B.
Level 2 serial I/O controller tests include the following user-definable test parameters in addition to those listed for Level 1 tests.
Type the IP address to be used on the tested system after starting the ppp link. The default IP address is 192.168.0.1.
Type the IP address to be used on the ppp client after the ppp link has been started. The default IP address is 192.168.0.11.
Select this button to start a new Controller Certification. This button is disabled when tests are running.
Select this button to start a new Systems Certification. This button is disabled when tests are running.
Select this button to view existing log files. You can view log files from previous tests that you ran on this system as well as log files from tests that are currently running.
| Next: Automated Tests |