| 101 | | || || || || |
| | 101 | == Test Case 5 == |
| | 102 | === Purpose === |
| | 103 | Verify Simulation Script tab shows all event types with proper formatting: bold for event type, Italics for field names, correct indenting for field data. Verify proper function at boundary conditions: start and end of script. |
| | 104 | |
| | 105 | === Configuration === |
| | 106 | Attached to this page is a test script file: `incident_multiple.xml`. Save this file to the `dynamicdata` directory and rename the file to `incident_script.xml`. |
| | 107 | |
| | 108 | In a terminal window (from webapps directory) execute: `python einotebook/spikes/runTimer.py`. |
| | 109 | |
| | 110 | === Application Startup === |
| | 111 | In a terminal window with `webapps` as the current directory, start the web server with the (Python 2.7) command: `python -m CGIHTTPServer 8080` |
| | 112 | |
| | 113 | Open a web browser to `localhost:8080/einotebook/` |
| | 114 | |
| | 115 | Four tabs appear with the first tab active ("Incident Summary"). Click on the "Simulation Script" tab. |
| | 116 | |
| | 117 | Every incident has its respective color, i.e, nothing is greyed out. The first event at time "00:00:00" with incident number "181" is highlighted. |
| | 118 | |
| | 119 | For each incident, each event has a header in bold and aligned to the left, for example, for the first incident, the event names "Incident Start", "MAINTENANCE_RADIO" and "TELEPHONE CONVERSATION Evaluation"in rp |