Detailed Results Report

Overview
Passed Failed Known Undefined %Passed
Features 0 5 0 0 0.00
Scenarios 121 46 0 0 72.46
Steps 413 46 0 6 88.82
Overall Duration: 1h 18m 41s

Table of Contents
1. Basic Security Testing ....................................................................................................................... 5
1. verify the wifi network name/wifi ssid in registerd panel .................................................... 5
2. LyricDAS_1095_User to Disarm the panel ........................................................................... 6
3. LyricDAS_1052_User to Arm Away the panel ..................................................................... 6
4. LyricDAS_1097_User to Arm Stay the panel ........................................................................ 6
5. Time synchronization to panel ................................................................................................ 7
6. LyricDAS_1052_User to Arm Away the panel ..................................................................... 7
7. LyricDAS_1095_User to Disarm the panel ........................................................................... 7
8. time synchronization to panel ................................................................................................. 7
9. Verify the default Entry and Exit delay and default chime and default camera settings . 7
10. Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds ......................... 8
11. Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds ......................... 8
12. Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds ......................... 8
13. Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds ......................... 8
14. Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds ......................... 9
15. Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds ......................... 9
16. Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds ......................... 9
17. Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds ......................... 9
18. LyricDAS_1095_User to Disarm the panel ........................................................................... 9
19. Time synchronization to panel ................................................................................................ 10
20. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 10
21. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 10
22. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 10
23. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 10
24. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 11
25. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 11
26. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 11
27. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 11
28. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 12
29.
Page 1 of 47
 Detailed Results Report

29. LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
read the chime volume levels .................................................................................................. 12
30. Time synchronization to panel ................................................................................................ 13
31. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 13
32. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 13
33. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 14
34. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 14
35. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 14
36. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 14
37. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 14
38. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 15
39. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 15
40. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 15
41. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 15
42. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 16
43. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 16
44. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 16
45. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 16
46. LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and
ArmStay modes ........................................................................................................................ 16
47. Time synchronization to panel ................................................................................................ 17
48. Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway ............................ 17
49. Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway ............................ 17
50. Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway ............................ 17
51. Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway ............................ 18
52. Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway ............................ 18
53. Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway ............................ 18
54. Add user and read the user details.Add Duplicate user and verify .................................... 18
55. Add user and read the user details.Add Duplicate user and verify .................................... 19
56. Add user and read the user details.Add Duplicate user and verify .................................... 19
57. Edit user and verify the Edited user details .......................................................................... 19
58. Edit user and verify the Edited user details .......................................................................... 19
59. Delete user and verify the deleted user details. ..................................................................... 20
2. DoorContact Test ............................................................................................................................... 20
1. time synchronization to panel ................................................................................................. 20
2. LyricDAS_SensorEnrollment_1_User to Disarm the panel ................................................ 20

3.
Page 2 of 47
 Detailed Results Report

3. LyricDAS_SensorEnrollment_2_ Start Sensor Enrollment ................................................ 20

4. LyricDAS_SensorEnrollment_3_ Trigger the Sensor on for Enrollment .......................... 21
5. LyricDAS_SensorEnrollment_3_1_Trigger the Sensor off for Enrollment ....................... 21
6. time synchronization to panel ................................................................................................. 21
7. LyricDAS_SensorEnrollment_4_To Check sensor enrollment is saved and stop enrollment
.................................................................................................................................................... 21
8. LyricDAS_SensorEnrollment_4_To Check sensor enrollment is saved and stop enrollment
.................................................................................................................................................... 22
9. time synchronization to panel ................................................................................................. 22
10. LyricDAS_SensorEnrollment_5_Trigger the Sensor on fault ............................................. 22
11. time synchronization to panel ................................................................................................. 22
12. LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault ........................................ 22
13. time synchronization to panel ................................................................................................. 23
14. LyricDAS_SensorEnrollment_6_Trigger the Sensor tamper on ........................................ 23
15. time synchronization to panel ................................................................................................. 23
16. LyricDAS_SensorEnrollment_6_1_Trigger the Sensor tamper off .................................... 23
17. LyricDAS_SensorEnrollment_6_2_Disarm the panel and get the tamper status ............. 24
18. LyricDAS_SensorEnrollment_8_Bypass the Specific Zone ................................................. 24
19. LyricDAS_SensorEnrollment_9_ Trigger the Sensor fault ................................................. 24
20. LyricDAS_SensorEnrollment_9_1 Trigger the Sensor fault ............................................... 24
21. LyricDAS_SensorEnrollment_10_User to Disarm the panel .............................................. 24
22. LyricDAS_SensorEnrollment_11_ Trigger the Sensor fault ............................................... 24
23. LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault ........................................ 25
24. LyricDAS_SensorEnrollment_9_ Get the Sensor status and panel status ......................... 25
25. LyricDAS_SensorEnrollment_9_ Get the Sensor status and panel status ......................... 25
26. LyricDAS_SensorEnrollment_10_User to Disarm the panel .............................................. 26
27. LyricDAS_1052_User to Arm Away the panel ..................................................................... 26
28. time synchronization to panel ................................................................................................. 26
29. LyricDAS_SensorEnrollment_5_Trigger the Sensor on fault when panel is in ArmAway ....
26
30. LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault when panel is in ArmAway
.................................................................................................................................................... 26
31. time synchronization to panel ................................................................................................. 27
32. LyricDAS_SensorEnrollment_10_User to Disarm the panel .............................................. 27
33. LyricDAS_1097_User to Arm Stay the panel ........................................................................ 27
34. time synchronization to panel ................................................................................................. 27
35. LyricDAS_SensorEnrollment_5_Trigger the Sensor on fault when panel is in Armstay ......
28
36. LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault when panel is in Armstay ..
28
37. time synchronization to panel ................................................................................................. 28
38. LyricDAS_SensorEnrollment_1_User to Disarm the panel ................................................ 28
39. time synchronization to panel ................................................................................................. 28
40. Start/Stop LED Test and validate the response .................................................................... 29
41. Start/Stop LED Test and validate the response .................................................................... 29
42. time synchronization to panel ................................................................................................. 29
43. Start Range Test and validate the response .......................................................................... 29
44. time synchronization to panel ................................................................................................. 30
45. Get the Range value ................................................................................................................. 30
46. Stop Range Test and validate the response ........................................................................... 30
47. Start Walk Test and validate the response ............................................................................ 30

48.
Page 3 of 47
 Detailed Results Report

48. LyricDAS_SensorEnrollment_5_Trigger the Sensor on fault ............................................. 30

49. time synchronization to panel ................................................................................................. 31
50. LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault ........................................ 31
51. Stop Walk Test and validate the response ............................................................................. 31
52. LyricDAS_SensorEnrollment_10_ Delete sensor from the panel ....................................... 31
3. System Security Feature Testing ...................................................................................................... 32
1. LyricDAS_SensorEnrollment_10_User to Disarm the panel .............................................. 32
2. Configure the Entry and Exit delay 15 seconds and arm the panel , verify event after 15
seconds ...................................................................................................................................... 32
3. LyricDAS_SensorEnrollment_10_User to Disarm the panel .............................................. 32
4. Configure the Entry and Exit delay 30 seconds and arm the panel , verify event after 30
seconds ...................................................................................................................................... 32
5. LyricDAS_SensorEnrollment_10_User to Disarm the panel .............................................. 33
6. Configure the Entry and Exit delay 45 seconds and arm the panel , verify event after 45
seconds ...................................................................................................................................... 33
7. LyricDAS_SensorEnrollment_10_User to Disarm the panel .............................................. 33
8. Configure the Entry and Exit delay 60 seconds and arm the panel , verify event after 60
seconds ...................................................................................................................................... 34
9. LyricDAS_SensorEnrollment_10_User to Disarm the panel .............................................. 34
4. ZWave Functional Testing ................................................................................................................ 34
1. LyricDAS_SensorEnrollment_1_User to Disarm the panel ................................................ 34
2. time synchronization to panel ................................................................................................. 34
3. LyricDAS_180_Zwave- Send API to exclude the dimmer or multilevel switch ................ 35
4. Zwave- Trip dimmer or multilevel switch to exclude ........................................................... 35
5. LyricDAS_180_Zwave- Send API to include the dimmer or multilevel switch ................. 35
6. Zwave- Trip dimmer or multilevel switch to include ........................................................... 35
7. LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status
of each test ................................................................................................................................ 36
8. LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status
of each test ................................................................................................................................ 36
9. LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status
of each test ................................................................................................................................ 36
10. LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status
of each test ................................................................................................................................ 37
11. LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status
of each test ................................................................................................................................ 37
12. LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status
of each test ................................................................................................................................ 38
13. LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status
of each test ................................................................................................................................ 38
14. LyricDAS_180_Zwave- Send API to exclude the dimmer or multilevel switch ................ 38
15. Zwave- Trip dimmer or multilevel switch to exclude ........................................................... 39
16. time synchronization to panel ................................................................................................. 39
17. LyricDAS_180_Zwave- Send API to exclude the binary switch ......................................... 39
18. Zwave- Trip binary switch to exclude .................................................................................... 39
19. LyricDAS_180_Zwave- Send API to include the binary switch .......................................... 39
20. Zwave- Trip binary switch to include .................................................................................... 40
21. LyricDAS_181_Zwave device binary switch on ,set percentage and off then verify status of
each test ..................................................................................................................................... 40
22. LyricDAS_181_Zwave device binary switch on ,set percentage and off then verify status of
each test ..................................................................................................................................... 40

23.
Page 4 of 47
 Detailed Results Report

23. LyricDAS_181_Zwave device binary switch on ,set percentage and off then verify status of
each test ..................................................................................................................................... 41
24. LyricDAS_181_Zwave device binary switch on ,set percentage and off then verify status of
each test ..................................................................................................................................... 41
25. LyricDAS_180_Zwave- Send API to exclude the binary switch ......................................... 41
26. Zwave- Trip binary switch to exclude .................................................................................... 42
5. Keyfob Test ......................................................................................................................................... 42
1. LyricDAS_SensorEnrollment_1_User to Disarm the panel ................................................ 42
2. LyricDAS_SensorEnrollment_2_ Start Sensor Enrollment for keyfob .............................. 42
3. Time synchronization to panel ................................................................................................ 42
4. LyricDAS_SensorEnrollment_3_ Trigger the keyfob Sensor Enrollment ......................... 43
5. LyricDAS_SensorEnrollment_3_1_Trigger the Sensor for Enrollment ............................ 43
6. time synchronization to panel ................................................................................................. 43
7. LyricDAS_SensorEnrollment_4_To Check sensor enrollment is saved and stop enrollment
.................................................................................................................................................... 43
8. LyricDAS_SensorEnrollment_4_To Check sensor enrollment is saved and stop enrollment
.................................................................................................................................................... 44
9. time synchronization to panel ................................................................................................. 44
10. LyricDAS_SensorEnrollment_5_Press the keyfob button for ArmAway .......................... 44
11. time synchronization to panel ................................................................................................. 44
12. LyricDAS_SensorEnrollment_6_Press the keyfob button for Disarm ............................... 45
13. time synchronization to panel ................................................................................................. 45
14. LyricDAS_SensorEnrollment_7_Press the keyfob button for ArmStay ............................ 45
15. time synchronization to panel ................................................................................................. 46
16. LyricDAS_SensorEnrollment_8_Press the keyfob button for panic .................................. 46
17. time synchronization to panel ................................................................................................. 46
18. Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway ............................ 46
19. time synchronization to panel ................................................................................................. 47
20. LyricDAS_SensorEnrollment_6_Press the keyfob button for Disarm ............................... 47
21. LyricDAS_SensorEnrollment_11_ Delete keyfob from the panel ....................................... 47

Detailed Results Report

Feature: Basic Security Testing
Passed: 46 Failed: 13 Undefined: 0 Duration: 1882.0
Scenario Outline: verify the wifi network name/wifi ssid in registerd panel
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "get-wifi-ssid" the panel using the command as "GET /ISOM/DeviceMgmt/Interfaces/config?l
with "na"
Then Panel should get function as "get-wifi-ssid" and Expected response should be as "Response Code : 2

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)

Page 5 of 47
 Detailed Results Report

at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "get-wifi-ssid" and Expected response should be as "Response Code
/BasicSecurity.feature:7)
After
Back to Table of Contents
Scenario Outline: LyricDAS_1095_User to Disarm the panel
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_disarm_as_something_and_expected_respon
(StepDefinitionTest.java:447)
at .Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200O
/BasicSecurity.feature:26)
After
Back to Table of Contents
Scenario Outline: LyricDAS_1052_User to Arm Away the panel
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Arm the panel using as "PUT /ISOM/AC/Partitions/1/setState/fullSet" with "ArmAway"
Then Panel should get Armed as "ArmAway" and Expected response should be as "Response Code : 200O

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_armed_as_something_and_expected_respon
(StepDefinitionTest.java:362)
at .Then Panel should get Armed as "ArmAway" and Expected response should be as "Response Code : 2
/BasicSecurity.feature:36)
After
Back to Table of Contents
Scenario Outline: LyricDAS_1097_User to Arm Stay the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud

Page 6 of 47
 Detailed Results Report

When Arm the panel using as "PUT /ISOM/AC/Partitions/1/setState/partSet" with "na"

Then Panel should get Armed as "ArmStay" and Expected response should be as "Response Code : 200O
After
Back to Table of Contents
Scenario Outline: Time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "ArmAway" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_1052_User to Arm Away the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Arm the panel using as "PUT /ISOM/AC/Partitions/1/setState/fullSet" with "ArmAway"
Then Panel should get Armed as "ArmAway" and Expected response should be as "Response Code : 200O
After
Back to Table of Contents
Scenario Outline: LyricDAS_1095_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarmed" and Expected response should be as "Response Code : 200O
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "Panel settings delay" and sync with panel
After
Back to Table of Contents
Scenario Outline: Verify the default Entry and Exit delay and default chime and default camera settings
Passed: 2 Failed: 1 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "default delay" the panel using the command as "GET /ISOM/AC/Partitions/1/config?dvi=100
Then Panel should get function as "default delay" and Expected response should be as "Response Code :

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)

Page 7 of 47
 Detailed Results Report

at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "default delay" and Expected response should be as "Response Cod
/BasicSecurity.feature:96)
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds
Passed: 2 Failed: 1 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Entry Exit delay 15" the panel using the command as "PUT /ISOM/AC/Partitions/1/config?d
Exit delay 15"
Then Panel should get function as "Entry Exit delay 15" and Expected response should be as "Response C

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Entry Exit delay 15" and Expected response should be as "Respon
/features/BasicSecurity.feature:129)
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Status for delay 15" the panel using the command as "GET /ISOM/AC/Partitions/1/config?d
Then Panel should get function as "Status for delay 15" and Expected response should be as "Response C
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Entry Exit delay 45" the panel using the command as "PUT /ISOM/AC/Partitions/1/config?d
Exit delay 45"
Then Panel should get function as "Entry Exit delay 45" and Expected response should be as "Response C
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds
Passed: 3 Failed: 0 Undefined: 0

Page 8 of 47
 Detailed Results Report

Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Status for delay 45" the panel using the command as "GET /ISOM/AC/Partitions/1/config?d
Then Panel should get function as "Status for delay 45" and Expected response should be as "Response C
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Entry Exit delay 60" the panel using the command as "PUT /ISOM/AC/Partitions/1/config?d
Exit delay 60"
Then Panel should get function as "Entry Exit delay 60" and Expected response should be as "Response C
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Status for delay 60" the panel using the command as "GET /ISOM/AC/Partitions/1/config?d
Then Panel should get function as "Status for delay 60" and Expected response should be as "Response C
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Entry Exit delay 30" the panel using the command as "PUT /ISOM/AC/Partitions/1/config?d
Exit delay 30"
Then Panel should get function as "Entry Exit delay 30" and Expected response should be as "Response C
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay duration as 15,30,45 and 60 seconds
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Status for delay 30" the panel using the command as "GET /ISOM/AC/Partitions/1/config?d
Then Panel should get function as "Status for delay 30" and Expected response should be as "Response C
After
Back to Table of Contents
Scenario Outline: LyricDAS_1095_User to Disarm the panel
Passed: 2 Failed: 0 Undefined: 0
Before
Page 9 of 47
 Detailed Results Report

Given Lyric DAS Panel is up and running, Connected to Cloud

When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
After
Back to Table of Contents
Scenario Outline: Time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "Panel chime settings" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user to configure the Chime volume as "Disarm-10;ArmAway-15;Armstay-15" using as "PUT /ISO
/config?dvi=100" with "Chime volume1"
Then Panel should configured the chime volume "Disarm-10;ArmAway-15;Armstay-15"using with "Chim
Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user to configure the Chime volume as "Disarm-10;ArmAway-15;Armstay-15" using as "GET /ISO
/config?dvi=100" with "na"
Then Panel should configured the chime volume "Disarm-10;ArmAway-15;Armstay-15"using with "Chim
Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user to configure the Chime volume as "Disarm-0;ArmAway-0;Armstay-0" using as "PUT /ISOM/
dvi=100" with "Chime volume set2"
Then Panel should configured the chime volume "Disarm-0;ArmAway-0;Armstay-0"using with "Chime v
Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 3 Failed: 0 Undefined: 0
Before

Page 10 of 47
 Detailed Results Report

Given Lyric DAS Panel is up and running, Connected to Cloud

When user to configure the Chime volume as "Disarm-0;ArmAway-0;Armstay-0" using as "GET /ISOM/
dvi=100" with "na"
Then Panel should configured the chime volume "Disarm-0;ArmAway-0;Armstay-0"using with "Chime m
Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user to configure the Chime volume as "Disarm-0;ArmAway-10;Armstay-100" using as "PUT /ISO
/config?dvi=100" with "Chime volume set3"
Then Panel should configured the chime volume "Disarm-0;ArmAway-10;Armstay-100"using with "Chim
Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user to configure the Chime volume as "Disarm-0;ArmAway-10;Armstay-100" using as "GET /ISO
/config?dvi=100" with "na"
Then Panel should configured the chime volume "Disarm-0;ArmAway-10;Armstay-100"using with "Chim
Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user to configure the Chime volume as "Disarm-50;ArmAway-100;Armstay-10" using as "PUT /IS
/config?dvi=100" with "Chime volume set4"
Then Panel should configured the chime volume "Disarm-50;ArmAway-100;Armstay-10"using with "Ch
Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user to configure the Chime volume as "Disarm-50;ArmAway-100;Armstay-10" using as "GET /IS
/config?dvi=100" with "na"
Then Panel should configured the chime volume "Disarm-50;ArmAway-100;Armstay-10"using with "Ch

Page 11 of 47
 Detailed Results Report

Expected response should be as "Response Code : 200OK"

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.
panel_should_configured_the_chime_volume_somethingusing_with_something_and_expected_response_s
(StepDefinitionTest.java:603)
at .Then Panel should configured the chime volume "Disarm-50;ArmAway-100;Armstay-10"using with "
response should be as "Response Code : 200OK"(src/test/java/features/BasicSecurity.feature:167)
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user to configure the Chime volume as "Disarm-100;ArmAway-100;Armstay-100" using as "PUT /
/config?dvi=100" with "Chime volume set5"
Then Panel should configured the chime volume "Disarm-100;ArmAway-100;Armstay-100"using with "C
Expected response should be as "Response Code : 200OK"

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.
panel_should_configured_the_chime_volume_somethingusing_with_something_and_expected_response_s
(StepDefinitionTest.java:603)
at .Then Panel should configured the chime volume "Disarm-100;ArmAway-100;Armstay-100"using with
response should be as "Response Code : 200OK"(src/test/java/features/BasicSecurity.feature:167)
After
Back to Table of Contents
Scenario Outline: LyricDAS_1085_2_11_Verify User to configure the chime volume with multiple levels and
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user to configure the Chime volume as "Disarm-100;ArmAway-100;Armstay-100" using as "GET
/config?dvi=100" with "na"
Then Panel should configured the chime volume "Disarm-100;ArmAway-100;Armstay-100"using with "C
Expected response should be as "Response Code : 200OK"

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)

Page 12 of 47
 Detailed Results Report

at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.
panel_should_configured_the_chime_volume_somethingusing_with_something_and_expected_response_s
(StepDefinitionTest.java:603)
at .Then Panel should configured the chime volume "Disarm-100;ArmAway-100;Armstay-100"using with
response should be as "Response Code : 200OK"(src/test/java/features/BasicSecurity.feature:167)
After
Back to Table of Contents
Scenario Outline: Time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Panel Camera settings" and sync with panel
And Wait for "Panel Camera settings" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-true;ArmAway-false;Armstay-false
/AC/Partitions/1/config?dvi=100" with "Camera payload1"
Then Panel should configured the Base station Camera settings "Disarm-true;ArmAway-false;Armstay-fa
"Camera payload1" and Expected response should be as "Response Code : 200OK"

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.
panel_should_configured_the_base_station_camera_settings_somethingusing_with_something_and_expec
(StepDefinitionTest.java:658)
at .Then Panel should configured the Base station Camera settings "Disarm-true;ArmAway-false;Armsta
payload1" and Expected response should be as "Response Code : 200OK"(src/test/java/features/BasicSec
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-true;ArmAway-false;Armstay-false
/AC/Partitions/1/config?dvi=100" with "na"
Then Panel should configured the Base station Camera settings "Disarm-true;ArmAway-false;Armstay-fa
"Camera state1" and Expected response should be as "Response Code : 200OK"
After

Page 13 of 47
 Detailed Results Report

Back to Table of Contents

Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-false;ArmAway-false;Armstay-true
/AC/Partitions/1/config?dvi=100" with "Camera payload2"
Then Panel should configured the Base station Camera settings "Disarm-false;ArmAway-false;Armstay-t
"Camera payload2" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-false;ArmAway-false;Armstay-true
/AC/Partitions/1/config?dvi=100" with "na"
Then Panel should configured the Base station Camera settings "Disarm-false;ArmAway-false;Armstay-t
"Camera state2" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-false;ArmAway-true;Armstay-false
/AC/Partitions/1/config?dvi=100" with "Camera payload3"
Then Panel should configured the Base station Camera settings "Disarm-false;ArmAway-true;Armstay-fa
"Camera payload3" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-false;ArmAway-true;Armstay-false
/AC/Partitions/1/config?dvi=100" with "na"
Then Panel should configured the Base station Camera settings "Disarm-false;ArmAway-true;Armstay-fa
"Camera state3" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before

Page 14 of 47
 Detailed Results Report

Given Lyric DAS Panel is up and running, Connected to Cloud

When User to configure the Base station Camera settings as "Disarm-false;ArmAway-false;Armstay-false
/AC/Partitions/1/config?dvi=100" with "Camera payload4"
Then Panel should configured the Base station Camera settings "Disarm-false;ArmAway-false;Armstay-f
"Camera payload4" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-false;ArmAway-false;Armstay-false
/ISOM/AC/Partitions/1/config?dvi=100" with "na"
Then Panel should configured the Base station Camera settings "Disarm-false;ArmAway-false;Armstay-f
"Camera state4" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-false;ArmAway-true;Armstay-true"
/AC/Partitions/1/config?dvi=100" with "Camera payload5"
Then Panel should configured the Base station Camera settings "Disarm-false;ArmAway-true;Armstay-tr
"Camera payload5" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-false;ArmAway-true;Armstay-true"
/AC/Partitions/1/config?dvi=100" with "na"
Then Panel should configured the Base station Camera settings "Disarm-false;ArmAway-true;Armstay-tr
"Camera state5" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-true;ArmAway-false;Armstay-true"
/AC/Partitions/1/config?dvi=100" with "Camera payload6"
Then Panel should configured the Base station Camera settings "Disarm-true;ArmAway-false;Armstay-tr

Page 15 of 47
 Detailed Results Report

"Camera payload6" and Expected response should be as "Response Code : 200OK"

After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-true;ArmAway-false;Armstay-true"
/AC/Partitions/1/config?dvi=100" with "na"
Then Panel should configured the Base station Camera settings "Disarm-true;ArmAway-false;Armstay-tr
"Camera state6" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-true;ArmAway-true;Armstay-false"
/AC/Partitions/1/config?dvi=100" with "Camera payload7"
Then Panel should configured the Base station Camera settings "Disarm-true;ArmAway-true;Armstay-fa
"Camera payload7" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-true;ArmAway-true;Armstay-false"
/AC/Partitions/1/config?dvi=100" with "na"
Then Panel should configured the Base station Camera settings "Disarm-true;ArmAway-true;Armstay-fa
"Camera state7" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-true;ArmAway-true;Armstay-true"
/AC/Partitions/1/config?dvi=100" with "Camera payload8"
Then Panel should configured the Base station Camera settings "Disarm-true;ArmAway-true;Armstay-tr
"Camera payload8" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: LyricDAS_Verify Base Station Camera settings ON and OFF for Disarm, ArmAway and A

Page 16 of 47
 Detailed Results Report

Passed: 3 Failed: 0 Undefined: 0

Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When User to configure the Base station Camera settings as "Disarm-true;ArmAway-true;Armstay-true"
/AC/Partitions/1/config?dvi=100" with "na"
Then Panel should configured the Base station Camera settings "Disarm-true;ArmAway-true;Armstay-tr
"Camera state8" and Expected response should be as "Response Code : 200OK"
After
Back to Table of Contents
Scenario Outline: Time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Panel panic alaram" and sync with panel
And Wait for "Panel panic alaram" and sync with panel
After
Back to Table of Contents
Scenario Outline: Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Disarm" the panel using the command as "PUT /ISOM/AC/Partitions/1/setState/unSet" with
Then Panel should get function as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Panic Alarm" the panel using the command as "PUT /ISOM/AC/DetectorGroups/999/release
"na"
Then Panel should get function as "Panic Alarm" and Expected response should be as "Response Code : 2
After
Back to Table of Contents
Scenario Outline: Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Clear Alarm" the panel using the command as "PUT /ISOM/AC/Partitions/1/alarmState/clea
Then Panel should get function as "Clear Alarm" and Expected response should be as "Response Code : 2

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)

Page 17 of 47
 Detailed Results Report

at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Clear Alarm" and Expected response should be as "Response Cod
/BasicSecurity.feature:234)
After
Back to Table of Contents
Scenario Outline: Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "ArmAway" the panel using the command as "PUT /ISOM/AC/Partitions/1/setState/fullSet" w
Then Panel should get function as "ArmAway" and Expected response should be as "Response Code : 200
After
Back to Table of Contents
Scenario Outline: Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Panic Alarm" the panel using the command as "PUT /ISOM/AC/DetectorGroups/999/release
"na"
Then Panel should get function as "Panic Alarm" and Expected response should be as "Response Code : 2
After
Back to Table of Contents
Scenario Outline: Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Arm Clear Alarm" the panel using the command as "PUT /ISOM/AC/Partitions/1/alarmStat
Then Panel should get function as "Arm Clear Alarm" and Expected response should be as "Response Co

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Arm Clear Alarm" and Expected response should be as "Response
/BasicSecurity.feature:234)
After
Back to Table of Contents
Scenario Outline: Add user and read the user details.Add Duplicate user and verify
Passed: 3 Failed: 0 Undefined: 0

Page 18 of 47
 Detailed Results Report

Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Adding User" the panel using the command as "PUT /ISOM/UserMgmt/CredentialHolders/c
User"
Then Panel should get function as "Adding User" and Expected response should be as "Response Code : 2
After
Back to Table of Contents
Scenario Outline: Add user and read the user details.Add Duplicate user and verify
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Duplicate User" the panel using the command as "PUT /ISOM/UserMgmt/CredentialHolder
"Duplicate User"
Then Panel should get function as "Duplicate User" and Expected response should be as "Response Code

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Duplicate User" and Expected response should be as "Response Co
/BasicSecurity.feature:252)
After
Back to Table of Contents
Scenario Outline: Add user and read the user details.Add Duplicate user and verify
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Added User" the panel using the command as "GET /ISOM/UserMgmt/CredentialHolders/c
dvi=12002&lastRef=1&count=10" with "na"
Then Panel should get function as "Added User" and Expected response should be as "Response Code : 2
After
Back to Table of Contents
Scenario Outline: Edit user and verify the Edited user details
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Edit User" the panel using the command as "PUT /ISOM/UserMgmt/CredentialHolders/con
Then Panel should get function as "Edit User" and Expected response should be as "Response Code : 200
After
Back to Table of Contents
Scenario Outline: Edit user and verify the Edited user details

Page 19 of 47
 Detailed Results Report

Passed: 2 Failed: 1 Undefined: 0

Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Edited User" the panel using the command as "GET /ISOM/UserMgmt/CredentialHolders/c
dvi=12002&lastRef=1&count=10" with "na"
Then Panel should get function as "Edited User" and Expected response should be as "Response Code : 2

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Edited User" and Expected response should be as "Response Code
/BasicSecurity.feature:264)
After
Back to Table of Contents
Scenario Outline: Delete user and verify the deleted user details.
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "delete User" the panel using the command as "DELETE /ISOM/UserMgmt/CredentialHolde
Then Panel should get function as "delete User" and Expected response should be as "Response Code : 20
After
Back to Table of Contents

Feature: DoorContact Test

Passed: 43 Failed: 9 Undefined: 0 Duration: 1090.4
Scenario Outline: time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
And Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_1_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_2_ Start Sensor Enrollment

Page 20 of 47
 Detailed Results Report

Passed: 2 Failed: 1 Undefined: 0

Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user enroll the sensor"DoorContact" using as "PUT /ISOM/DeviceMgmt/Peripherals/discovery/sta
(rName=peripheralConnectedToInterface&rEid=7)&added=true&count=1&duration=600" with"na"
Then Panel should get function as "SensorEnrollment" and Expected response should be as "<ExpectedR

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "SensorEnrollment" and Expected response should be as "<Expecte
/DoorContactTest.feature:50)
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_3_ Trigger the Sensor on for Enrollment
Passed: 2 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay on 0"
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_3_1_Trigger the Sensor off for Enrollment
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay off 0"
Then Panel should get function as "Triggerfault" and Expected response should be as "Response Code : 2
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_4_To Check sensor enrollment is saved and stop enrollment
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud

Page 21 of 47
 Detailed Results Report

When user enroll the sensor"DoorContact" using as "PUT /ISOM/AC/DetectorGroups/2/config?dvi=800"

SensorEnrollmentSave"
Then Panel should get function as "SensorEnrollmentSave" and Expected response should be as "<Expec
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_4_To Check sensor enrollment is saved and stop enrollment
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user enroll the sensor"DoorContact" using as "PUT /ISOM/DeviceMgmt/Peripherals/discovery/sta
Then Panel should get function as "Sensorenrollmentstop" and Expected response should be as "<Expect
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_5_Trigger the Sensor on fault
Passed: 5 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay on 1"
And Wait for "<Operation>" and sync with panel
And Wait for "<Operation>" and sync with panel
Then Panel should get function as "Triggerfault1" and Expected response should be as "Response Code :
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault
Passed: 5 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay off 1"

Page 22 of 47
 Detailed Results Report

And Wait for "<Operation>" and sync with panel

And Wait for "<Operation>" and sync with panel
Then Panel should get function as "Triggerfault2" and Expected response should be as "Response Code :
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_6_Trigger the Sensor tamper on
Passed: 4 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay on 2"
And Wait for "<Operation>" and sync with panel
And Wait for "<Operation>" and sync with panel
Then Panel should get function as "Triggerfault3" and Expected response should be as "Response Code :

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Triggerfault3" and Expected response should be as "Response Cod
/DoorContactTest.feature:166)
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_6_1_Trigger the Sensor tamper off
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay off 2"
Then Panel should get function as "Triggerfault4" and Expected response should be as "Response Code :

Page 23 of 47
 Detailed Results Report

After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_6_2_Disarm the panel and get the tamper status
Passed: 2 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_8_Bypass the Specific Zone
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "ByPass 2 zone" the panel using the command as "PUT /ISOM/AC/DetectorGroups/2/bypassS
Then Panel should get function as "ByPass 2 zone" and Expected response should be as "<ExpectedRespo
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_9_ Trigger the Sensor fault
Passed: 2 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay on 1"
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_9_1 Trigger the Sensor fault
Passed: 1 Failed: 0 Undefined: 0
Before
When user trigger the sensor fault for "DoorContact"as"relay off 1"
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_10_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_11_ Trigger the Sensor fault
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud

Page 24 of 47
 Detailed Results Report

When user trigger the sensor fault for "DoorContact"as"relay on 1"

Then Panel should get function as "Triggerfault1" and Expected response should be as "Response Code :

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Triggerfault1" and Expected response should be as "Response Cod
/DoorContactTest.feature:275)
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay off 1"
Then Panel should get function as "Triggerfault2" and Expected response should be as "Response Code :

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Triggerfault2" and Expected response should be as "Response Cod
/DoorContactTest.feature:287)
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_9_ Get the Sensor status and panel status
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When API call is made with message and command as "GET /ISOM/AC/DetectorGroups/2/state" with "n
Then Panel should get function as "Sensor State" and Expected response should be as "Response Code : 2
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_9_ Get the Sensor status and panel status
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When API call is made with message and command as "GET /ISOM/AC/Partitions/1/state" with "na"
Then Panel should get function as "Partition State" and Expected response should be as "Response Code

Page 25 of 47
 Detailed Results Report

After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_10_User to Disarm the panel
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_disarm_as_something_and_expected_respon
(StepDefinitionTest.java:447)
at .Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200O
/DoorContactTest.feature:313)
After
Back to Table of Contents
Scenario Outline: LyricDAS_1052_User to Arm Away the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Arm the panel using as "PUT /ISOM/AC/Partitions/1/setState/fullSet" with "ArmAway"
Then Panel should get Armed as "ArmAway" and Expected response should be as "Response Code : 200O
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_5_Trigger the Sensor on fault when panel is in ArmAway
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay on 1"
Then Panel should get function as "Armfault1" and Expected response should be as "Response Code : 20
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault when panel is in ArmAway
Passed: 3 Failed: 0 Undefined: 0

Page 26 of 47
 Detailed Results Report

Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay off 1"
Then Panel should get function as "Armfault2" and Expected response should be as "Response Code : 20
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_10_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: LyricDAS_1097_User to Arm Stay the panel
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Arm the panel using as "PUT /ISOM/AC/Partitions/1/setState/partSet" with "na"
Then Panel should get Armed as "ArmStay" and Expected response should be as "Response Code : 200O

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_armed_as_something_and_expected_respon
(StepDefinitionTest.java:362)
at .Then Panel should get Armed as "ArmStay" and Expected response should be as "Response Code : 20
/DoorContactTest.feature:384)
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents

Page 27 of 47
 Detailed Results Report

Scenario Outline: LyricDAS_SensorEnrollment_5_Trigger the Sensor on fault when panel is in Armstay

Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay on 1"
Then Panel should get function as "Armfault3" and Expected response should be as "Response Code : 20

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Armfault3" and Expected response should be as "Response Code :
/DoorContactTest.feature:404)
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault when panel is in Armstay
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay off 1"
Then Panel should get function as "Armfault4" and Expected response should be as "Response Code : 20
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_1_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "LED Start/Stop" and sync with panel

Page 28 of 47
 Detailed Results Report

After
Back to Table of Contents
Scenario Outline: Start/Stop LED Test and validate the response
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "LED Test Start" the panel using the command as "PUT /ISOM/DeviceMgmt/Peripherals/2/te
with "LED Test Start"
Then Panel should get function as "LED Test Start" and Expected response should be as "Response Code
After
Back to Table of Contents
Scenario Outline: Start/Stop LED Test and validate the response
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "LED Test Stop" the panel using the command as "PUT /ISOM/DeviceMgmt/Peripherals/2/te
with "LED Test Stop"
Then Panel should get function as "LED Test Stop" and Expected response should be as "Response Code
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "Range Start/Stop" and sync with panel
After
Back to Table of Contents
Scenario Outline: Start Range Test and validate the response
Passed: 2 Failed: 1 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Range Test Start" the panel using the command as "PUT /ISOM/DeviceMgmt/Peripherals/2/
duration=30" with "Range Test Start"
Then Panel should get function as "Range Test Start" and Expected response should be as "Response Cod

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Range Test Start" and Expected response should be as "Response
/DoorContactTest.feature:474)
After

Page 29 of 47
 Detailed Results Report

Back to Table of Contents

Scenario Outline: time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Range Start/Stop" and sync with panel
When Wait for "Range Start/Stop" and sync with panel
After
Back to Table of Contents
Scenario Outline: Get the Range value
Passed: 2 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When Wait for "Get Ragne value" and sync with panel
After
Back to Table of Contents
Scenario Outline: Stop Range Test and validate the response
Passed: 2 Failed: 1 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Range Test Stop" the panel using the command as "PUT /ISOM/DeviceMgmt/Peripherals/2/
with "Range Test Stop"
Then Panel should get function as "Range Test Stop" and Expected response should be as "Response Cod

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Range Test Stop" and Expected response should be as "Response C
/DoorContactTest.feature:505)
After
Back to Table of Contents
Scenario Outline: Start Walk Test and validate the response
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "WalkTest start" the panel using the command as "PUT /ISOM/DeviceMgmt/Peripherals/2/te
with "WalkTest start"
Then Panel should get function as "WalkTest start" and Expected response should be as "Response Code
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_5_Trigger the Sensor on fault

Page 30 of 47
 Detailed Results Report

Passed: 5 Failed: 0 Undefined: 0

Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay on 1"
And Wait for "<Operation>" and sync with panel
And Wait for "<Operation>" and sync with panel
Then Panel should get function as "Triggerfault1" and Expected response should be as "Response Code :
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Sensorenrollment" and sync with panel
When Wait for "Sensorenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_5_1_Trigger the Sensor off fault
Passed: 5 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for "DoorContact"as"relay off 1"
And Wait for "<Operation>" and sync with panel
And Wait for "<Operation>" and sync with panel
Then Panel should get function as "Triggerfault2" and Expected response should be as "Response Code :
After
Back to Table of Contents
Scenario Outline: Stop Walk Test and validate the response
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "WalkTest stop" the panel using the command as "PUT /ISOM/DeviceMgmt/Peripherals/2/te
with "WalkTest stop"
Then Panel should get function as "WalkTest stop" and Expected response should be as "Response Code
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_10_ Delete sensor from the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When API call is made with message and command as "DELETE /ISOM/AC/DetectorGroups/2/config" w
Then Panel should get function as "DeleteSensor" and Expected response should be as "Response Code :
After

Page 31 of 47
 Detailed Results Report

Back to Table of Contents

Feature: System Security Feature Testing

Passed: 6 Failed: 3 Undefined: 0 Duration: 488.67
Scenario Outline: LyricDAS_SensorEnrollment_10_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay 15 seconds and arm the panel , verify event after 15 sec
Passed: 2 Failed: 1 Undefined: 2
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Entry Exit delay 15" the panel using the command as "PUT /ISOM/AC/Partitions/1/config?d
Exit delay 15"
Then Panel should get function as "Entry Exit delay 15" and Expected response should be as "Response C

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Entry Exit delay 15" and Expected response should be as "Respon
/features/SystemSecurityTestcase.feature:19)
When Arm the panel using as "PUT /ISOM/AC/Partitions/1/setState/fullSet" with "ArmAway"
Then Wait for "ArmAway1" event with specified delay time "5" and Expected response should be as "Re
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_10_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay 30 seconds and arm the panel , verify event after 30 sec
Passed: 5 Failed: 0 Undefined: 0

Before

Page 32 of 47
 Detailed Results Report

Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Entry Exit delay 30" the panel using the command as "PUT /ISOM/AC/Partitions/1/config?d
Exit delay 30"
Then Panel should get function as "Entry Exit delay 30" and Expected response should be as "Response C
When Arm the panel using as "PUT /ISOM/AC/Partitions/1/setState/fullSet" with "ArmAway"
Then Wait for "ArmAway1" event with specified delay time "30" and Expected response should be as "R
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_10_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: Configure the Entry and Exit delay 45 seconds and arm the panel , verify event after 45 sec
Passed: 2 Failed: 1 Undefined: 2
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Entry Exit delay 45" the panel using the command as "PUT /ISOM/AC/Partitions/1/config?d
Exit delay 45"
Then Panel should get function as "Entry Exit delay 45" and Expected response should be as "Response C

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Entry Exit delay 45" and Expected response should be as "Respon
/features/SystemSecurityTestcase.feature:66)
When Arm the panel using as "PUT /ISOM/AC/Partitions/1/setState/fullSet" with "ArmAway"
Then Wait for "ArmAway1" event with specified delay time "65" and Expected response should be as "R
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_10_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After

Page 33 of 47
 Detailed Results Report

Back to Table of Contents

Scenario Outline: Configure the Entry and Exit delay 60 seconds and arm the panel , verify event after 60 sec
Passed: 2 Failed: 1 Undefined: 2
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When user "Entry Exit delay 60" the panel using the command as "PUT /ISOM/AC/Partitions/1/config?d
Exit delay 60"
Then Panel should get function as "Entry Exit delay 60" and Expected response should be as "Response C

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "Entry Exit delay 60" and Expected response should be as "Respon
/features/SystemSecurityTestcase.feature:89)
When Arm the panel using as "PUT /ISOM/AC/Partitions/1/setState/fullSet" with "ArmAway"
Then Wait for "ArmAway1" event with specified delay time "95" and Expected response should be as "R
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_10_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents

Feature: ZWave Functional Testing

Passed: 13 Failed: 13 Undefined: 0 Duration: 857.83
Scenario Outline: LyricDAS_SensorEnrollment_1_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Zwave Function" and sync with panel

Page 34 of 47
 Detailed Results Report

And Wait for "Zwave Function" and sync with panel

After
Back to Table of Contents
Scenario Outline: LyricDAS_180_Zwave- Send API to exclude the dimmer or multilevel switch
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Exclude" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Per
/enabled?dvi=10201&duration=60s&deleted=true" with "na"
Then Zwave switch or dimmer should get "Exclude" and done the "Exclude"with "Response Code : 200O
After
Back to Table of Contents
Scenario Outline: Zwave- Trip dimmer or multilevel switch to exclude
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for zwave "zwavedelete"as"relay on F","relay off F"
Then Panel should get function as "zwavedelete" and Expected response should be as "Response Code : 2
After
Back to Table of Contents
Scenario Outline: LyricDAS_180_Zwave- Send API to include the dimmer or multilevel switch
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Include" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Per
/enabled?dvi=10201&duration=60s&added=true" with "na"
Then Zwave switch or dimmer should get "Include" and done the "Include"with "Response Code : 200O
After
Back to Table of Contents
Scenario Outline: Zwave- Trip dimmer or multilevel switch to include
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for zwave "zwaveadd"as"relay on F","relay off F"
Then Panel should get function as "zwaveadd" and Expected response should be as "Response Code : 200

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)

Page 35 of 47
 Detailed Results Report

at .Then Panel should get function as "zwaveadd" and Expected response should be as "Response Code :
/ZwaveFUTtest.feature:61)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status o
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "DimON" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Ou
/release" with "na"
Then Zwave switch or dimmer should get "ON" and done the "DimON"with "Response Code : 200OK"

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "ON" and done the "DimON"with "Response Code : 200OK
/ZwaveFUTtest.feature:72)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status o
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "DSTATUS" the Zwave switch or dimmer using the command as "GET /ISOM/DeviceMgmt/
"na"
Then Zwave switch or dimmer should get "ON" and done the "DSTATUS"with "Response Code : 200OK

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "ON" and done the "DSTATUS"with "Response Code : 200
/ZwaveFUTtest.feature:72)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status o
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud

Page 36 of 47
 Detailed Results Report

When user "DimOFF" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Ou
/normal" with "na"
Then Zwave switch or dimmer should get "OFF" and done the "DimOFF"with "Response Code : 200OK

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "OFF" and done the "DimOFF"with "Response Code : 200
/ZwaveFUTtest.feature:72)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status o
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "DSTATUS1" the Zwave switch or dimmer using the command as "GET /ISOM/DeviceMgmt
"na"
Then Zwave switch or dimmer should get "ON" and done the "DSTATUS1"with "Response Code : 200O

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "ON" and done the "DSTATUS1"with "Response Code : 20
/ZwaveFUTtest.feature:72)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status o
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "volume" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Out
/release" with "volume"
Then Zwave switch or dimmer should get "VOLUME" and done the "volume"with "Response Code : 200

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)

Page 37 of 47
 Detailed Results Report

at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "VOLUME" and done the "volume"with "Response Code :
/ZwaveFUTtest.feature:72)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status o
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "VSTATUS" the Zwave switch or dimmer using the command as "GET /ISOM/DeviceMgmt/
"na"
Then Zwave switch or dimmer should get "ON" and done the "VSTATUS"with "Response Code : 200OK

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "ON" and done the "VSTATUS"with "Response Code : 200
/ZwaveFUTtest.feature:72)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device dimmer switch on ,set percentage and off then verify status o
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "DimOFF" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Ou
/normal" with "na"
Then Zwave switch or dimmer should get "OFF" and done the "DimOFF"with "Response Code : 200OK

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "OFF" and done the "DimOFF"with "Response Code : 200
/ZwaveFUTtest.feature:72)
After
Back to Table of Contents
Scenario Outline: LyricDAS_180_Zwave- Send API to exclude the dimmer or multilevel switch
Passed: 3 Failed: 0 Undefined: 0
Before
Page 38 of 47
 Detailed Results Report

Given Lyric DAS Panel is up and running, Connected to Cloud

When user "Exclude" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Per
/enabled?dvi=10201&duration=60s&deleted=true" with "na"
Then Zwave switch or dimmer should get "Exclude" and done the "Exclude"with "Response Code : 200O
After
Back to Table of Contents
Scenario Outline: Zwave- Trip dimmer or multilevel switch to exclude
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for zwave "zwavedelete"as"relay on F","relay off F"
Then Panel should get function as "zwavedelete" and Expected response should be as "Response Code : 2
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 2 Failed: 0 Undefined: 0
Before
When Wait for "Zwave Function" and sync with panel
And Wait for "Zwave Function" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_180_Zwave- Send API to exclude the binary switch
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Exclude" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Per
/enabled?dvi=10201&duration=60s&deleted=true" with "na"
Then Zwave switch or dimmer should get "Exclude" and done the "Exclude"with "Response Code : 200O
After
Back to Table of Contents
Scenario Outline: Zwave- Trip binary switch to exclude
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for zwave "zwavedelete"as"relay on E","relay off E"
Then Panel should get function as "zwavedelete" and Expected response should be as "Response Code : 2
After
Back to Table of Contents
Scenario Outline: LyricDAS_180_Zwave- Send API to include the binary switch
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud

Page 39 of 47
 Detailed Results Report

When user "Include" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Per
/enabled?dvi=10201&duration=60s&added=true" with "na"
Then Zwave switch or dimmer should get "Include" and done the "Include"with "Response Code : 200O
After
Back to Table of Contents
Scenario Outline: Zwave- Trip binary switch to include
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for zwave "zwaveadd"as"relay on E","relay off E"
Then Panel should get function as "zwaveadd" and Expected response should be as "Response Code : 200
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device binary switch on ,set percentage and off then verify status of
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "SwitchON" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/O
/release" with "na"
Then Zwave switch or dimmer should get "ON" and done the "SwitchON"with "Response Code : 200OK

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "ON" and done the "SwitchON"with "Response Code : 200
/ZwaveFUTtest.feature:166)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device binary switch on ,set percentage and off then verify status of
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "ZSTATUS" the Zwave switch or dimmer using the command as "GET /ISOM/DeviceMgmt/
"na"
Then Zwave switch or dimmer should get "ON" and done the "ZSTATUS"with "Response Code : 200OK

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t

Page 40 of 47
 Detailed Results Report

(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "ON" and done the "ZSTATUS"with "Response Code : 200
/ZwaveFUTtest.feature:166)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device binary switch on ,set percentage and off then verify status of
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "SwitchOFF" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/
/normal" with "na"
Then Zwave switch or dimmer should get "OFF" and done the "SwitchOFF"with "Response Code : 200O

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "OFF" and done the "SwitchOFF"with "Response Code : 2
/ZwaveFUTtest.feature:166)
After
Back to Table of Contents
Scenario Outline: LyricDAS_181_Zwave device binary switch on ,set percentage and off then verify status of
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "ZSTATUS1" the Zwave switch or dimmer using the command as "GET /ISOM/DeviceMgmt
"na"
Then Zwave switch or dimmer should get "ON" and done the "ZSTATUS1"with "Response Code : 200O

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "ON" and done the "ZSTATUS1"with "Response Code : 20
/ZwaveFUTtest.feature:166)
After
Back to Table of Contents
Scenario Outline: LyricDAS_180_Zwave- Send API to exclude the binary switch
Passed: 2 Failed: 1 Undefined: 0
Before

Page 41 of 47
 Detailed Results Report

Given Lyric DAS Panel is up and running, Connected to Cloud

When user "Exclude" the Zwave switch or dimmer using the command as "PUT /ISOM/DeviceMgmt/Per
/enabled?dvi=10201&duration=60s&deleted=true" with "na"
Then Zwave switch or dimmer should get "Exclude" and done the "Exclude"with "Response Code : 200O

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.zwave_switch_or_dimmer_should_get_something_and_done_t
(StepDefinitionTest.java:874)
at .Then Zwave switch or dimmer should get "Exclude" and done the "Exclude"with "Response Code : 2
/ZwaveFUTtest.feature:179)
After
Back to Table of Contents
Scenario Outline: Zwave- Trip binary switch to exclude
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for zwave "zwavedelete"as"relay on E","relay off E"
Then Panel should get function as "zwavedelete" and Expected response should be as "Response Code : 2
After
Back to Table of Contents

Feature: Keyfob Test

Passed: 13 Failed: 8 Undefined: 0 Duration: 402.84
Scenario Outline: LyricDAS_SensorEnrollment_1_User to Disarm the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When Disarm the panel using as "PUT /ISOM/AC/Partitions/1/setState/unSet" with "na"
Then Panel should get disarm as "Disarm" and Expected response should be as "Response Code : 200OK
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_2_ Start Sensor Enrollment for keyfob
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user enroll the sensor"Keyfob" using as "PUT /ISOM/DeviceMgmt/Peripherals/discovery/state/ena
(rName=peripheralConnectedToInterface&rEid=7)&added=true&count=1&duration=600" with"na"
Then Panel should get function as "KeyfobEnrollment1" and Expected response should be as "<Expected
After
Back to Table of Contents
Scenario Outline: Time synchronization to panel

Page 42 of 47
 Detailed Results Report

Passed: 2 Failed: 0 Undefined: 0

Before
When Wait for "sensor enroll" and sync with panel
And Wait for "sensor enroll" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_3_ Trigger the keyfob Sensor Enrollment
Passed: 3 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for keyfob as "keyfob"as"relay on 3","relay on 4"
And Wait for "keyfob" and sync with panel
Then Panel should get function as "KeyfobEnrollment" and Expected response should be as "Response C

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "KeyfobEnrollment" and Expected response should be as "Respons
/keyfobTest.feature:42)
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_3_1_Trigger the Sensor for Enrollment
Passed: 1 Failed: 0 Undefined: 0
Before
When user trigger the sensor fault for keyfob as "DoorContact"as"relay off 3","relay off 4"
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "keyfobenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_4_To Check sensor enrollment is saved and stop enrollment
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user enroll the sensor"keyfob" using as "PUT /ISOM/DeviceMgmt/KeyFobs/131/config?dvi=1200"
keyfobEnrollmentSave"
Then Panel should get function as "keyfobEnrollmentSave" and Expected response should be as "<Expec

Page 43 of 47
 Detailed Results Report

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "keyfobEnrollmentSave" and Expected response should be as "<Ex
/features/keyfobTest.feature:70)
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_4_To Check sensor enrollment is saved and stop enrollment
Passed: 3 Failed: 0 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user enroll the sensor"keyfob" using as "PUT /ISOM/DeviceMgmt/Peripherals/discovery/state/disa
Then Panel should get function as "keyfobenrollmentstop" and Expected response should be as "<Expect
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "keyfobenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_5_Press the keyfob button for ArmAway
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for keyfob as "keyfob"as"relay on 3","relay off 3"
Then Panel should get function as "keyfobfault1" and Expected response should be as "Response Code : 2

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "keyfobfault1" and Expected response should be as "Response Code
/keyfobTest.feature:92)
After
Back to Table of Contents
Scenario Outline: time synchronization to panel

Page 44 of 47
 Detailed Results Report

Passed: 1 Failed: 0 Undefined: 0

Before
When Wait for "keyfobenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_6_Press the keyfob button for Disarm
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for keyfob as "keyfob"as"relay on 4","relay off 4"
Then Panel should get function as "keyfobfault2" and Expected response should be as "Response Code : 2

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "keyfobfault2" and Expected response should be as "Response Code
/keyfobTest.feature:112)
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "keyfobenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_7_Press the keyfob button for ArmStay
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for keyfob as "keyfob"as"relay on 5","relay off 5"
Then Panel should get function as "keyfobfault3" and Expected response should be as "Response Code : 2

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "keyfobfault3" and Expected response should be as "Response Code
/keyfobTest.feature:131)

Page 45 of 47
 Detailed Results Report

After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "keyfobenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_8_Press the keyfob button for panic
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for keyfob as "keyfob"as"relay on 6","relay off 6"
Then Panel should get function as "keyfobfault4" and Expected response should be as "Response Code : 2

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "keyfobfault4" and Expected response should be as "Response Code
/keyfobTest.feature:150)
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "keyfobenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: Panic/Clear Alaram in Disarm then Panic/Clear Alaram in ArmAway
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user "Arm Clear Alarm" the panel using the command as "PUT /ISOM/AC/Partitions/1/alarmStat
Then Panel should get function as "Arm Clear Alarm" and Expected response should be as "Response Co

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo

Page 46 of 47
 Detailed Results Report

(StepDefinitionTest.java:700)
at .Then Panel should get function as "Arm Clear Alarm" and Expected response should be as "Response
/keyfobTest.feature:169)
After
Back to Table of Contents
Scenario Outline: time synchronization to panel
Passed: 1 Failed: 0 Undefined: 0
Before
When Wait for "keyfobenrollment" and sync with panel
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_6_Press the keyfob button for Disarm
Passed: 2 Failed: 1 Undefined: 0
Before
Given Lyric DAS Panel is up and running, Connected to Cloud
When user trigger the sensor fault for keyfob as "keyfob"as"relay on 4","relay off 4"
Then Panel should get function as "keyfobfault2" and Expected response should be as "Response Code : 2

java.lang.AssertionError: expected:<false> but was:<true>

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at cucumberMobiletest.StepDefinitionTest.panel_should_get_function_as_something_and_expected_respo
(StepDefinitionTest.java:700)
at .Then Panel should get function as "keyfobfault2" and Expected response should be as "Response Code
/keyfobTest.feature:190)
After
Back to Table of Contents
Scenario Outline: LyricDAS_SensorEnrollment_11_ Delete keyfob from the panel
Passed: 3 Failed: 0 Undefined: 0
Before
Given lyric DAS system up running,connected to IOT cloud and Disarmed with no fault/trouble
When API call is made with message and command as "DELETE /ISOM/DeviceMgmt/KeyFobs/131/conf
Then Panel should get function as "DeletekeyfobSensor" and Expected response should be as "Response C
After
Back to Table of Contents

Page 47 of 47