[Jenkins]Jenkins

Test Result

242 failures (+238) , 2,739 skipped (+2697)
19,844 tests (+599)
Took 2 hr 3 min.

All Failed Tests

Test NameDurationAge
 org.eclipse.kapua.broker.core.plugin.ConnectorDescriptorTest.defaultProviderWithDisabledDefaultDescriptorTest19 ms1
 org.eclipse.kapua.broker.core.plugin.ConnectorDescriptorTest.defaultProviderAllowingDefaultFallbackTest4 ms1
 Scenario: Start Jetty server for all scenarios.Given Start Jetty Server on host "127.0.0.1" at port "8081"3 ms1
 Scenario: Start Jetty server for all scenarios.Scenario: Start Jetty server for all scenarios4 ms1
 Scenario: Simple Jetty with rest-api war.When REST POST call at "/v1/authentication/user" with JSON "{"password": "kapua-password", "username": "kapua-sys"}"2 ms1
 Scenario: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war3 ms1
 Scenario: Bug when user can retrieve user in another account if it has other account's user id.Then REST POST call at "/v1/authentication/user" with JSON "{"password": "ToManySecrets123#", "username": "kapua-a"}"1 ms1
 Scenario: Bug when user can retrieve user in another account if it has other account's user id.Scenario: Bug when user can retrieve user in another account if it has other account's user id2 ms1
 Scenario: Send BIRTH message and then DC message.And Packages are requested6 ms1
 Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message8 ms1
 Scenario: Starting and stopping the simulator should create a device entry and properly set its status.When I fetch the bundle states21 ms1
 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 status24 ms1
 Scenario: Installing a package.When I fetch the package states4 ms1
 Scenario: Installing a package.Scenario: Installing a package6 ms1
 Scenario: Starting a job with Bundle Start step.And Bundles are requested5 ms1
 Scenario: Starting a job with Bundle Start step.Scenario: Starting a job with Bundle Start step7 ms1
 Scenario: Starting a job with Bundle Stop step.And Bundles are requested4 ms1
 Scenario: Starting a job with Bundle Stop step.Scenario: Starting a job with Bundle Stop step6 ms1
 Scenario: Starting a job with Package Install step.And Packages are requested and 1 package is received5 ms1
 Scenario: Starting a job with Package Install step.Scenario: Starting a job with Package Install step7 ms1
 Scenario: Starting a job with Package Uninstall step.And Packages are requested and 1 package is received0 ms1
 Scenario: Starting a job with Package Uninstall step.Scenario: Starting a job with Package Uninstall step1 ms1
 Scenario: Starting a job with Command Execution and Bundle Start steps.And Bundles are requested3 ms1
 Scenario: Starting a job with Command Execution and Bundle Start steps.Scenario: Starting a job with Command Execution and Bundle Start steps5 ms1
 Scenario: Starting a job with Asset Write and Bundle Start steps.And Bundles are requested3 ms1
 Scenario: Starting a job with Asset Write and Bundle Start steps.Scenario: Starting a job with Asset Write and Bundle Start steps5 ms1
 Scenario: Starting a job with two Bundle Start steps.And Bundles are requested4 ms1
 Scenario: Starting a job with two Bundle Start steps.Scenario: Starting a job with two Bundle Start steps5 ms1
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.And Bundles are requested5 ms1
 Scenario: Starting a job with Bundle Stop and Bundle Start steps.Scenario: Starting a job with Bundle Stop and Bundle Start steps7 ms1
 Scenario: Starting a job with Configuration Put and Bundle Start steps.And Bundles are requested2 ms1
 Scenario: Starting a job with Configuration Put and Bundle Start steps.Scenario: Starting a job with Configuration Put and Bundle Start steps4 ms1
 Scenario: Starting a job with Package Install and Bundle Start steps.And Packages are requested and 1 package is received3 ms1
 Scenario: Starting a job with Package Install and Bundle Start steps.Scenario: Starting a job with Package Install and Bundle Start steps6 ms1
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.And Packages are requested and 1 package is received3 ms1
 Scenario: Starting a job with Package Uninstall and Bundle Start steps.Scenario: Starting a job with Package Uninstall and Bundle Start steps6 ms1
 Scenario: Starting job with Package Download/Install step and multiple devices.And Packages are requested and 1 package is received5 ms1
 Scenario: Starting job with Package Download/Install step and multiple devices.Scenario: Starting job with Package Download/Install step and multiple devices8 ms1
 Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices.And Packages are requested and 1 package is received5 ms1
 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 devices7 ms1
 Scenario: Restarting job with valid Command Execution step two times.Then I find 2 or more device events3 ms1
 Scenario: Restarting job with valid Command Execution step two times.Scenario: Restarting job with valid Command Execution step two times4 ms1
 Scenario: Restarting job with valid Bundle Start step two times.And Bundles are requested5 ms1
 Scenario: Restarting job with valid Bundle Start step two times.Scenario: Restarting job with valid Bundle Start step two times7 ms1
 Scenario: Restarting job with invalid Bundle Start step two times.And Bundles are requested4 ms1
 Scenario: Restarting job with invalid Bundle Start step two times.Scenario: Restarting job with invalid Bundle Start step two times6 ms1
 Scenario: Restarting job with valid Bundle Stop step two times.And Bundles are requested1 ms1
 Scenario: Restarting job with valid Bundle Stop step two times.Scenario: Restarting job with valid Bundle Stop step two times3 ms1
 Scenario: Restarting job with invalid Bundle Stop step two times.And Bundles are requested4 ms1
 Scenario: Restarting job with invalid Bundle Stop step two times.Scenario: Restarting job with invalid Bundle Stop step two times5 ms1
 Scenario: Restarting a job with valid Package Uninstall step two times.Then Packages are requested and 1 package is received3 ms1
 Scenario: Restarting a job with valid Package Uninstall step two times.Scenario: Restarting a job with valid Package Uninstall step two times5 ms1
 Scenario: Restarting a job with invalid Package Uninstall step two times.Then Packages are requested and 1 package is received5 ms1
 Scenario: Restarting a job with invalid Package Uninstall step two times.Scenario: Restarting a job with invalid Package Uninstall step two times8 ms1
 Scenario: Restarting job with valid Command Execution and Package Install steps two times.And Command pwd is executed4 ms1
 Scenario: Restarting job with valid Command Execution and Package Install steps two times.Scenario: Restarting job with valid Command Execution and Package Install steps two times6 ms1
 Scenario: Restarting job with invalid Command Execution and Package Install step two times.And Command pwd is executed2 ms1
 Scenario: Restarting job with invalid Command Execution and Package Install step two times.Scenario: Restarting job with invalid Command Execution and Package Install step two times4 ms1
 Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times.And Bundles are requested4 ms1
 Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times.Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times5 ms1
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times.And Bundles are requested0 ms1
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times.Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times0 ms1
 Scenario: Restarting job with valid Command Execution step and multiple devices two times.And Command pwd is executed5 ms1
 Scenario: Restarting job with valid Command Execution step and multiple devices two times.Scenario: Restarting job with valid Command Execution step and multiple devices two times8 ms1
 Scenario: Restarting job with invalid Command Execution step and multiple devices two times.And Command pwd is executed0 ms1
 Scenario: Restarting job with invalid Command Execution step and multiple devices two times.Scenario: Restarting job with invalid Command Execution step and multiple devices two times0 ms1
 Scenario: Restarting job with valid Bundle Start step and multiple devices two times.And Bundles are requested0 ms1
 Scenario: Restarting job with valid Bundle Start step and multiple devices two times.Scenario: Restarting job with valid Bundle Start step and multiple devices two times2 ms1
 Scenario: Restarting job with invalid Bundle Start step and multiple devices two times.And Bundles are requested3 ms1
 Scenario: Restarting job with invalid Bundle Start step and multiple devices two times.Scenario: Restarting job with invalid Bundle Start step and multiple devices two times5 ms1
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.And Bundles are requested0 ms1
 Scenario: Restarting job with valid Bundle Stop step and multiple devices two times.Scenario: Restarting job with valid Bundle Stop step and multiple devices two times1 ms1
 Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times.And Bundles are requested3 ms1
 Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times.Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times4 ms1
 Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times.Then Packages are requested and 1 package is received5 ms1
 Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times.Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times11 ms1
 Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times.Then Packages are requested and 1 package is received6 ms1
 Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times.Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times9 ms1
 Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed3 ms1
 Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times.Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times5 ms1
 Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times.And Command pwd is executed5 ms1
 Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times.Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times9 ms1
 Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested2 ms1
 Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times.Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times4 ms1
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times.And Bundles are requested5 ms1
 Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times.Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times7 ms1
 Scenario: Restarting a job with valid Configuration Put step two times.Then Configuration is requested4 ms1
 Scenario: Restarting a job with valid Configuration Put step two times.Scenario: Restarting a job with valid Configuration Put step two times6 ms1
 Scenario: Restarting a job with invalid Configuration Put step two times.Then Configuration is requested1 ms1
 Scenario: Restarting a job with invalid Configuration Put step two times.Scenario: Restarting a job with invalid Configuration Put step two times1 ms1
 Scenario: Restarting a job with valid Package Install step two times.And Packages are requested and 1 package is received4 ms1
 Scenario: Restarting a job with valid Package Install step two times.Scenario: Restarting a job with valid Package Install step two times6 ms1
 Scenario: Restarting a job with invalid Package Install step two times.And Packages are requested and 1 package is received4 ms1
 Scenario: Restarting a job with invalid Package Install step two times.Scenario: Restarting a job with invalid Package Install step two times5 ms1
 Scenario: Restarting job With valid Asset Write step two times.And Device assets are requested0 ms1
 Scenario: Restarting job With valid Asset Write step two times.Scenario: Restarting job With valid Asset Write step two times0 ms1
 Scenario: Restarting job with invalid Asset Write step two times.And Device assets are requested3 ms1
 Scenario: Restarting job with invalid Asset Write step two times.Scenario: Restarting job with invalid Asset Write step two times5 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Then Configuration is requested6 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps two times9 ms1
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Then Configuration is requested1 ms1
 Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times.Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times1 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.And Device assets are requested3 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times5 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.And Device assets are requested0 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times0 ms1
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.Then Configuration is requested5 ms1
 Scenario: Restarting a job with valid Configuration Put step and multiple devices two times.Scenario: Restarting a job with valid Configuration Put step and multiple devices two times7 ms1
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.Then Configuration is requested3 ms1
 Scenario: Restarting a job with invalid Configuration Put and multiple devices two times.Scenario: Restarting a job with invalid Configuration Put and multiple devices two times5 ms1
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.And Packages are requested and 1 package is received4 ms1
 Scenario: Restarting a job with valid Package Install step and multiple devices two times.Scenario: Restarting a job with valid Package Install step and multiple devices two times6 ms1
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.And Packages are requested and 1 package is received3 ms1
 Scenario: Restarting a job with invalid Package Install step and multiple devices two times.Scenario: Restarting a job with invalid Package Install step and multiple devices two times5 ms1
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.And Device assets are requested2 ms1
 Scenario: Restarting job with valid Asset Write step and multiple devices two times.Scenario: Restarting job with valid Asset Write step and multiple devices two times4 ms1
 Scenario: Restarting job With invalid Asset Write and multiple two times.And Device assets are requested3 ms1
 Scenario: Restarting job With invalid Asset Write and multiple two times.Scenario: Restarting job With invalid Asset Write and multiple two times5 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested5 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times8 ms1
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested5 ms1
 Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times.Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times7 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.And Packages are requested and 1 package is received5 ms1
 Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times8 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.And Packages are requested and 1 package is received4 ms1
 Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times.Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times6 ms1
 Scenario: Starting a job with valid Command Execution step.Then I find 2 device events6 ms1
 Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step8 ms1
 Scenario: Starting a job with valid Bundle Start step.And Bundles are requested6 ms1
 Scenario: Starting a job with valid Bundle Start step.Scenario: Starting a job with valid Bundle Start step8 ms1
 Scenario: Starting a job with invalid Bundle Start step.And Bundles are requested6 ms1
 Scenario: Starting a job with invalid Bundle Start step.Scenario: Starting a job with invalid Bundle Start step9 ms1
 Scenario: Starting a job with valid Bundle Stop step.And Bundles are requested6 ms1
 Scenario: Starting a job with valid Bundle Stop step.Scenario: Starting a job with valid Bundle Stop step9 ms1
 Scenario: Starting a job with invalid Bundle Stop step.And Bundles are requested3 ms1
 Scenario: Starting a job with invalid Bundle Stop step.Scenario: Starting a job with invalid Bundle Stop step6 ms1
 Scenario: Starting a job with valid Configuration Put step.When Configuration is requested0 ms1
 Scenario: Starting a job with valid Configuration Put step.Scenario: Starting a job with valid Configuration Put step0 ms1
 Scenario: Starting a job with invalid Configuration Put step.When Configuration is requested3 ms1
 Scenario: Starting a job with invalid Configuration Put step.Scenario: Starting a job with invalid Configuration Put step5 ms1
 Scenario: Starting a job with valid Package Install step.And Packages are requested and 1 package is received5 ms1
 Scenario: Starting a job with valid Package Install step.Scenario: Starting a job with valid Package Install step7 ms1
 Scenario: Starting a job with invalid Package Install step.And Packages are requested and 1 package is received0 ms1
 Scenario: Starting a job with invalid Package Install step.Scenario: Starting a job with invalid Package Install step0 ms1
 Scenario: Starting a job with valid Asset Write step.When Device assets are requested6 ms1
 Scenario: Starting a job with valid Asset Write step.Scenario: Starting a job with valid Asset Write step8 ms1
 Scenario: Starting a job with invalid Asset Write step.And Device assets are requested3 ms1
 Scenario: Starting a job with invalid Asset Write step.Scenario: Starting a job with invalid Asset Write step6 ms1
 Scenario: Starting a job with valid Package Uninstall step.And Packages are requested and 1 package is received5 ms1
 Scenario: Starting a job with valid Package Uninstall step.Scenario: Starting a job with valid Package Uninstall step7 ms1
 Scenario: Starting a job with invalid Package Uninstall step.And Packages are requested and 1 package is received0 ms1
 Scenario: Starting a job with invalid Package Uninstall step.Scenario: Starting a job with invalid Package Uninstall step1 ms1
 Scenario: Starting job with valid Command Execution and Package Install steps.And Command "pwd" is executed4 ms1
 Scenario: Starting job with valid Command Execution and Package Install steps.Scenario: Starting job with valid Command Execution and Package Install steps6 ms1
 Scenario: Starting job with invalid Command Execution and Package Install steps.And Command "pwd" is executed4 ms1
 Scenario: Starting job with invalid Command Execution and Package Install steps.Scenario: Starting job with invalid Command Execution and Package Install steps6 ms1
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.And Bundles are requested5 ms1
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps.Scenario: Starting a job with valid Bundle Start and Bundle Stop steps6 ms1
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.And Bundles are requested0 ms1
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps.Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps0 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps.And Configuration is requested6 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps.Scenario: Starting job with valid Configuration Put and Command Execution steps8 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Then Configuration is requested6 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps.Scenario: Starting job with invalid Configuration Put and Command Execution steps9 ms1
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.When Device assets are requested0 ms1
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps.Scenario: Starting a job with valid Package Uninstall and Asset Write steps1 ms1
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.When Device assets are requested4 ms1
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps.Scenario: Starting a job with invalid Package Uninstall and Asset Write steps7 ms1
 Scenario: Starting job with valid Command Execution step and multiple devices.And Command "pwd" is executed5 ms1
 Scenario: Starting job with valid Command Execution step and multiple devices.Scenario: Starting job with valid Command Execution step and multiple devices7 ms1
 Scenario: Starting job with invalid Command Execution step and multiple devices.And Command "pwd" is executed4 ms1
 Scenario: Starting job with invalid Command Execution step and multiple devices.Scenario: Starting job with invalid Command Execution step and multiple devices6 ms1
 Scenario: Starting job with valid Bundle Start step and multiple devices.And Bundles are requested1 ms1
 Scenario: Starting job with valid Bundle Start step and multiple devices.Scenario: Starting job with valid Bundle Start step and multiple devices1 ms1
 Scenario: Starting job with invalid Bundle Start step and multiple devices.And Bundles are requested4 ms1
 Scenario: Starting job with invalid Bundle Start step and multiple devices.Scenario: Starting job with invalid Bundle Start step and multiple devices6 ms1
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.And Bundles are requested0 ms1
 Scenario: Starting a job with valid Bundle Stop step and multiple devices.Scenario: Starting a job with valid Bundle Stop step and multiple devices0 ms1
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.And Bundles are requested4 ms1
 Scenario: Starting a job with invalid Bundle Stop step and multiple devices.Scenario: Starting a job with invalid Bundle Stop step and multiple devices6 ms1
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Then Configuration is requested0 ms1
 Scenario: Starting a job with valid Configuration Put step and multiple devices.Scenario: Starting a job with valid Configuration Put step and multiple devices1 ms1
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Then Configuration is requested3 ms1
 Scenario: Starting a job with invalid Configuration Put step and multiple devices.Scenario: Starting a job with invalid Configuration Put step and multiple devices5 ms1
 Scenario: Starting a job with valid Asset Write step and multiple targets.And Device assets are requested3 ms1
 Scenario: Starting a job with valid Asset Write step and multiple targets.Scenario: Starting a job with valid Asset Write step and multiple targets6 ms1
 Scenario: Starting a job with invalid Asset Write step and multiple targets.And Device assets are requested3 ms1
 Scenario: Starting a job with invalid Asset Write step and multiple targets.Scenario: Starting a job with invalid Asset Write step and multiple targets5 ms1
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.And Packages are requested and 1 package is received4 ms1
 Scenario: Starting a job with valid Package Uninstall step and multiple targets.Scenario: Starting a job with valid Package Uninstall step and multiple targets6 ms1
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.And Packages are requested and 1 package is received4 ms1
 Scenario: Starting a job with invalid Package Uninstall step and multiple targets.Scenario: Starting a job with invalid Package Uninstall step and multiple targets6 ms1
 Scenario: Starting a job with valid Package Install step and multiple devices.Then Packages are requested and 1 package is received6 ms1
 Scenario: Starting a job with valid Package Install step and multiple devices.Scenario: Starting a job with valid Package Install step and multiple devices8 ms1
 Scenario: Starting a job with invalid Package Install step and multiple devices.And Packages are requested and 1 package is received5 ms1
 Scenario: Starting a job with invalid Package Install step and multiple devices.Scenario: Starting a job with invalid Package Install step and multiple devices7 ms1
 Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices.And Command "pwd" is executed5 ms1
 Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices.Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices7 ms1
 Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices.And Command "pwd" is executed4 ms1
 Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices.Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices6 ms1
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested4 ms1
 Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices.Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices6 ms1
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices.And Bundles are requested0 ms1
 Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices.Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices0 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested4 ms1
 Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices.Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices6 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested0 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices.Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices0 ms1
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.And Packages are requested and 1 package is received6 ms1
 Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices7 ms1
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices.And Packages are requested and 1 package is received5 ms1
 Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices.Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices7 ms1
 Scenario: Stop job with multiple Bundle Start and Package Install steps and one target.And Bundles are requested5 ms1
 Scenario: Stop job with multiple Bundle Start and Package Install steps and one target.Scenario: Stop job with multiple Bundle Start and Package Install steps and one target7 ms1
 Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target.And Bundles are requested4 ms1
 Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target.Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target5 ms1
 Scenario: Stop job with multiple Command Execution and Package Install steps and one target.And Command pwd is executed5 ms1
 Scenario: Stop job with multiple Command Execution and Package Install steps and one target.Scenario: Stop job with multiple Command Execution and Package Install steps and one target7 ms1
 Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target.And Configuration is requested5 ms1
 Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target.Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target8 ms1
 Scenario: Stop job with multiple Asset Write and Package Install steps and one target.When Device assets are requested10 ms1
 Scenario: Stop job with multiple Asset Write and Package Install steps and one target.Scenario: Stop job with multiple Asset Write and Package Install steps and one target12 ms1
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.And Bundles are requested6 ms1
 Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.Scenario: Stop job with multiple targets and Bundle Start and Package Install steps8 ms1
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.And Bundles are requested0 ms1
 Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps2 ms1
 Scenario: Stop job with multiple targets and Command Execution and Package Install steps.And Command pwd is executed5 ms1
 Scenario: Stop job with multiple targets and Command Execution and Package Install steps.Scenario: Stop job with multiple targets and Command Execution and Package Install steps7 ms1
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.And Configuration is requested0 ms1
 Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps1 ms1
 Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target.When Device assets are requested3 ms1
 Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target.Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target5 ms1
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.And I confirm the step index is 0 and status is "PROCESS_OK"3 ms1
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.Scenario: Executing Job When Device Connected After The Specified Start Date And Time5 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.And I confirm the step index is 0 and status is "PROCESS_OK"4 ms1
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time6 ms1
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events5 ms1
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device7 ms1
 Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT"2 ms6
 Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage3 ms6
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"9 ms19
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description10 ms19

All Tests

PackageDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
(root)18 sec240+2362729+269713592-288616561+47
Scenario: Creating And Account Without "8 ms0066
org.eclipse.kapua0.22 sec00106106
org.eclipse.kapua.broker4 ms0077
org.eclipse.kapua.broker.core0.47 sec0099
org.eclipse.kapua.broker.core.converter0.21 sec0074+7474+74
org.eclipse.kapua.broker.core.listener29 ms002424
org.eclipse.kapua.broker.core.message0.18 sec004141
org.eclipse.kapua.broker.core.message.system33 ms0077
org.eclipse.kapua.broker.core.plugin2.4 sec2+2082+584+7
org.eclipse.kapua.broker.core.plugin.authentication0 ms0011
org.eclipse.kapua.broker.core.plugin.authorization18 ms001414
org.eclipse.kapua.broker.core.plugin.metric9 ms0099
org.eclipse.kapua.broker.core.pool0.45 sec003434
org.eclipse.kapua.broker.core.router0.33 sec0071+5571+55
org.eclipse.kapua.broker.core.security37 ms002222
org.eclipse.kapua.broker.core.setting2 ms0044
org.eclipse.kapua.client.gateway85 ms006262
org.eclipse.kapua.client.gateway.kura0.14 sec003535
org.eclipse.kapua.client.gateway.kura.internal83 ms002222
org.eclipse.kapua.client.gateway.mqtt0.38 sec004141
org.eclipse.kapua.client.gateway.mqtt.fuse0.27 sec002121
org.eclipse.kapua.client.gateway.mqtt.fuse.internal0.22 sec0044
org.eclipse.kapua.client.gateway.mqtt.paho.internal0.29 sec001818
org.eclipse.kapua.client.gateway.profile.kura0.45 sec001616
org.eclipse.kapua.client.gateway.spi0.43 sec00241241
org.eclipse.kapua.client.gateway.spi.util5 sec008888
org.eclipse.kapua.client.gateway.util1 ms0033
org.eclipse.kapua.commons.about0.54 sec001212
org.eclipse.kapua.commons.cache0.12 sec0088
org.eclipse.kapua.commons.configuration16 ms00137137
org.eclipse.kapua.commons.configuration.metatype5 ms00134134
org.eclipse.kapua.commons.event10 ms003939
org.eclipse.kapua.commons.liquibase0.68 sec0044
org.eclipse.kapua.commons.metric0.26 sec0066
org.eclipse.kapua.commons.model91 ms004848
org.eclipse.kapua.commons.model.id0.16 sec002424
org.eclipse.kapua.commons.model.query0.18 sec00119119
org.eclipse.kapua.commons.model.query.predicate20 ms002929
org.eclipse.kapua.commons.security2.8 sec0033
org.eclipse.kapua.commons.service.event.store.internal30 ms002323
org.eclipse.kapua.commons.service.internal.cache23 ms002222
org.eclipse.kapua.commons.service.internal.cache.dummy7 ms005555
org.eclipse.kapua.commons.setting45 ms00101101
org.eclipse.kapua.commons.setting.system1 ms0044
org.eclipse.kapua.commons.util0.5 sec00166166
org.eclipse.kapua.commons.util.log0.75 sec002727
org.eclipse.kapua.commons.util.xml0.52 sec001212
org.eclipse.kapua.entity0 ms0022
org.eclipse.kapua.event3 ms001616
org.eclipse.kapua.integration.misc18 sec01487+253488+253
org.eclipse.kapua.integration.service.datastoreJunit0 ms0505
org.eclipse.kapua.kura.simulator.main.simulation5.5 sec001313
org.eclipse.kapua.locator0 ms001010
org.eclipse.kapua.locator.internal0.12 sec021012
org.eclipse.kapua.message.internal0.24 sec022628
org.eclipse.kapua.message.internal.device.data1 ms0033
org.eclipse.kapua.message.internal.device.lifecycle7 ms001717
org.eclipse.kapua.message.internal.xml1 sec001111
org.eclipse.kapua.model1 ms0011
org.eclipse.kapua.model.domain1 ms0022
org.eclipse.kapua.model.id0 ms0044
org.eclipse.kapua.model.query2 ms0022
org.eclipse.kapua.model.type11 ms001717
org.eclipse.kapua.model.xml13 ms001919
org.eclipse.kapua.service.authentication.credential.mfa.shiro80 ms005151
org.eclipse.kapua.service.authentication.credential.shiro0.12 sec003737
org.eclipse.kapua.service.authentication.shiro33 ms002626
org.eclipse.kapua.service.authentication.shiro.exceptions71 ms001414
org.eclipse.kapua.service.authentication.shiro.mfa27 sec001414
org.eclipse.kapua.service.authentication.shiro.realm0.78 sec002727
org.eclipse.kapua.service.authentication.shiro.registration0.3 sec0066
org.eclipse.kapua.service.authentication.shiro.setting7 ms0066
org.eclipse.kapua.service.authentication.shiro.utils3.3 sec001919
org.eclipse.kapua.service.authentication.token.shiro0.93 sec003939
org.eclipse.kapua.service.authorization.access.shiro57 ms0085+5385+53
org.eclipse.kapua.service.authorization.domain.shiro20 ms0041+4141+41
org.eclipse.kapua.service.authorization.group.shiro11 ms002525
org.eclipse.kapua.service.authorization.role.shiro14 ms0038+3838+38
org.eclipse.kapua.service.authorization.shiro11 ms005+55+5
org.eclipse.kapua.service.authorization.shiro.exception3 ms0013+1313+13
org.eclipse.kapua.service.authorization.shiro.setting2 ms003+33+3
org.eclipse.kapua.service.config49 ms001313
org.eclipse.kapua.service.datastore.test.junit0.16 sec0066
org.eclipse.kapua.service.datastore.test.junit.utils0.27 sec0077
org.eclipse.kapua.service.device.management.commons.message.notification8 ms0022
org.eclipse.kapua.service.elasticsearch.client.transport3 sec0055
org.eclipse.kapua.service.elasticsearch.client.utils0.34 sec0033
org.eclipse.kapua.service.stream5 ms0044
org.eclipse.kapua.transport.exception35 ms0029+929+9
org.eclipse.kapua.transport.mqtt.test.message.mqtt23 ms002323
org.eclipse.kapua.transport.mqtt.test.mqtt1 ms0088
org.eclipse.kapua.transport.mqtt.test.mqtt.exception99 ms004343
org.eclipse.kapua.transport.utils19 ms004+14+1