Test Result : (root)

240 failures (+236) , 2,729 skipped (+2697)
16,561 tests (+47)
Took 18 sec.

All Failed Tests

Test NameDurationAge
 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: 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: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description10 ms19
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"9 ms19
 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: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device7 ms1
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events5 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: Installing a package.Scenario: Installing a package6 ms1
 Scenario: Installing a package.When I fetch the package states4 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 invalid Configuration Put and multiple devices two times.Then Configuration is requested3 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 invalid Configuration Put step two times.Then Configuration is requested1 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 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 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 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 two times.Scenario: Restarting a job with invalid Package Uninstall step two times8 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 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 valid Configuration Put step and multiple devices two times.Then Configuration is requested5 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 valid Configuration Put step two times.Then Configuration is requested4 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 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 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 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 two times.Scenario: Restarting a job with valid Package Uninstall 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 invalid Configuration Put and Command Execution steps and multiple devices two times.Then Configuration is requested5 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: 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 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 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 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 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 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 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 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 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 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 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 valid Command Execution step two times.Scenario: Restarting job with valid Command Execution step two times4 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 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 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 two times.Scenario: Restarting job with valid Configuration Put and Command Execution steps two times9 ms1
 Scenario: Restarting job with valid Configuration Put and Command Execution steps two times.Then Configuration is requested6 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 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: 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: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war3 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: 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: 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 invalid Configuration Put step.Scenario: Starting a job with invalid Configuration Put step5 ms1
 Scenario: Starting a job with invalid Configuration Put step.When 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 invalid Configuration Put step and multiple devices.Then Configuration is requested3 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 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 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 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 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: 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 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 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 valid Asset Write step.Scenario: Starting a job with valid Asset Write step8 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 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 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 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 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 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 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 valid Command Execution step.Scenario: Starting a job with valid Command Execution step8 ms1
 Scenario: Starting a job with valid Command Execution step.Then I find 2 device events6 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 valid Configuration Put step.When 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 valid Configuration Put step and multiple devices.Then Configuration is requested0 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 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 valid Package Install step and multiple devices.Then Packages are requested and 1 package is received6 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 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 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 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 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 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: Starting and stopping the simulator should create a device entry and properly set its status.When I fetch the bundle states21 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: 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 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 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 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 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 job with invalid Configuration Put and Command Execution steps.Scenario: Starting job with invalid Configuration Put and Command Execution steps9 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 and multiple devices.Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices0 ms1
 Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested0 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 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 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 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 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 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 valid Configuration Put and Command Execution steps and multiple devices.Then Configuration is requested4 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 Asset Write and Package Install steps and one target.When Device assets are requested10 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 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: 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 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

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope7 ms0044
Scenario: A newly created account must have some metadata5 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic14 ms0088
Scenario: Access info service sanity checks5 ms0044
Scenario: Access service comparison sanity checks5 ms0033
Scenario: Account based ClientInfo data check34 ms002424
Scenario: Account exactly on its expiration date9 ms001414
Scenario: Account name must not be mutable6 ms0066
Scenario: Account past its expiration date16 ms001414
Scenario: Account wide metrics check28 ms002828
Scenario: Account with future expiration date8 ms001313
Scenario: Account with no expiration date15 ms001313
Scenario: Add Access Info domain permissions to new user20 ms002626
Scenario: Add Account permissions to the role in child account18 ms002828
Scenario: Add Credential domain permissions to new user10 ms001818
Scenario: Add Datastore domain permissions to new user0.56 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user13 ms001111
Scenario: Add Device Connection domain permissions to new user16 ms002323
Scenario: Add Device Event domain permissions to new user16 ms001616
Scenario: Add Device domain permissions to new user16 ms001717
Scenario: Add Domain domain permissions to kapua-sys user12 ms001717
Scenario: Add Domain domain permissions to new user15 ms003232
Scenario: Add Endpoint Permission To The User12 ms003030
Scenario: Add Endpoint_info permissions to the role in child account12 ms003030
Scenario: Add Group domain permissions to new user15 ms001717
Scenario: Add Group permissions to the role in child account13 ms002626
Scenario: Add Job domain permissions to new user12 ms001919
Scenario: Add Role domain permissions to new user24 ms001717
Scenario: Add Role permissions to the role in child account19 ms002626
Scenario: Add Scheduler Permissions With Job Permissions13 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions11 ms002121
Scenario: Add Scheduler permissions to the role in child account16 ms003636
Scenario: Add Tag domain permissions to new user13 ms001515
Scenario: Add Tag permissions to the role in child account15 ms002626
Scenario: Add User domain permissions to new user13 ms002020
Scenario: Add account permissions to the role22 ms001919
Scenario: Add admin role to the user20 ms004444
Scenario: Add and delete Account permissions from the "admin" role17 ms001414
Scenario: Add and delete Device permissions from the "admin" role10 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role12 ms001414
Scenario: Add and delete Group permissions from the "admin" role17 ms001414
Scenario: Add and delete Job permissions from the "admin" role12 ms001414
Scenario: Add and delete Role permissions from the "admin" role15 ms001414
Scenario: Add and delete User permissions from the "admin" role10 ms001515
Scenario: Add datastore permissions to the role17 ms002727
Scenario: Add deleted role again17 ms001010
Scenario: Add device event permissions to the role13 ms003232
Scenario: Add device permissions to the role12 ms001919
Scenario: Add device permissions to the role in child account12 ms002626
Scenario: Add domain, user and access_info permissions to the role38 ms002323
Scenario: Add endpoint_info permissions to the role17 ms003131
Scenario: Add group permissions to the role12 ms001818
Scenario: Add job permissions to the role16 ms001919
Scenario: Add job permissions to the role in child account11 ms002626
Scenario: Add role permissions to the role20 ms001919
Scenario: Add same permission twice to the same role12 ms001414
Scenario: Add same role to user twice18 ms001313
Scenario: Add scheduler permissions to the role15 ms003131
Scenario: Add tag permissions to the role9 ms001818
Scenario: Add user permissions to the role12 ms001919
Scenario: Add user permissions to the role in child account10 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters21 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value5 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format17 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only6 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time19 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter6 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter18 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only4 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time9 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter6 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters8 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only9 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time11 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name6 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name6 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only6 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter6 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name6 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter7 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only13 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time9 ms001111
Scenario: Adding "Device Connect" Schedule Without Name5 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter6 ms0099
Scenario: Adding "Empty" Tag To Device4 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters9 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only17 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time7 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name7 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name6 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only7 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter18 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name7 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter10 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number18 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only7 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time5 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number19 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter6 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name9 ms001111
Scenario: Adding "admin" role to a user in a child account14 ms001414
Scenario: Adding "admin" role to multiple users12 ms001818
Scenario: Adding "admin" role twice13 ms001313
Scenario: Adding Account:Delete permission to user in same scope11 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope41 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope10 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope11 ms001919
Scenario: Adding Account:Read permission to user in same scope12 ms002323
Scenario: Adding Account:Read permission to user in sub-account scope10 ms002929
Scenario: Adding Account:Write and Account:Delete permission to user in same scope11 ms002323
Scenario: Adding Account:Write permission to user in same scope11 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope9 ms003131
Scenario: Adding Multiple Permissions To User13 ms002020
Scenario: Adding One Permission To User20 ms001111
Scenario: Adding Permissions To Child User14 ms001818
Scenario: Adding Permissions To Parallel User12 ms001818
Scenario: Adding Previously Deleted Permission12 ms002828
Scenario: Adding Previously Deleted Tag From Device Again6 ms001111
Scenario: Adding Regular Device to a Group With Description9 ms001010
Scenario: Adding Regular Device to a Group Without a Description11 ms001212
Scenario: Adding Regular Group Without Description to Device4 ms001010
Scenario: Adding Regular Tag Without Description To Device7 ms0066
Scenario: Adding Same Regular Group Without Description to Device6 ms001414
Scenario: Adding Tag With Long Name Without Description To Device4 ms0066
Scenario: Adding Tag With Numbers Without Description To Device3 ms0066
Scenario: Adding Tag With Short Name Without Description To Device7 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device7 ms0066
Scenario: Adding all Account permissions to user in same scope12 ms001717
Scenario: Adding all Account permissions to user in sub-account scope10 ms002424
Scenario: Adding existing roles to user12 ms001515
Scenario: Adding role from child account to user in new child account18 ms001515
Scenario: Adding role to multiple users in child account11 ms001818
Scenario: Adding same role twice to user in child account11 ms001515
Scenario: Adding the same role to user twice in child account13 ms001313
Scenario: All device parameters must match the device creator5 ms0033
Scenario: Assign 100 Devices to One Group13 ms001111
Scenario: B1 Broker publish to CTRL_ACC_REPLY28 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed15 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed11 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI19 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed18 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed8 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY24 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY17 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account13 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed17 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed11 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed9 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI20 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed18 ms0099
Scenario: Basic Device Event queries10 ms001010
Scenario: Birth and applications event handling7 ms001212
Scenario: Birth and death message handling9 ms001212
Scenario: Birth and missing event handling5 ms001212
Scenario: Birth message handling from a new device10 ms001313
Scenario: Birth message handling from an existing device6 ms001212
Scenario: Both the parent and child accounts do not expire12 ms001111
Scenario: Both the parent and child accounts have the same expiration date10 ms001111
Scenario: Bug when user can retrieve user in another account if it has other account's user id3 ms2+212+1219+1933+33
Scenario: Captured date based ClientInfo data check33 ms003030
Scenario: Case sensitiveness of named device searches5 ms0044
Scenario: Change an existing step name3 ms001111
Scenario: Change role name so it is too short3 ms0066
Scenario: Change the account parent path3 ms0055
Scenario: Changing Client ID19 ms0099
Scenario: Changing Description On Group With Long Description6 ms0077
Scenario: Changing Description On Group With Long Name11 ms0077
Scenario: Changing Description On Group With Numbers In Name5 ms001010
Scenario: Changing Description On Group With Permitted Symbols12 ms0077
Scenario: Changing Description On Group With Short Description5 ms0077
Scenario: Changing Description On Group With Short Name5 ms0077
Scenario: Changing Description On Tag With Long Description6 ms0044
Scenario: Changing Description On Tag With Long Name4 ms0055
Scenario: Changing Description On Tag With Numbers In Name6 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name4 ms0044
Scenario: Changing Description On Tag With Short Description5 ms0044
Scenario: Changing Description On Tag With Short Name4 ms0044
Scenario: Changing Device Status To Disabled14 ms0099
Scenario: Changing Device Status To Enabled15 ms0099
Scenario: Changing Group's Description To Non-Uniqe One6 ms0077
Scenario: Changing Group's Description To Uniqe One4 ms0077
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description5 ms0088
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description6 ms0077
Scenario: Changing Group's Name To Non-Unique One7 ms0099
Scenario: Changing Group's Name To Short One Without Changing Description8 ms0077
Scenario: Changing Group's Name To Unique One6 ms0077
Scenario: Changing Group's Name To a Long One Without Changing Description5 ms0077
Scenario: Changing Group's Name To a Too Long One Without Changing Description7 ms0088
Scenario: Changing Group's Name To a Too Short One Without Changing Description8 ms0088
Scenario: Changing Tag's Description To Non-Unique One8 ms0055
Scenario: Changing Tag's Description To Unique One6 ms0077
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description5 ms0055
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description4 ms0055
Scenario: Changing Tag's Name To Non-Unique One9 ms0066
Scenario: Changing Tag's Name To Short One Without Description7 ms0077
Scenario: Changing Tag's Name To Unique One6 ms0077
Scenario: Changing Tag's Name To a Long One Without Description4 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description6 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description5 ms0055
Scenario: Changing description of a nonexisting role5 ms0077
Scenario: Changing job description to non-unique one5 ms0077
Scenario: Changing job description to the long one12 ms0066
Scenario: Changing job description to unique one6 ms0066
Scenario: Changing job description to very short one6 ms0077
Scenario: Changing job name to a long one without description8 ms0077
Scenario: Changing job name to a too long one without description5 ms0055
Scenario: Changing job name to a too short one without description12 ms0066
Scenario: Changing job name to contain invalid symbols in name without description7 ms0044
Scenario: Changing job name to contain permitted symbols in name without description11 ms0055
Scenario: Changing job name to non-unique one6 ms0088
Scenario: Changing job name to short one without description8 ms0077
Scenario: Changing job name to unique one10 ms0099
Scenario: Changing name of a nonexisting role7 ms0077
Scenario: Changing role description to a valid one3 ms0066
Scenario: Changing role name so it is too long5 ms0066
Scenario: Changing role name to contain special character3 ms0044
Scenario: Changing role name to null2 ms0066
Scenario: Changing role's name to a valid one7 ms0066
Scenario: Channel info queries based on datastore channel filters29 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id24 ms002828
Scenario: ChannelInfo client ID based on the account id29 ms002626
Scenario: ChannelInfo last published date31 ms003030
Scenario: ChannelInfo topic data based on the account id30 ms002626
Scenario: Check account properties6 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency41 ms003030
Scenario: Check the mapping for message semantic topics38 ms003030
Scenario: Check the message store35 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization4 ms0022
Scenario: Child account expires after parent9 ms0099
Scenario: Child account expires before parent17 ms001111
Scenario: Child account has null expiration date8 ms0099
Scenario: Client Id based ClientInfo data check37 ms002828
Scenario: Compare domain entries6 ms0033
Scenario: Connect to the system and publish some data0.34 sec002222
Scenario: Connection Service factory sanity checks1 ms0022
Scenario: Count access info entities in a specific scope5 ms002424
Scenario: Count access role entities by scope8 ms003939
Scenario: Count connections in empty scope4 ms0044
Scenario: Count connections in scope4 ms0055
Scenario: Count devices with a specific BIOS version7 ms0066
Scenario: Count domains in a blank database9 ms0044
Scenario: Count domains in the database13 ms0077
Scenario: Count events in empty scope5 ms0066
Scenario: Count groups10 ms001414
Scenario: Count groups in a blank database5 ms0055
Scenario: Count job items6 ms0077
Scenario: Count job items in wrong - empty - scope4 ms0088
Scenario: Count role permissions in specific scopes11 ms001818
Scenario: Count roles in specific scopes5 ms001515
Scenario: Count step definition items6 ms0044
Scenario: Count step definitions in wrong (empty) scope5 ms0011
Scenario: Count steps in the database4 ms001414
Scenario: Count user6 ms0066
Scenario: Counting created roles items in the DB4 ms0055
Scenario: Create a regular event25 ms0088
Scenario: Create a single device with an empty string for clientID6 ms0044
Scenario: Create a single device with null clientID value6 ms0044
Scenario: Create a valid job entry44 ms0066
Scenario: Create an event with a null scope ID10 ms0077
Scenario: Create and count several execution items for a job6 ms001111
Scenario: Create index with specific prefix26 ms001212
Scenario: Create multiple users3 ms0055
Scenario: Create regular access permissions17 ms002020
Scenario: Create same user in different accounts16 ms001515
Scenario: Create scheduler with correct end date7 ms0088
Scenario: Create scheduler with empty schedule name15 ms0088
Scenario: Create scheduler with end date before start date7 ms0099
Scenario: Create scheduler with invalid Retry Interval property11 ms0099
Scenario: Create scheduler with invalid cron job trigger property6 ms0099
Scenario: Create scheduler with invalid schedule name13 ms0088
Scenario: Create scheduler with short schedule name10 ms0088
Scenario: Create scheduler with too long schedule name12 ms0088
Scenario: Create scheduler with valid Retry Interval property7 ms0077
Scenario: Create scheduler with valid cron job trigger property14 ms0077
Scenario: Create scheduler with valid schedule name33 ms0066
Scenario: Create scheduler without Cron Job Trigger property5 ms0099
Scenario: Create scheduler without Retry Interval property7 ms0099
Scenario: Create scheduler without start date11 ms0077
Scenario: Create some regular role permissions5 ms0099
Scenario: Create user that already exist6 ms0077
Scenario: Create user that has more than DB allowed length8 ms0055
Scenario: Create user with short name9 ms0055
Scenario: Create user with special characters in his name18 ms0055
Scenario: Create with permissions12 ms001414
Scenario: Create with permissions and a role7 ms001717
Scenario: Create with permissions and a role in the wrong scope6 ms001515
Scenario: Creating 100 Sub-accounts While InfiniteChildAccounts Is Set To True7 ms0077
Scenario: Creating A Device With Disabled Status5 ms0077
Scenario: Creating A Device With Enabled Status6 ms0077
Scenario: Creating A Device With Long Display Name6 ms0077
Scenario: Creating A Device With Long Name5 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols11 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols7 ms0077
Scenario: Creating A Device With No Name7 ms0088
Scenario: Creating A Device With Non-unique Display Name12 ms0077
Scenario: Creating A Device With Non-unique Name5 ms001010
Scenario: Creating A Device With Short Display Name14 ms0077
Scenario: Creating A Device With Short Name8 ms0077
Scenario: Creating A Device With Too Long Display Name4 ms0088
Scenario: Creating A Device With Too Long Name7 ms0088
Scenario: Creating A Device With Unique Name11 ms0099
Scenario: Creating A Valid Account8 ms0055
Scenario: Creating An Account With Long Name9 ms0055
Scenario: Creating An Account With Long Organization Name10 ms0055
Scenario: Creating An Account With Non-unique Name17 ms0088
Scenario: Creating An Account With Numbers And Valid Symbols In Name5 ms0055
Scenario: Creating An Account With Short Name8 ms0055
Scenario: Creating An Account With Short Organization Name8 ms0055
Scenario: Creating An Account With Special Symbols In Organization Name10 ms0055
Scenario: Creating An Account With Too Long Organization Name7 ms0066
Scenario: Creating An Account With Unique Name18 ms0077
Scenario: Creating An Account With Wrong TLD Format In Email5 ms001010
Scenario: Creating An Account Without Email9 ms0066
Scenario: Creating An Account Without Name5 ms0066
Scenario: Creating An Account Without Ogranization Name11 ms0066
Scenario: Creating And Account Without "@" In Email6 ms0066
Scenario: Creating Devices And Than Setting Device Service So It Does Not Allow Devices10 ms001212
Scenario: Creating Devices And Then Changing Device Service Values8 ms001010
Scenario: Creating Devices Under Account That Allows Infinite Child Devices9 ms001010
Scenario: Creating Devices Under Account That Does Not Allow Devices9 ms0099
Scenario: Creating Devices Under Account That Has Limited Child Devices10 ms001313
Scenario: Creating Endpoint Non-Unique "Domain Name"6 ms0088
Scenario: Creating Endpoint Non-Unique "Port"4 ms0088
Scenario: Creating Endpoint Non-Unique "Schema"4 ms0099
Scenario: Creating Endpoint With "Domain Name" Only4 ms0066
Scenario: Creating Endpoint With "Port" Only7 ms0066
Scenario: Creating Endpoint With "Schema" Only6 ms0066
Scenario: Creating Endpoint With Disabled Secure Field4 ms0066
Scenario: Creating Endpoint With Enabled Secure Field6 ms0066
Scenario: Creating Endpoint With Invalid "Domain Name"6 ms0066
Scenario: Creating Endpoint With Invalid "Schema" containing symbols2 ms0066
Scenario: Creating Endpoint With Long "Domain Name"2 ms0055
Scenario: Creating Endpoint With Max Length "Port"6 ms0055
Scenario: Creating Endpoint With NULL parameters5 ms0066
Scenario: Creating Endpoint With Schema Containing "http://"4 ms0066
Scenario: Creating Endpoint With Schema Containing "https://"3 ms0066
Scenario: Creating Endpoint With Short "Domain Name"5 ms0066
Scenario: Creating Endpoint With Short "Schema"5 ms0066
Scenario: Creating Endpoint With Small Number "Port"6 ms0066
Scenario: Creating Endpoint With Too Big "Port"4 ms0066
Scenario: Creating Endpoint With Too Long "Domain Name"5 ms0066
Scenario: Creating Endpoint With Too Long "Schema"5 ms0066
Scenario: Creating Endpoint Without "Domain Name"4 ms0066
Scenario: Creating Endpoint Without "Port"4 ms0066
Scenario: Creating Endpoint Without "Schema"7 ms0066
Scenario: Creating Endpoint Without Long "Schema"5 ms0055
Scenario: Creating Endpoint with invalid "Schema" which contains only numbers5 ms0066
Scenario: Creating Group Invalid Symbols In Name Without Description5 ms0077
Scenario: Creating Group With Invalid Symbols In Name With Valid Description5 ms0077
Scenario: Creating Group With Long Name With Valid Description11 ms0066
Scenario: Creating Group With Long Name Without Description5 ms0066
Scenario: Creating Group With Numbers In Name With Valid Description6 ms0088
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description6 ms0066
Scenario: Creating Group With Permitted Symbols In Name With Valid Description9 ms0066
Scenario: Creating Group With Short Name With Valid Description6 ms0066
Scenario: Creating Group With Short Name Without Description5 ms0066
Scenario: Creating Group With Too Long Name With Valid Description6 ms0077
Scenario: Creating Group With Too Long Name Without Description10 ms0077
Scenario: Creating Group With Too Short Name With Valid Description5 ms0077
Scenario: Creating Group With Too Short Name Without Description4 ms0077
Scenario: Creating Group Without a Name And With Valid Description6 ms0077
Scenario: Creating Group Without a Name And Without Description10 ms0077
Scenario: Creating Groups And Than Setting Group Service So It Does Not Allow Groups6 ms001111
Scenario: Creating Groups And Then Changing InfiniteChildGroups To False And Set MaxNumberChildGroups8 ms001010
Scenario: Creating Groups Under Account That Allows Infinite Child Groups10 ms0099
Scenario: Creating Groups Under Account That Does Not Allow Groups8 ms0099
Scenario: Creating Groups Under Account That Has Limited Child Groups5 ms001212
Scenario: Creating Jobs And Than Setting Job Service So It Does Not Allow Jobs8 ms001212
Scenario: Creating Jobs And Then Changing Job Service Values8 ms001010
Scenario: Creating Jobs Under Account That Allows Infinite Child Devices9 ms001010
Scenario: Creating Jobs Under Account That Does Not Allow Jobs8 ms0099
Scenario: Creating Jobs Under Account That Has Limited Child Jobs10 ms001313
Scenario: Creating Non-Unique Group With Valid Description7 ms0088
Scenario: Creating Non-Unique Tag With Valid Description5 ms0055
Scenario: Creating Non-unique Group Without Description6 ms0088
Scenario: Creating Non-unique Tag Without Description13 ms0044
Scenario: Creating Roles And Than Setting Role Service So It Does Not Allow Roles10 ms001111
Scenario: Creating Roles And Then Changing Role Service Values7 ms001010
Scenario: Creating Roles Under Account That Allows Infinite Child Roles7 ms001010
Scenario: Creating Roles Under Account That Does Not Allow Roles8 ms0099
Scenario: Creating Roles Under Account That Has Limited Child Roles9 ms001212
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To False And maxNumberChildAccounts Is Set7 ms001313
Scenario: Creating Sub-accounts When InfiniteChildAccoounts Is Set To True And maxNumberChildAccounts Is Set11 ms001414
Scenario: Creating Sub-accounts When InfiniteChildAccounts Is Set To False6 ms0099
Scenario: Creating Sub-accounts when InfiniteChildAccounts Is Set To True9 ms001212
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description5 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description5 ms0044
Scenario: Creating Tag With Long Name With Valid Description7 ms0044
Scenario: Creating Tag With Long Name Without Description6 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description5 ms0044
Scenario: Creating Tag With Numbers In Name Without Description9 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description4 ms0044
Scenario: Creating Tag With Permitted Symbols In Name Without Description5 ms0044
Scenario: Creating Tag With Short Name With Valid Description7 ms0044
Scenario: Creating Tag With Short Name Without Description8 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description2 ms0044
Scenario: Creating Tag With Too Long Name Without Description10 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description5 ms0044
Scenario: Creating Tag With Too Short Name Without Description9 ms0044
Scenario: Creating Tag Without a Name And With Valid Description5 ms0044
Scenario: Creating Tag Without a Name And Without Description9 ms0044
Scenario: Creating Tags And Than Setting Tag Service So It Does Not Allow Tags18 ms001111
Scenario: Creating Tags And Then Changing Tag Service Values13 ms001010
Scenario: Creating Tags Under Account That Allows Infinite Child Devices10 ms001010
Scenario: Creating Tags Under Account That Does Not Allow Tags15 ms0099
Scenario: Creating Tags Under Account That Has Limited Child Tags15 ms001212
Scenario: Creating Unique Group With Long Description11 ms0066
Scenario: Creating Unique Group With Non-unique Description9 ms0077
Scenario: Creating Unique Group With Short Description7 ms0066
Scenario: Creating Unique Group With Unique Description5 ms0066
Scenario: Creating Unique Group Without Description6 ms0066
Scenario: Creating Unique Tag With Long Description4 ms0044
Scenario: Creating Unique Tag With Non-unique Description4 ms0055
Scenario: Creating Unique Tag With Short Description5 ms0044
Scenario: Creating Unique Tag With Unique Description6 ms0044
Scenario: Creating Unique Tag Without Description30 ms0044
Scenario: Creating Users And Than Setting User Service So It Does Not Allow Users14 ms001111
Scenario: Creating Users And Then Changing User Service Values9 ms001010
Scenario: Creating Users Under Account That Allows Infinite Child Users13 ms001010
Scenario: Creating Users Under Account That Does Not Allow Users17 ms0099
Scenario: Creating Users Under Account That Has Limited Child Users6 ms001212
Scenario: Creating Valid Endpoint6 ms0066
Scenario: Creating a Access Group with invalid special symbols in name6 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name5 ms0077
Scenario: Creating a Device With Unique Display Name10 ms0088
Scenario: Creating a job with name only15 ms0066
Scenario: Creating a job with null name15 ms0055
Scenario: Creating a job without name with valid description19 ms0055
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement8 ms0044
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement23 ms0033
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement7 ms0055
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement8 ms0044
Scenario: Creating a role name with allowed symbols in its name3 ms0055
Scenario: Creating a role with 255 characters long description2 ms0055
Scenario: Creating a role with a name and description that contain digits only3 ms0055
Scenario: Creating a role with forbidden symbols in its name0 ms0044
Scenario: Creating a role with name only4 ms0055
Scenario: Creating a role with null name4 ms0055
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough4 ms0055
Scenario: Creating a role with special characters in the description4 ms0044
Scenario: Creating a role with the name that contains digits4 ms0055
Scenario: Creating a role with too long name2 ms0055
Scenario: Creating a role with too short name4 ms0055
Scenario: Creating a role with valid name and with too long description5 ms0033
Scenario: Creating a role wtih 255 characters long name3 ms0055
Scenario: Creating a single device with case sensitive clientID4 ms0055
Scenario: Creating a single device with clientID that contains 255 characters6 ms0055
Scenario: Creating a single device with clientID that contains 256 characters5 ms0044
Scenario: Creating a single device with clientID that contains invalid character3 ms0044
Scenario: Creating a single device with clientID that contains invalid characters3 ms0044
Scenario: Creating a single device with spaces in clientID6 ms0055
Scenario: Creating a single device with valid clientID5 ms0055
Scenario: Creating a valid Access Group with numbers in name4 ms0055
Scenario: Creating a valid Access Group with only numbers in name5 ms0055
Scenario: Creating a valid Access Group with unique name6 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name5 ms0055
Scenario: Creating a valid role3 ms0055
Scenario: Creating an Access Group with empty name4 ms0044
Scenario: Creating an Access Group with long name3 ms0055
Scenario: Creating an Access Group with short name5 ms0055
Scenario: Creating an Access Group with too long name4 ms0044
Scenario: Creating an Access Group with too short name6 ms0044
Scenario: Creating an Access Group without name and with description3 ms0044
Scenario: Creating and Deleting Endpoint Two Times10 ms002525
Scenario: Creating index with regular user18 ms002525
Scenario: Creating job with invalid symbols in name without description9 ms0044
Scenario: Creating job with long name and valid description7 ms0066
Scenario: Creating job with long name without description11 ms0066
Scenario: Creating job with numbers in name and valid description16 ms0066
Scenario: Creating job with numbers in name without description6 ms0066
Scenario: Creating job with permitted symbols in name without description13 ms0033
Scenario: Creating job with short name and valid job description10 ms0066
Scenario: Creating job with short name without description13 ms0066
Scenario: Creating job with too long name and valid description5 ms0055
Scenario: Creating job with too long name without description10 ms0055
Scenario: Creating job with too short name and valid description17 ms0055
Scenario: Creating job with too short name without description17 ms0055
Scenario: Creating job without name and without description8 ms0055
Scenario: Creating new device and tagging it with specific Tag13 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag7 ms001616
Scenario: Creating non-unique Access Group7 ms0055
Scenario: Creating non-unique Access Group with unique description3 ms0055
Scenario: Creating non-unique job name with valid job description10 ms0077
Scenario: Creating two device with the same clientID4 ms0055
Scenario: Creating two indexes with daily index18 ms001717
Scenario: Creating two indexes with hourly index15 ms001717
Scenario: Creating two indexes with weekly index15 ms001717
Scenario: Creating two roles with the same description4 ms0066
Scenario: Creating two roles with the same name4 ms0077
Scenario: Creating unique Access Group with long description3 ms0055
Scenario: Creating unique Access Group with non-unique description4 ms0066
Scenario: Creating unique Access Group with numbers in description3 ms0055
Scenario: Creating unique Access Group with only numbers in description6 ms0055
Scenario: Creating unique Access Group with short description10 ms0055
Scenario: Creating unique Access Group with special symbols in description19 ms2114
Scenario: Creating unique Access Group with unique description2 ms0055
Scenario: Creating unique job with long description9 ms0066
Scenario: Creating unique job with non-unique description6 ms001010
Scenario: Creating unique job with short description9 ms0066
Scenario: Creating user17 ms0055
Scenario: Creation of access role with neither acess info and role entities5 ms001212
Scenario: Creation of access role without an acess info entity7 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY16 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI24 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed26 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed26 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY10 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY14 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account10 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC19 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI25 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed12 ms0099
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed19 ms0099
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed7 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed18 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI22 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed26 ms0099
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY24 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY18 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account5 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed21 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed15 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed7 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI15 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC14 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY16 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed12 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed15 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed11 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed22 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed14 ms0099
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed8 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY14 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY14 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed13 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed24 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed9 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI15 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed17 ms0099
Scenario: Decreasing MaxNumberChildAccounts When Sub-accounts Are Already Created10 ms001515
Scenario: Delete Kapua system user8 ms0055
Scenario: Delete a access info entity with permissions and roles9 ms001717
Scenario: Delete a connection from the database7 ms0088
Scenario: Delete a group from the database10 ms001010
Scenario: Delete a group from the database - Unknown group ID6 ms0066
Scenario: Delete a job5 ms001111
Scenario: Delete a job execution item5 ms0088
Scenario: Delete a job execution item twice4 ms0099
Scenario: Delete a job twice9 ms001010
Scenario: Delete a non existent event7 ms0077
Scenario: Delete a non existing connection5 ms0077
Scenario: Delete a non existing permission entity5 ms001616
Scenario: Delete a non existing role entry6 ms001111
Scenario: Delete a non-existing step4 ms001212
Scenario: Delete a nonexistent domain8 ms0055
Scenario: Delete a step definition6 ms0088
Scenario: Delete a step definition twice6 ms0077
Scenario: Delete access role from user15 ms001212
Scenario: Delete an access info entity twice8 ms001111
Scenario: Delete an access info entity using the wrong scope ID5 ms001111
Scenario: Delete an existing access info entity7 ms001212
Scenario: Delete an existing access permission entity10 ms001515
Scenario: Delete an existing access role entry5 ms002222
Scenario: Delete an existing account5 ms0055
Scenario: Delete an existing device from the registry6 ms0044
Scenario: Delete an existing event6 ms0099
Scenario: Delete an existing role7 ms001010
Scenario: Delete an existing role twice4 ms001616
Scenario: Delete an existing step3 ms001111
Scenario: Delete items based on query results42 ms008484
Scenario: Delete items by date ranges1 sec00132132
Scenario: Delete items by the datastore ID44 ms006666
Scenario: Delete middle child expiration6 ms001515
Scenario: Delete nonexisting account4 ms0044
Scenario: Delete nonexisting role permission13 ms001313
Scenario: Delete parent expiration7 ms001414
Scenario: Delete permissions from role30 ms001818
Scenario: Delete role permissions7 ms001010
Scenario: Delete scheduler7 ms0088
Scenario: Delete scheduler which doesn't exist8 ms0055
Scenario: Delete the Kapua system account4 ms0055
Scenario: Delete the last created domain entry8 ms0088
Scenario: Delete user5 ms0066
Scenario: Delete user that doesn't exist4 ms0055
Scenario: Deleting "Cron Schedule" Triggering8 ms001313
Scenario: Deleting "Device Schedule" Triggering7 ms001111
Scenario: Deleting "Interval Schedule" Triggering8 ms001313
Scenario: Deleting Device With Disabled Status12 ms001010
Scenario: Deleting Device With Enabled Status9 ms001010
Scenario: Deleting Endpoint Domain Name And Leaving it Empty4 ms0088
Scenario: Deleting Endpoint Which Does Not Exist6 ms0066
Scenario: Deleting Existing Group5 ms0088
Scenario: Deleting Existing Group And Creating It Again With Same Name6 ms001212
Scenario: Deleting Existing Tag And Creating It Again With Same Name4 ms0077
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description10 ms0088
Scenario: Deleting Non-Existent Tag4 ms0077
Scenario: Deleting Tag From Device4 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description5 ms0055
Scenario: Deleting Unexisitng Group6 ms001111
Scenario: Deleting a Permission10 ms002121
Scenario: Deleting a non-existing Access Group2 ms0066
Scenario: Deleting a role twice3 ms0077
Scenario: Deleting admin role11 ms0077
Scenario: Deleting an existing Access Group4 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name4 ms0077
Scenario: Deleting an existing role2 ms0066
Scenario: Deleting default permissions from admin role11 ms001212
Scenario: Deleting existing tag4 ms0099
Scenario: Deleting role after adding it to user13 ms001414
Scenario: Deleting role after it has been added to user in child account9 ms001616
Scenario: Deleting user in account that is higher in hierarchy20 ms002323
Scenario: Deleting user in account that is lower in hierarchy13 ms002424
Scenario: Device connection update12 ms0077
Scenario: Device factory sanity checks3 ms0022
Scenario: Device queries10 ms001010
Scenario: Device query - find by BIOS version5 ms0077
Scenario: Domain entry query16 ms0055
Scenario: Domain with null actions6 ms0055
Scenario: Domain with null name6 ms0055
Scenario: Domains with duplicate names5 ms0088
Scenario: Duplicate group name in root scope6 ms001010
Scenario: Duplicate role names13 ms0077
Scenario: Editing Access Group description to description with numbers3 ms0055
Scenario: Editing Access Group description to description with only numbers4 ms0055
Scenario: Editing Access Group description to description with special symbols3 ms0044
Scenario: Editing Access Group description to long description5 ms0055
Scenario: Editing Access Group description to non-unique one5 ms0055
Scenario: Editing Access Group description to short description3 ms0055
Scenario: Editing Access Group description to unique one4 ms0077
Scenario: Editing Access Group name to a long one4 ms0077
Scenario: Editing Access Group name to a too long one4 ms0055
Scenario: Editing Access Group name to empty name3 ms0055
Scenario: Editing Access Group name to name that contains numbers6 ms0077
Scenario: Editing Access Group name to name that contains only numbers4 ms0077
Scenario: Editing Access Group name to name with invalid special symbols in name1 ms0055
Scenario: Editing Access Group name to name with valid special symbols4 ms0077
Scenario: Editing Access Group name to non-unique one3 ms0066
Scenario: Editing Access Group name to short one4 ms0077
Scenario: Editing Access Group name to too short one3 ms0055
Scenario: Editing Access Group name to valid one4 ms0077
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols4 ms0088
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers4 ms0088
Scenario: Editing Endpoint Domain Name So It Has Max Value5 ms0077
Scenario: Editing Endpoint Domain Name So It Has Min Value4 ms0077
Scenario: Editing Endpoint Domain Name To Non-unique Value5 ms0099
Scenario: Editing Endpoint Domain Name To Unique Value5 ms0077
Scenario: Editing Endpoint Port To Non-unique Value3 ms0099
Scenario: Editing Endpoint Port To Unique Value5 ms0077
Scenario: Editing Endpoint Schema And Leaving It Empty5 ms0088
Scenario: Editing Endpoint Schema So It Contains "http://"9 ms0088
Scenario: Editing Endpoint Schema So It Contains "https://"5 ms0088
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols6 ms0088
Scenario: Editing Endpoint Schema So It Contains Only Numbers5 ms0088
Scenario: Editing Endpoint Schema So It Has Max Length4 ms0077
Scenario: Editing Endpoint Schema So It Has Min Length5 ms0077
Scenario: Editing Endpoint Schema To Non-unique Value5 ms0088
Scenario: Editing Endpoint Schema To Unique Value23 ms0077
Scenario: Editing Endpoint Secure Field To Non-unique Value5 ms0099
Scenario: Editing Endpoint Secure Field To Unique Value5 ms0077
Scenario: Editing Endpoint To NULL Values6 ms001414
Scenario: Editing Endpoint To Non-unique Endpoint8 ms001010
Scenario: Editing Group's Name To Contain Numbers Without Changing Description7 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description4 ms0077
Scenario: Empty query results are supported7 ms0088
Scenario: Event factory sanity checks5 ms0022
Scenario: Event service domain check8 ms0022
Scenario: Every account must have the default configuration items5 ms0033
Scenario: Execute possible docker steps to show its usage5 ms231033
Scenario: Executing Job And Then Restarting Device14 ms2+216+1627-1845
Scenario: Executing Job When Device Connected After End Date And Time50 ms003838
Scenario: Executing Job When Device Connected After The Specified Start Date And Time7 ms2+24+432-638
Scenario: Executing Job When Device Connected Before End Date And Time17 ms2+24+433-639
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time26 ms003737
Scenario: Executing Job Without Steps55 ms004040
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode26 ms00419419
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode47 ms00397397
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices31 ms00305305
Scenario: Find a connection by its IDs5 ms0066
Scenario: Find a connection by its client ID7 ms0066
Scenario: Find a group entry in the database7 ms0099
Scenario: Find a non existing event5 ms0066
Scenario: Find account by Id6 ms0044
Scenario: Find account by Ids6 ms0044
Scenario: Find account by name7 ms0044
Scenario: Find account by random Id6 ms0033
Scenario: Find all child accounts8 ms0033
Scenario: Find an access info entity6 ms001111
Scenario: Find an access info entity by user ID5 ms001010
Scenario: Find an event by its ID8 ms0066
Scenario: Find an existing access role entity7 ms001313
Scenario: Find by name nonexisting account5 ms0033
Scenario: Find correct number of messages by corresponding metric0.5 sec005858
Scenario: Find device by client ID6 ms0033
Scenario: Find device by registry ID5 ms0044
Scenario: Find last created permission17 ms001212
Scenario: Find multiple users6 ms0055
Scenario: Find role by ID6 ms0077
Scenario: Find self account by id14 ms001111
Scenario: Find self account by id and scope id8 ms001111
Scenario: Find self account by name8 ms001111
Scenario: Find the last created domain entry10 ms0055
Scenario: Find user by id6 ms0055
Scenario: Find user by its email3 ms0066
Scenario: Find user by its phone number4 ms0066
Scenario: Find user by name40 ms0055
Scenario: Find user by name that doesn't exist4 ms0033
Scenario: Find user with id and scope id that doesn't exist4 ms0033
Scenario: Finding all messages by selecting all metrics0.43 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.47 sec005252
Scenario: Finding messages with incorrect metric parameters0.64 sec007272
Scenario: Finding user by expiration date in the future4 ms0055
Scenario: Finding user by expiration date in the past4 ms0066
Scenario: Finding user by expiration date in the present4 ms0066
Scenario: Generic connection query5 ms0088
Scenario: Get metadata4 ms0033
Scenario: Group with a null name6 ms0077
Scenario: Handle account creation20 ms0033
Scenario: Handle duplicate account names7 ms0055
Scenario: Handle null account name9 ms0044
Scenario: Handling of 2 birth messages7 ms001212
Scenario: Handling of a disconnect message from a non existing device6 ms001010
Scenario: Have Two Devices in The Same Group Without Description7 ms001313
Scenario: I try to find a non-existing connection5 ms0066
Scenario: If user credential expiration date is before today, user can not login7 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive7 ms001414
Scenario: If user credential expiration date is tomorrow, user can login3 ms001313
Scenario: If user credential is in state disabled, user can not login10 ms001414
Scenario: If user credential is in state enabled, user can login5 ms001313
Scenario: If user expiration date is before today, user can not login8 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached8 ms001313
Scenario: If user expiration date is tomorrow, user can login2 ms001212
Scenario: Init Security Context for all scenarios0.21 sec004848
Scenario: Installing a package10 ms2+26+65-813
Scenario: Interval Job" Schedule With Too Long Name6 ms001111
Scenario: It must be possible to query for specific entries in the role database10 ms0088
Scenario: It should not be possible to change the configuration items4 ms0055
Scenario: Job execution factory sanity checks1 ms0022
Scenario: Job factory sanity checks17 ms0033
Scenario: Job with a duplicate name3 ms0099
Scenario: Job with a null name4 ms0088
Scenario: Job with a null scope ID4 ms0099
Scenario: Job with an empty name4 ms0088
Scenario: List Endpoints Created From Sub-Account6 ms002626
Scenario: List Endpoints From "kapua-sys" Account6 ms001111
Scenario: List Endpoints From Sub-Account Of Another Sub-Account6 ms002626
Scenario: List Endpoints From Sub-account5 ms001515
Scenario: MetricsInfo client ID and topic data based on the client id29 ms003434
Scenario: MetricsInfo last published date30 ms004848
Scenario: Modify a role that was deleted9 ms0099
Scenario: Modify an existing account6 ms0044
Scenario: Modify last child expiration so that it still expires before parent9 ms001414
Scenario: Modify middle child expiration so that it still expires before parent9 ms001414
Scenario: Modify middle child expiration to outlive parent8 ms001515
Scenario: Modify nonexisting account5 ms0066
Scenario: Modify parent expiration so that it still expires after child6 ms001414
Scenario: Modify parent expiration to before child expiration7 ms001515
Scenario: Modifying Sub-account of a different parent account13 ms002525
Scenario: Moving Device From One Group With Description to Another7 ms001414
Scenario: Nameless role entry4 ms0077
Scenario: Negative scenario when client connects twice with same client id42 ms001111
Scenario: New connection with reserved ID15 ms003434
Scenario: Permission factory sanity checks5 ms0033
Scenario: Positive scenario without stealing link36 ms001212
Scenario: Query based on message ordering47 ms002020
Scenario: Query based on metrics ordering30 ms002020
Scenario: Query before schema search22 ms008282
Scenario: Query for a specific group by name6 ms001616
Scenario: Query for all the access info entities of a specific user4 ms001818
Scenario: Query for all the access info entities of an invalid user8 ms001010
Scenario: Query for executions of a specific job4 ms001818
Scenario: Query for jobs with specified name4 ms0099
Scenario: Query for step definitions5 ms0077
Scenario: Query user4 ms0066
Scenario: Querying Other Items With All Account Permissions11 ms003939
Scenario: Regular connection7 ms0077
Scenario: Regular creation of Access Role entity5 ms001414
Scenario: Regular domain6 ms0055
Scenario: Regular group in random scope6 ms0077
Scenario: Regular group in root scope6 ms0077
Scenario: Regular job creation5 ms001010
Scenario: Regular job execution creation9 ms0077
Scenario: Regular role creation12 ms0099
Scenario: Regular step creation4 ms001111
Scenario: Regular step definition creation16 ms0077
Scenario: Regular step definition with a property list13 ms0044
Scenario: Reset Security Context for all scenarios0.14 sec004848
Scenario: Restarting a job with Asset Write and Bundle Start steps25 ms002828
Scenario: Restarting a job with Command Execution and Bundle Start steps24 ms002828
Scenario: Restarting a job with Configuration Put and Bundle Start steps25 ms002828
Scenario: Restarting a job with Package Uninstall and Bundle Start steps31 ms002828
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times7 ms2+224+247-2633
Scenario: Restarting a job with invalid Configuration Put step two times3 ms2+227+277-2936
Scenario: Restarting a job with invalid Package Install step and multiple devices two times10 ms2+222+227-2431
Scenario: Restarting a job with invalid Package Install step two times12 ms2+225+257-2734
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times15 ms2+223+237-2532
Scenario: Restarting a job with invalid Package Uninstall step two times13 ms2+225+257-2734
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times12 ms2+224+247-2633
Scenario: Restarting a job with valid Configuration Put step two times13 ms2+227+277-2936
Scenario: Restarting a job with valid Package Install step and multiple devices two times10 ms2+220+207-2229
Scenario: Restarting a job with valid Package Install step two times10 ms2+225+257-2734
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times17 ms2+221+217-2330
Scenario: Restarting a job with valid Package Uninstall step two times9 ms2+223+237-2532
Scenario: Restarting job With invalid Asset Write and multiple two times9 ms2+225+257-2734
Scenario: Restarting job With valid Asset Write step two times2 ms2+227+277-2936
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices22 ms003131
Scenario: Restarting job with Asset Write step25 ms002525
Scenario: Restarting job with Asset Write step and multiple devices31 ms002828
Scenario: Restarting job with Bundle Start step20 ms002525
Scenario: Restarting job with Bundle Start step and multiple devices25 ms002727
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices21 ms003131
Scenario: Restarting job with Bundle Stop and Bundle Start steps23 ms002929
Scenario: Restarting job with Bundle Stop step26 ms002525
Scenario: Restarting job with Bundle Stop step and multiple devices24 ms002727
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices27 ms003131
Scenario: Restarting job with Command Execution step24 ms002525
Scenario: Restarting job with Command Execution step and multiple devices20 ms002727
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices44 ms003131
Scenario: Restarting job with Configuration Put step19 ms002525
Scenario: Restarting job with Configuration Put step and multiple devices23 ms002727
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices57 ms005959
Scenario: Restarting job with Package Download/Install step and multiple devices23 ms002727
Scenario: Restarting job with Package Install step23 ms002525
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device27 ms003131
Scenario: Restarting job with Package Uninstall step24 ms002525
Scenario: Restarting job with Package Uninstall step and multiple device20 ms002727
Scenario: Restarting job with invalid Asset Write step two times10 ms2+227+277-2936
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times12 ms2+232+327-3441
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times0 ms2+234+347-3643
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times7 ms2+226+267-2835
Scenario: Restarting job with invalid Bundle Start step two times10 ms2+228+287-3037
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times12 ms2+226+267-2835
Scenario: Restarting job with invalid Bundle Stop step two times9 ms2+228+287-3037