Test Result

336 failures (+32) , 3,234 skipped (-313)
9,118 tests (-253)
Took 2 hr 24 min.

All Failed Tests

Test NameDurationAge
 Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The First Time.And Command pwd is executed1 ms1
 Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The First Time2 ms1
 Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The First Time.And Command invalidCommand is executed2 ms1
 Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The First Time3 ms1
 Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The Second Time.And Command pwd is executed1 ms1
 Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Command Execution", multiple devices And Step Index=0 For The Second Time2 ms1
 Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The Second Time.And Command invalidCommand is executed2 ms1
 Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Command Execution", multiple devices And Step Index=0 For The Second Time2 ms1
 Scenario: Restarting Job With Valid "Bundle Start", multiple devices And Step Index=0 For The First Time.Then Devices status is "CONNECTED"4 ms1
 Scenario: Restarting Job With Valid "Bundle Start", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Bundle Start", multiple devices And Step Index=0 For The First Time5 ms1
 Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The First Time.Then Devices status is "CONNECTED"5 ms1
 Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The First Time7 ms1
 Scenario: Restarting Job With Valid "Bundle Start", multiple devicess And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Bundle Start", multiple devicess And Step Index=0 For The Second Time4 ms1
 Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The Second Time5 ms1
 Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The First Time4 ms1
 Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The First Time4 ms1
 Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The Second Time4 ms1
 Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The Second Time5 ms1
 Scenario: Starting job with valid Command Execution and Bundle Start steps.Scenario: Starting job with valid Command Execution and Bundle Start steps5 ms1
 Scenario: Starting job with invalid Command Execution and Bundle Start steps.Scenario: Starting job with invalid Command Execution and Bundle Start steps6 ms1
 Scenario: Starting job with valid Command Execution step and multiple devices.Scenario: Starting job with valid Command Execution step and multiple devices2 ms1
 Scenario: Starting job with invalid Command Execution step and multiple devices.Scenario: Starting job with invalid Command Execution step and multiple devices0 ms1
 Scenario: Starting job with valid Bundle Start step and multiple devices.Scenario: Starting job with valid Bundle Start step and multiple devices4 ms1
 Scenario: Starting job with invalid Bundle Start step and multiple devices.Scenario: Starting job with invalid Bundle Start step and multiple devices4 ms1
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.Scenario: Starting a job with valid Bundle Stop step and multiple devices3 ms1
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.Scenario: Starting a job with invalid Bundle Stop step and multiple devices1 ms1
 Scenario: Starting job with valid Command Execution, valid Bundle Start steps and multiple devices.Scenario: Starting job with valid Command Execution, valid Bundle Start steps and multiple devices3 ms1
 Scenario: Starting job with invalid Command Execution, invalid Bundle Start steps and multiple devices.Scenario: Starting job with invalid Command Execution, invalid Bundle Start steps and multiple devices16 ms1
 Scenario: Starting a job with two valid Bundle Start steps and multiple devices.Scenario: Starting a job with two valid Bundle Start steps and multiple devices3 ms1
 Scenario: Starting a job with two invalid Bundle Start steps and multiple devices.Scenario: Starting a job with two invalid Bundle Start steps and multiple devices4 ms1
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps and multiple devices.Scenario: Starting a job with valid Bundle Stop and Bundle Start steps and multiple devices3 ms1
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps and multiple devices.Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps and multiple devices4 ms1
 Scenario: Restarting job with Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Start step and multiple devices6 ms2
 Scenario: Restarting job with Bundle Stop step and multiple devices.Scenario: Restarting job with Bundle Stop step and multiple devices3 ms2
 Scenario: Restarting job with Package Download/Install step and multiple devices.Scenario: Restarting job with Package Download/Install step and multiple devices4 ms2
 Scenario: Restarting job with Package Uninstall step and multiple device.Scenario: Restarting job with Package Uninstall step and multiple device3 ms2
 Scenario: Restarting job with Asset Write step and multiple devices.Scenario: Restarting job with Asset Write step and multiple devices4 ms2
 Scenario: Restarting job with Configuration Put step and multiple devices.Scenario: Restarting job with Configuration Put step and multiple devices3 ms2
 Scenario: Restarting job with Command Execution step and multiple devices.Scenario: Restarting job with Command Execution step and multiple devices3 ms2
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Scenario: Restarting job with two Bundle Start steps and multiple devices4 ms2
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices5 ms2
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device5 ms2
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices4 ms2
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices5 ms2
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices5 ms2
 Scenario: Restarting job with Command Execution step.Scenario: Restarting job with Command Execution step2 ms3
 Scenario: Restarting job with Asset Write step.Scenario: Restarting job with Asset Write step2 ms3
 Scenario: Restarting job with Configuration Put step.Scenario: Restarting job with Configuration Put step2 ms3
 Scenario: Restarting job with Bundle Start step.Scenario: Restarting job with Bundle Start step4 ms3
 Scenario: Restarting job with Bundle Stop step.Scenario: Restarting job with Bundle Stop step3 ms3
 Scenario: Restarting job with Package Install step.Scenario: Restarting job with Package Install step0 ms3
 Scenario: Restarting job with Package Uninstall step.Scenario: Restarting job with Package Uninstall step5 ms3
 Scenario: Restarting job with two Bundle Start steps.Scenario: Restarting job with two Bundle Start steps3 ms3
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Scenario: Restarting job with Bundle Stop and Bundle Start steps3 ms3
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices6 ms3
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices6 ms3
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Scenario: Restarting a job with Package Uninstall and Bundle Start steps5 ms3
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Scenario: Restarting a job with Command Execution and Bundle Start steps4 ms3
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Scenario: Restarting a job with Asset Write and Bundle Start steps4 ms3
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Scenario: Restarting a job with Configuration Put and Bundle Start steps5 ms3
 Scenario: Starting job with Bundle Start step and multiple devices.Scenario: Starting job with Bundle Start step and multiple devices2 ms7
 Scenario: Starting job with Bundle Stop step and multiple devices.Scenario: Starting job with Bundle Stop step and multiple devices2 ms7
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices4 ms7
 Scenario: Starting job with Package Uninstall step and multiple device.Scenario: Starting job with Package Uninstall step and multiple device2 ms7
 Scenario: Starting job with Asset Write step and multiple devices.Scenario: Starting job with Asset Write step and multiple devices2 ms7
 Scenario: Starting job with Configuration Put step and multiple devices.Scenario: Starting job with Configuration Put step and multiple devices2 ms7
 Scenario: Starting job with Command Execution step and multiple devices.Scenario: Starting job with Command Execution step and multiple devices0 ms7
 Scenario: Starting job with two Bundle Start steps and multiple devices.Scenario: Starting job with two Bundle Start steps and multiple devices2 ms7
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices1 ms7
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices5 ms7
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device2 ms7
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices2 ms7
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices2 ms7
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices2 ms7
 Scenario: Find correct number of messages by corresponding metric.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms8
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric13 ms8
 Scenario: Finding correct number of messages by corresponding two metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms8
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics2 ms8
 Scenario: Finding all messages by selecting all metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms8
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics2 ms8
 Scenario: Finding messages with incorrect metric parameters.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms8
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters3 ms8
 Scenario: Find correct number of messages by corresponding metric.Then I prepare a number of messages with the following details and remember the list as "TestMessages"2 ms8
 Scenario: Find correct number of messages by corresponding metric.Scenario: Find correct number of messages by corresponding metric2 ms8
 Scenario: Finding correct number of messages by corresponding two metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms8
 Scenario: Finding correct number of messages by corresponding two metrics.Scenario: Finding correct number of messages by corresponding two metrics1 ms8
 Scenario: Finding all messages by selecting all metrics.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms8
 Scenario: Finding all messages by selecting all metrics.Scenario: Finding all messages by selecting all metrics1 ms8
 Scenario: Finding messages with incorrect metric parameters.Then I prepare a number of messages with the following details and remember the list as "TestMessages"1 ms8
 Scenario: Finding messages with incorrect metric parameters.Scenario: Finding messages with incorrect metric parameters2 ms8
 Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The First Time2 ms8
 Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The First Time2 ms8
 Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The Second Time2 ms8
 Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The Second Time2 ms8
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The First Time4 ms8
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time4 ms8
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time5 ms8
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time4 ms8
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The First Time.Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The First Time4 ms8
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time.Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time6 ms8
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The Second Time.Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The Second Time2 ms8
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time.Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time4 ms8
 Scenario: Starting job with Bundle Start step and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Bundle Stop step and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Package Uninstall step and multiple device.Then I count 21 ms8
 Scenario: Starting job with Asset Write step and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Configuration Put step and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Command Execution step and multiple devices.Then I count 20 ms8
 Scenario: Starting job with two Bundle Start steps and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device.Then I count 21 ms8
 Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices.Then I count 21 ms8
 Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices.Then I count 22 ms8
 Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices.Then I count 21 ms8
 Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step2 ms9
 Scenario: Starting a job with invalid Command Execution step.Scenario: Starting a job with invalid Command Execution step2 ms9
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step1 ms9
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step5 ms9
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step6 ms9
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step6 ms9
 Scenario: Starting a job with two valid Bundle Start steps.Scenario: Starting a job with two valid Bundle Start steps3 ms9
 Scenario: Starting a job with two invalid Bundle Start steps.Scenario: Starting a job with two invalid Bundle Start steps4 ms9
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps.Scenario: Starting a job with valid Bundle Stop and Bundle Start steps3 ms9
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps.Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps3 ms9
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Given Start Broker2 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms10
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The Second Time.And Bundles are requested4 ms10
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The Second Time.And Bundles are requested2 ms10
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The First Time.And Bundles are requested2 ms10
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The First Time.And Bundles are requested4 ms10
 Scenario: Restarting Job With Valid "Bundle Stop" And Step Index=0 For The Second Time.And Bundles are requested1 ms10
 Scenario: Restarting Job With Invalid "Bundle Stop" And Step Index=0 For The Second Time.And Bundles are requested3 ms10
 Scenario: Restarting Job With Valid "Bundle Start", multiple devicess And Step Index=0 For The Second Time.And Bundles are requested3 ms10
 Scenario: Restarting Job With Invalid "Bundle Start", multiple devices And Step Index=0 For The Second Time.And Bundles are requested4 ms10
 Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The First Time.And Bundles are requested3 ms10
 Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The First Time.And Bundles are requested2 ms10
 Scenario: Restarting Job With Valid "Bundle Stop", multiple devices And Step Index=0 For The Second Time.And Bundles are requested3 ms10
 Scenario: Restarting Job With Invalid "Bundle Stop", multiple devices And Step Index=0 For The Second Time.And Bundles are requested3 ms10
 Scenario: Starting a job with Command Execution step.Scenario: Starting a job with Command Execution step4 ms10
 Scenario: Starting a job with Asset Write step.Scenario: Starting a job with Asset Write step4 ms10
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step5 ms10
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested6 ms10
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step7 ms10
 Scenario: Starting a job with Configuration Put step.Scenario: Starting a job with Configuration Put step2 ms10
 Scenario: Starting a job with Package Install Command step.Scenario: Starting a job with Package Install Command step4 ms10
 Scenario: Starting a job with Package Uninstall Command step.Scenario: Starting a job with Package Uninstall Command step3 ms10
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps5 ms10
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps5 ms10
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps5 ms10
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested4 ms10
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps6 ms10
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested3 ms10
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps4 ms10
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps7 ms10
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps4 ms10
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested4 ms10
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested4 ms10
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps.And Bundles are requested2 ms10
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps.And Bundles are requested2 ms10
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.And Bundles are requested1 ms10
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.And Bundles are requested1 ms10
 Scenario: Starting a job with valid Bundle Stop and Bundle Start steps and multiple devices.And Bundles are requested2 ms10
 Scenario: Starting a job with invalid Bundle Stop and Bundle Start steps and multiple devices.And Bundles are requested2 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms10
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms10
 Scenario: Start broker for all scenarios.Given Start Broker1 ms15
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms15
 Scenario: Start broker for all scenarios.Given Start Broker1 ms15
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms15
 Scenario: Start broker for all scenarios.Given Start Broker0 ms15
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios0 ms15
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms17
 Scenario: Start broker for all scenarios.Given Start Broker4 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios6 ms17
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"7 ms17
 Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed8 ms17
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"3 ms17
 Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY5 ms17
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown2 ms17
 Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account7 ms17
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Then An exception was thrown2 ms17
 Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed4 ms17
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"4 ms17
 Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms17
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown2 ms17
 Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms17
 Scenario: Start broker for all scenarios.Given Start Broker16 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios16 ms17
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"4 ms17
 Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY5 ms17
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"4 ms17
 Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY5 ms17
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown1 ms17
 Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account.Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account3 ms17
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Then An exception was thrown6 ms17
 Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed8 ms17
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"3 ms17
 Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed4 ms17
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"3 ms17
 Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed5 ms17
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown5 ms17
 Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed6 ms17
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"6 ms17
 Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms17
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown3 ms17
 Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms17
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"4 ms17
 Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY5 ms17
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"4 ms17
 Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY5 ms17
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown15 ms17
 Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account15 ms17
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms17
 Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed4 ms17
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"4 ms17
 Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed5 ms17
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown2 ms17
 Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed4 ms17
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"2 ms17
 Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed4 ms17
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY"3 ms17
 Scenario: DV1 Data view publish to CTRL_ACC_REPLY.Scenario: DV1 Data view publish to CTRL_ACC_REPLY4 ms17
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Then Broker receives string "Hello broker" on topic "$EDC/acme/client-1/CONF-V1/REPLY/foo"3 ms17
 Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY5 ms17
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Then An exception was thrown1 ms17
 Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account.Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account3 ms17
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Then An exception was thrown4 ms17
 Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed.Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms17
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme"2 ms17
 Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed4 ms17
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"9 ms17
 Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed10 ms17
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Then Broker receives string "Hello broker" on topic "$EDC/acme/foo/bar/NOTIFY/client-1"4 ms17
 Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms17
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Then An exception was thrown6 ms17
 Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed8 ms17
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms17
 Scenario: Send BIRTH message and then DC message.And Bundles are requested2 ms17
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message3 ms17
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms17
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Then Device is connected with "localhost" server ip1 ms17
 Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Scenario: Send BIRTH message and then DC message while broker ip is set by config file2 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms17
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Then Device is connected with "localhost" server ip1 ms17
 Scenario: Send BIRTH message and then DC message while broker ip is set by System.Scenario: Send BIRTH message and then DC message while broker ip is set by System2 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms17
 Scenario: Stealing link scenario.Scenario: Stealing link scenario6 ms17
 Scenario: Start broker for all scenarios.Given Start Broker1 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios1 ms17
 Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds2 ms17
 Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data3 ms17
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios2 ms17
 Scenario: Start broker for all scenarios.Given Start Broker2 ms17
 Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios3 ms17
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Then Device sim-1 for account kapua-sys is registered after 5 seconds4 ms17
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Scenario: Starting and stopping the simulator should create a device entry and properly set its status6 ms17
 Scenario: Installing a package.Then Device sim-1 for account kapua-sys is registered after 5 seconds5 ms17
 Scenario: Installing a package.Scenario: Installing a package7 ms17
 Scenario: Stealing link scenario.And Client named "client-2" is not connected4 ms542
 Scenario: Restarting job with Command Execution step.And A new job target item1 ms542
 Scenario: Restarting job with Asset Write step.And A new job target item1 ms542
 Scenario: Restarting job with Configuration Put step.And A new job target item2 ms542
 Scenario: Restarting job with Bundle Start step.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Bundle Stop step.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with Package Install step.Then Device status is "CONNECTED"0 ms542
 Scenario: Restarting job with Package Uninstall step.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with two Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with Bundle Stop and Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting a job with Package Uninstall and Bundle Start steps.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting a job with Command Execution and Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting a job with Asset Write and Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting a job with Configuration Put and Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with Bundle Start step and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Bundle Stop step and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with Package Download/Install step and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Package Uninstall step and multiple device.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with Asset Write step and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Configuration Put step and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Command Execution step and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting job with two Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"4 ms542
 Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The First Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The First Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Restarting Job With Valid "Command Execution" And Step Index=0 For The Second Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Restarting Job With Invalid "Command Execution" And Step Index=0 For The Second Time.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Restarting Job With Valid "Bundle Start" And Step Index=0 For The First Time.Then Device status is "CONNECTED"2 ms542
 Scenario: Restarting Job With Invalid "Bundle Start" And Step Index=0 For The First Time.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with Command Execution step.And A new job target item2 ms542
 Scenario: Starting a job with Asset Write step.And A new job target item2 ms542
 Scenario: Starting a job with Bundle Start step.Then Device status is "CONNECTED"4 ms542
 Scenario: Starting a job with Configuration Put step.And A new job target item1 ms542
 Scenario: Starting a job with Package Install Command step.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with Package Uninstall Command step.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting a job with Command Execution and Bundle Start steps.Then Device status is "CONNECTED"4 ms542
 Scenario: Starting a job with Asset Write and Bundle Start steps.Then Device status is "CONNECTED"4 ms542
 Scenario: Starting a job with two Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with Package Install and Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting job with Package Download/Install step and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with valid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Starting a job with invalid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"1 ms542
 Scenario: Starting a job with valid Bundle Start step.Then Device status is "CONNECTED"1 ms542
 Scenario: Starting a job with invalid Bundle Start step.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting job with valid Command Execution and Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting job with invalid Command Execution and Bundle Start steps.Then Device status is "CONNECTED"4 ms542
 Scenario: Starting a job with two valid Bundle Start steps.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting a job with two invalid Bundle Start steps.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting job with valid Command Execution step and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting job with invalid Command Execution step and multiple devices.Then Device status is "CONNECTED"0 ms542
 Scenario: Starting job with valid Bundle Start step and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting job with invalid Bundle Start step and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting job with valid Command Execution, valid Bundle Start steps and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting job with invalid Command Execution, invalid Bundle Start steps and multiple devices.Then Device status is "CONNECTED"3 ms542
 Scenario: Starting a job with two valid Bundle Start steps and multiple devices.Then Device status is "CONNECTED"2 ms542
 Scenario: Starting a job with two invalid Bundle Start steps and multiple devices.Then Device status is "CONNECTED"2 ms542

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)8.4 sec336+323222-3125249+288807-252
org.eclipse.kapua64 ms0033
org.eclipse.kapua.broker.core.plugin3.4 sec001515
org.eclipse.kapua.client.gateway54 ms004343
org.eclipse.kapua.client.gateway.kura0.2 sec001414
org.eclipse.kapua.client.gateway.spi.util2.7 sec001515
org.eclipse.kapua.client.gateway.util1 ms0033
org.eclipse.kapua.commons.about0.28 sec0011
org.eclipse.kapua.commons.configuration65 ms0011
org.eclipse.kapua.commons.configuration.metatype11 ms001919
org.eclipse.kapua.commons.liquibase1.9 sec0044
org.eclipse.kapua.commons.metric4 ms0022
org.eclipse.kapua.commons.model0.13 sec0088
org.eclipse.kapua.commons.model.id5 ms0011
org.eclipse.kapua.commons.security2.8 sec0033
org.eclipse.kapua.commons.setting1 ms0044
org.eclipse.kapua.commons.util35 ms003838
org.eclipse.kapua.commons.util.xml0.26 sec0099
org.eclipse.kapua.integration.service.datastoreJunit0 ms0505
org.eclipse.kapua.kura.simulator.main.simulation5.4 sec001313
org.eclipse.kapua.locator.internal0.18 sec021012
org.eclipse.kapua.message.internal0.24 sec022628
org.eclipse.kapua.message.internal.device.data0 ms0033
org.eclipse.kapua.message.internal.device.lifecycle56 ms002121
org.eclipse.kapua.message.internal.xml1 sec001111
org.eclipse.kapua.service.datastore.test.junit0.16 sec0044
org.eclipse.kapua.service.datastore.test.junit.client0.28 sec0077
org.eclipse.kapua.service.datastore.test.junit.clientTransport58 ms031922
org.eclipse.kapua.service.device.management.commons.message.notification7 ms0022