Automate the following parts of the test script

[noel]

These are the parts of the test script we should be able to auto mate with selenium

# DAEMONS TAB

1. On the Daemons tab of Settings, stop all of the daemons. Check to make sure they all stop.
2. Start up each of the daemons. Make sure they start.

# MONITORING

1. Load win2k-test2
2. Confirm that all device components are loaded (OS and HW)
3. Manually flip interfaces, ip services, filesystems, OSProcesses to be NOT monitored
4. Check to see that each is not monitored
5. Flip them all back
6. Check to see that each is monitored 3.

# EVENT CONSOLE

1. Follow Section 6 of the basic training guide.

# BACKUPS TAB

1. Run a backup.
2. Check to see that the backup appears in the list.

# FILESYSTEM & THRESHOLDS

1. Navigate to the OS tab for the machine “build.zenoss.loc” you loaded into the system.
2. Click the “/” File System.
3. Click on the Templates tab
4. Click the Create Local Copy button to make a local copy of the template for this device.
5. Click the name of the template to modify it
6. In the Thresholds area, in the Add box, enter the name “Really Low Threshold” and click the Add button.
7. Click on the link for the Really Low Threshold.
8. Choose the usedBlocks use Blocks
9. In the Max Value area, enter the following expression: here.totalBlocks * .05

1. Make sure Enabled is set to True.
2. Click on the "Save" button.
3. Click over to the Events console to see the result of changing the threshold.

# CUSTOM DEVICE REPORTS

1. Do Activity 9.3 in the basic training guide

# GRAPH REPORTS

1. Create a graph report. Add some graphs. Make sure it shows the right graphs.
2. Re-sequence the graphs. Make sure the sequencing was applied

# PERFORMANCE REPORTS

1. For each utilization report, make sure the right boxes show up.
2. Make sure none of the devices have N/A for % Util
3. Exercise all the date range etc. controls. Verify the report responds. 7.

# USER COMMANDS

1. Pick a device and run the Forward DNS Lookup command.
2. Confirm that the right string comes back.
3. Run the same command on a device class and see that the command is executed against each device

# CUSTOM EVENT VIEWS

1. Make an event view with a complex rule and non-default fields.
2. Make an event that matches and an event that doesn't.
3. Check to see if the right event shows up in the event view.
4. Make sure the right fields are shown. 5.

# Multi-Graph Reports with collections

1. Add a collection of objects using the device class /Server/Linux
2. Add a graph definition that has the DataPoint laLoadInt5_laLoadInt5
3. Add a graph group with these two in "Separate graph for each device"
4. Confirm that the graph displays correctly
5. Now switch to "All devices on a single graph"
6. Confirm that the graph displays correctly 6.

# Multi-Graph Reports with selected components (LOTS MORE HERE)

1. Add a collection with all of gate2's interfaces and gate the router
2. Add a graph definition with ifInOctets
3. Add a graph group with these in separate and single graph mode
4. Confirm that the reports render correctly 5.