Changes between Version 3 and Version 4 of Ticket #592, comment 24


Ignore:
Timestamp:
May 15, 2014, 1:20:43 PM (11 years ago)
Author:
olle

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #592, comment 24

    v3 v4  
    33 * Set-up: The lab environment extension were configured to measure temperature and humidity values every minute, and store the average values every 5 minutes. An activated alarm were identified by an entry in the log file. Alarms were configured for lab sensors 1 and 2:[[BR]][[BR]]a. The alarms were set to be in use during hours `08:00` - `16:30`.[[BR]]b. Narrow limit settings were used for temperature and humidity, ensuring that an alarm should be activated with high probability when averaged data were obtained to be stored on the server.[[BR]]c. User A were set in the user list for both alarms, while user B were set only in the user list for the alarm for sensor 1.[[BR]]d. At a specified time, the network cable for sensor 2 was disconnected for a 7 minute interval, in order to test missing data alarm.[[BR]]
    44
    5  * Results: The test results were those expected for a passed test:[[BR]][[BR]]a. No alarm were reported outside the time interval `08:00` - `16:30`, even though the temperature or humidity values were outside the alarm limits.[[BR]]b. Alarms were reported during the time interval `08:00` - `16:30`, when temperature or humidity values were outside the alarm limits.[[BR]]c. After an alarm had been reported, the alarm was marked as blocked for further alarm reports, until re-set by one of the configured users. Both alarm blocker `Yes/No` menus were enabled for alarm user A, while only the alarm blocker `Yes/No` menu for alarm 1 was enabled for user B.[[BR]]d. A blocked alarm could be re-set by a user for which the alarm blocker `Yes/No` menu was enabled by setting the menu to `No`, and pressing the "`Set alarm blocker`" button (the old alarm text will remain until a new alarm is reported).[[BR]]e. A "Missing data" alarm were reported for sensor 2, after it had been disconnected for more than 5 minutes.
     5 * Results: The test results were those expected for a passed test:[[BR]][[BR]]a. No alarm were reported outside the time interval `08:00` - `16:30`, even though the temperature or humidity values were outside the alarm limits.[[BR]]b. Alarms were reported during the time interval `08:00` - `16:30`, when temperature or humidity values were outside the alarm limits.[[BR]]c. After an alarm had been reported, the alarm was marked as blocked for further alarm reports, until re-set by one of the configured users. Both alarm blocker `Yes/No` menus were enabled for alarm user A, while only the alarm blocker `Yes/No` menu for alarm 1 was enabled for user B.[[BR]]d. A blocked alarm could be re-set by a user for which the alarm blocker `Yes/No` menu was enabled by setting the menu to `No`, and pressing the "`Set alarm blocker`" button (the old alarm text will remain until a new alarm is reported).[[BR]]e. A "Missing data" alarm was reported for sensor 2, after it had been disconnected for more than 5 minutes.