Test Result : (root)

8 failures (-14) , 29 skipped (-156)
7,240 tests (-9262)
Took 9.9 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description11 ms6
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"11 ms6
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device6 ms6
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events5 ms6
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.And I confirm the executed job is finished27 ms6
 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 Time31 ms6
 Scenario: Executing Job When Device Connected Before End Date And Time.And I confirm the executed job is finished5 ms6
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time7 ms6

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A newly created account must have some metadata3 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic10 ms0088
Scenario: Account based ClientInfo data check30 ms002424
Scenario: Account name must not be mutable3 ms0066
Scenario: Account wide metrics check38 ms002828
Scenario: Add Access Info domain permissions to new user11 ms002626
Scenario: Add Account permissions to the role in child account11 ms002828
Scenario: Add Credential domain permissions to new user17 ms001818
Scenario: Add Datastore domain permissions to new user0.21 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user12 ms001111
Scenario: Add Device Connection domain permissions to new user12 ms002323
Scenario: Add Device Event domain permissions to new user14 ms001616
Scenario: Add Device domain permissions to new user13 ms001717
Scenario: Add Domain domain permissions to kapua-sys user15 ms001717
Scenario: Add Domain domain permissions to new user12 ms003232
Scenario: Add Endpoint Permission To The User11 ms003030
Scenario: Add Endpoint_info permissions to the role in child account11 ms003030
Scenario: Add Group domain permissions to new user16 ms001717
Scenario: Add Group permissions to the role in child account15 ms002626
Scenario: Add Job domain permissions to new user8 ms001919
Scenario: Add Role domain permissions to new user11 ms001717
Scenario: Add Role permissions to the role in child account17 ms002626
Scenario: Add Scheduler Permissions With Job Permissions16 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions15 ms002121
Scenario: Add Scheduler permissions to the role in child account13 ms003636
Scenario: Add Tag domain permissions to new user21 ms001515
Scenario: Add Tag permissions to the role in child account14 ms002626
Scenario: Add User domain permissions to new user14 ms002020
Scenario: Add account permissions to the role11 ms001919
Scenario: Add admin role to the user17 ms004444
Scenario: Add and delete Account permissions from the "admin" role12 ms001414
Scenario: Add and delete Device permissions from the "admin" role40 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role10 ms001414
Scenario: Add and delete Group permissions from the "admin" role14 ms001414
Scenario: Add and delete Job permissions from the "admin" role16 ms001414
Scenario: Add and delete Role permissions from the "admin" role11 ms001414
Scenario: Add and delete User permissions from the "admin" role12 ms001515
Scenario: Add datastore permissions to the role36 ms002727
Scenario: Add deleted role again11 ms001010
Scenario: Add device event permissions to the role15 ms003232
Scenario: Add device permissions to the role20 ms001919
Scenario: Add device permissions to the role in child account10 ms002626
Scenario: Add domain, user and access_info permissions to the role12 ms002323
Scenario: Add endpoint_info permissions to the role12 ms003131
Scenario: Add group permissions to the role23 ms001818
Scenario: Add job permissions to the role20 ms001919
Scenario: Add job permissions to the role in child account10 ms002626
Scenario: Add role permissions to the role18 ms001919
Scenario: Add same permission twice to the same role18 ms001414
Scenario: Add same role to user twice10 ms001313
Scenario: Add scheduler permissions to the role23 ms003131
Scenario: Add tag permissions to the role13 ms001818
Scenario: Add user permissions to the role15 ms001919
Scenario: Add user permissions to the role in child account38 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters10 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value7 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format5 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only7 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time6 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter10 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter8 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only7 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time8 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter6 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters11 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only6 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 Name7 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only7 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter11 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name9 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter10 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only8 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time6 ms001111
Scenario: Adding "Device Connect" Schedule Without Name7 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter8 ms0099
Scenario: Adding "Empty" Tag To Device3 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters9 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only9 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time5 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name9 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name10 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only6 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter9 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name7 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter8 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number9 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only11 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time5 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number4 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter6 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name7 ms001111
Scenario: Adding "admin" role to a user in a child account15 ms001414
Scenario: Adding "admin" role to multiple users12 ms001818
Scenario: Adding "admin" role twice9 ms001313
Scenario: Adding Account:Delete permission to user in same scope10 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope10 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope13 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope10 ms001919
Scenario: Adding Account:Read permission to user in same scope11 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 scope9 ms002323
Scenario: Adding Account:Write permission to user in same scope10 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope10 ms003131
Scenario: Adding Multiple Permissions To User10 ms002020
Scenario: Adding One Permission To User13 ms001111
Scenario: Adding Permissions To Child User17 ms001818
Scenario: Adding Permissions To Parallel User10 ms001818
Scenario: Adding Previously Deleted Permission12 ms002828
Scenario: Adding Previously Deleted Tag From Device Again6 ms001111
Scenario: Adding Regular Tag Without Description To Device7 ms0066
Scenario: Adding Tag With Long Name Without Description To Device3 ms0066
Scenario: Adding Tag With Numbers Without Description To Device4 ms0066
Scenario: Adding Tag With Short Name Without Description To Device7 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device5 ms0066
Scenario: Adding all Account permissions to user in same scope8 ms001717
Scenario: Adding all Account permissions to user in sub-account scope15 ms002424
Scenario: Adding existing roles to user12 ms001515
Scenario: Adding role from child account to user in new child account9 ms001515
Scenario: Adding role to multiple users in child account15 ms001818
Scenario: Adding same role twice to user in child account12 ms001515
Scenario: Adding the same role to user twice in child account53 ms001313
Scenario: All device parameters must match the device creator4 ms0033
Scenario: B1 Broker publish to CTRL_ACC_REPLY16 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed16 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed6 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI23 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed12 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY24 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY25 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account12 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed13 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed10 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed7 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI12 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed18 ms0099
Scenario: Basic Device Event queries5 ms001010
Scenario: Birth and applications event handling8 ms001212
Scenario: Birth and death message handling7 ms001212
Scenario: Birth and missing event handling7 ms001212
Scenario: Birth message handling from a new device4 ms001313
Scenario: Birth message handling from an existing device7 ms001212
Scenario: Captured date based ClientInfo data check28 ms003030
Scenario: Case sensitiveness of named device searches3 ms0044
Scenario: Change role name so it is too short3 ms0066
Scenario: Change the account parent path3 ms0055
Scenario: Changing Client ID6 ms0099
Scenario: Changing Description On Tag With Long Description5 ms0044
Scenario: Changing Description On Tag With Long Name3 ms0055
Scenario: Changing Description On Tag With Numbers In Name4 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name4 ms0044
Scenario: Changing Description On Tag With Short Description4 ms0044
Scenario: Changing Description On Tag With Short Name3 ms0044
Scenario: Changing Device Status To Disabled6 ms0099
Scenario: Changing Device Status To Enabled7 ms0099
Scenario: Changing Tag's Description To Non-Unique One5 ms0055
Scenario: Changing Tag's Description To Unique One3 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 Description7 ms0055
Scenario: Changing Tag's Name To Non-Unique One9 ms0066
Scenario: Changing Tag's Name To Short One Without Description4 ms0077
Scenario: Changing Tag's Name To Unique One5 ms0077
Scenario: Changing Tag's Name To a Long One Without Description5 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description4 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description5 ms0055
Scenario: Changing description of a nonexisting role2 ms0077
Scenario: Changing job description to non-unique one7 ms0077
Scenario: Changing job description to the long one6 ms0066
Scenario: Changing job description to unique one5 ms0066
Scenario: Changing job description to very short one13 ms0077
Scenario: Changing job name to a long one without description9 ms0077
Scenario: Changing job name to a too long one without description7 ms0055
Scenario: Changing job name to a too short one without description8 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 description5 ms0055
Scenario: Changing job name to non-unique one7 ms0088
Scenario: Changing job name to short one without description9 ms0077
Scenario: Changing job name to unique one9 ms0099
Scenario: Changing name of a nonexisting role4 ms0077
Scenario: Changing role description to a valid one3 ms0066
Scenario: Changing role name so it is too long3 ms0066
Scenario: Changing role name to contain special character3 ms0044
Scenario: Changing role name to null4 ms0066
Scenario: Changing role's name to a valid one3 ms0066
Scenario: Channel info queries based on datastore channel filters23 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id38 ms002828
Scenario: ChannelInfo client ID based on the account id28 ms002626
Scenario: ChannelInfo last published date29 ms003030
Scenario: ChannelInfo topic data based on the account id35 ms002626
Scenario: Check account properties5 ms0044
Scenario: Check the Device Connection Domain data seetting4 ms0022
Scenario: Check the database cache coherency32 ms003030
Scenario: Check the mapping for message semantic topics31 ms003030
Scenario: Check the message store29 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization4 ms0022
Scenario: Client Id based ClientInfo data check29 ms002828
Scenario: Connect to the system and publish some data94 ms002222
Scenario: Connection Service factory sanity checks3 ms0022
Scenario: Count connections in empty scope2 ms0044
Scenario: Count connections in scope4 ms0055
Scenario: Count devices with a specific BIOS version3 ms0066
Scenario: Count events in empty scope6 ms0066
Scenario: Count step definition items10 ms0044
Scenario: Count step definitions in wrong (empty) scope9 ms0011
Scenario: Count user5 ms0066
Scenario: Counting created roles items in the DB2 ms0055
Scenario: Create a regular event23 ms0088
Scenario: Create a single device with an empty string for clientID3 ms0044
Scenario: Create a single device with null clientID value3 ms0044
Scenario: Create a valid job entry33 ms0066
Scenario: Create an event with a null scope ID8 ms0077
Scenario: Create index with specific prefix14 ms001212
Scenario: Create multiple users3 ms0055
Scenario: Create same user in different accounts19 ms001515
Scenario: Create scheduler with correct end date6 ms0088
Scenario: Create scheduler with empty schedule name11 ms0088
Scenario: Create scheduler with end date before start date8 ms0099
Scenario: Create scheduler with invalid Retry Interval property5 ms0099
Scenario: Create scheduler with invalid cron job trigger property10 ms0099
Scenario: Create scheduler with invalid schedule name48 ms0088
Scenario: Create scheduler with short schedule name8 ms0088
Scenario: Create scheduler with too long schedule name11 ms0088
Scenario: Create scheduler with valid Retry Interval property7 ms0077
Scenario: Create scheduler with valid cron job trigger property7 ms0077
Scenario: Create scheduler with valid schedule name27 ms0066
Scenario: Create scheduler without Cron Job Trigger property9 ms0099
Scenario: Create scheduler without Retry Interval property6 ms0099
Scenario: Create scheduler without start date20 ms0077
Scenario: Create user that already exist3 ms0077
Scenario: Create user that has more than DB allowed length8 ms0055
Scenario: Create user with short name10 ms0055
Scenario: Create user with special characters in his name5 ms0055
Scenario: Creating A Device With Disabled Status6 ms0077
Scenario: Creating A Device With Enabled Status5 ms0077
Scenario: Creating A Device With Long Display Name5 ms0077
Scenario: Creating A Device With Long Name9 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols8 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 Name9 ms0077
Scenario: Creating A Device With Non-unique Name5 ms001010
Scenario: Creating A Device With Short Display Name11 ms0077
Scenario: Creating A Device With Short Name9 ms0077
Scenario: Creating A Device With Too Long Display Name4 ms0088
Scenario: Creating A Device With Too Long Name10 ms0088
Scenario: Creating A Device With Unique Name7 ms0099
Scenario: Creating Non-Unique Tag With Valid Description5 ms0055
Scenario: Creating Non-unique Tag Without Description8 ms0044
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description4 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description5 ms0044
Scenario: Creating Tag With Long Name With Valid Description5 ms0044
Scenario: Creating Tag With Long Name Without Description7 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description3 ms0044
Scenario: Creating Tag With Numbers In Name Without Description4 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description6 ms0044
Scenario: Creating Tag With Permitted Symbols In Name Without Description5 ms0044
Scenario: Creating Tag With Short Name With Valid Description4 ms0044
Scenario: Creating Tag With Short Name Without Description0.17 sec0044
Scenario: Creating Tag With Too Long Name With Valid Description1 ms0044
Scenario: Creating Tag With Too Long Name Without Description6 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description8 ms0044
Scenario: Creating Tag With Too Short Name Without Description7 ms0044
Scenario: Creating Tag Without a Name And With Valid Description5 ms0044
Scenario: Creating Tag Without a Name And Without Description7 ms0044
Scenario: Creating Unique Tag With Long Description4 ms0044
Scenario: Creating Unique Tag With Non-unique Description4 ms0055
Scenario: Creating Unique Tag With Short Description94 ms0044
Scenario: Creating Unique Tag With Unique Description4 ms0044
Scenario: Creating Unique Tag Without Description27 ms0044
Scenario: Creating a Access Group with invalid special symbols in name0 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name8 ms0077
Scenario: Creating a Device With Unique Display Name5 ms0088
Scenario: Creating a job with name only19 ms0066
Scenario: Creating a job with null name19 ms0055
Scenario: Creating a job without name with valid description6 ms0055
Scenario: Creating a role name with allowed symbols in its name2 ms0055
Scenario: Creating a role with 255 characters long description2 ms0055
Scenario: Creating a role with a name and description that contain digits only2 ms0055
Scenario: Creating a role with forbidden symbols in its name0 ms0044
Scenario: Creating a role with name only3 ms0055
Scenario: Creating a role with null name3 ms0055
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough5 ms0055
Scenario: Creating a role with special characters in the description2 ms0044
Scenario: Creating a role with the name that contains digits4 ms0055
Scenario: Creating a role with too long name1 ms0055
Scenario: Creating a role with too short name2 ms0055
Scenario: Creating a role with valid name and with too long description4 ms0033
Scenario: Creating a role wtih 255 characters long name3 ms0055
Scenario: Creating a single device with case sensitive clientID3 ms0055
Scenario: Creating a single device with clientID that contains 255 characters6 ms0055
Scenario: Creating a single device with clientID that contains 256 characters3 ms0044
Scenario: Creating a single device with clientID that contains invalid character3 ms0044
Scenario: Creating a single device with clientID that contains invalid characters0 ms0044
Scenario: Creating a single device with spaces in clientID7 ms0055
Scenario: Creating a single device with valid clientID3 ms0055
Scenario: Creating a valid Access Group with numbers in name3 ms0055
Scenario: Creating a valid Access Group with only numbers in name5 ms0055
Scenario: Creating a valid Access Group with unique name25 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 name9 ms0044
Scenario: Creating an Access Group with long name6 ms0055
Scenario: Creating an Access Group with short name8 ms0055
Scenario: Creating an Access Group with too long name2 ms0044
Scenario: Creating an Access Group with too short name5 ms0044
Scenario: Creating an Access Group without name and with description1 ms0044
Scenario: Creating index with regular user14 ms002525
Scenario: Creating job with invalid symbols in name without description0 ms0044
Scenario: Creating job with long name and valid description6 ms0066
Scenario: Creating job with long name without description9 ms0066
Scenario: Creating job with numbers in name and valid description5 ms0066
Scenario: Creating job with numbers in name without description6 ms0066
Scenario: Creating job with permitted symbols in name without description6 ms0033
Scenario: Creating job with short name and valid job description7 ms0066
Scenario: Creating job with short name without description7 ms0066
Scenario: Creating job with too long name and valid description4 ms0055
Scenario: Creating job with too long name without description5 ms0055
Scenario: Creating job with too short name and valid description6 ms0055
Scenario: Creating job with too short name without description9 ms0055
Scenario: Creating job without name and without description6 ms0055
Scenario: Creating new device and tagging it with specific Tag7 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag6 ms001616
Scenario: Creating non-unique Access Group5 ms0055
Scenario: Creating non-unique Access Group with unique description4 ms0055
Scenario: Creating non-unique job name with valid job description5 ms0077
Scenario: Creating two device with the same clientID3 ms0055
Scenario: Creating two indexes with daily index9 ms001717
Scenario: Creating two indexes with hourly index11 ms001717
Scenario: Creating two indexes with weekly index12 ms001717
Scenario: Creating two roles with the same description2 ms0066
Scenario: Creating two roles with the same name2 ms0077
Scenario: Creating unique Access Group with long description5 ms0055
Scenario: Creating unique Access Group with non-unique description7 ms0066
Scenario: Creating unique Access Group with numbers in description3 ms0055
Scenario: Creating unique Access Group with only numbers in description4 ms0055
Scenario: Creating unique Access Group with short description3 ms0055
Scenario: Creating unique Access Group with special symbols in description22 ms2114
Scenario: Creating unique Access Group with unique description3 ms0055
Scenario: Creating unique job with long description6 ms0066
Scenario: Creating unique job with non-unique description8 ms001010
Scenario: Creating unique job with short description6 ms0066
Scenario: Creating user18 ms0055
Scenario: D1 Device publish to CTRL_ACC_REPLY14 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI14 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed10 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed14 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY15 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY15 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account9 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC18 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI21 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed11 ms0099
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed12 ms0099
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed7 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed22 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI8 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed14 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_REPLY14 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY28 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account8 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed17 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed21 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed7 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI13 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC14 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY11 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed20 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed9 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed16 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed13 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed21 ms0099
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed11 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY15 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY19 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account12 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed18 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed17 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed11 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI4 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed15 ms0099
Scenario: Delete Kapua system user5 ms0055
Scenario: Delete a connection from the database3 ms0088
Scenario: Delete a non existent event5 ms0077
Scenario: Delete a non existing connection4 ms0077
Scenario: Delete a step definition10 ms0088
Scenario: Delete a step definition twice5 ms0077
Scenario: Delete access role from user20 ms001212
Scenario: Delete an existing account4 ms0055
Scenario: Delete an existing device from the registry3 ms0044
Scenario: Delete an existing event4 ms0099
Scenario: Delete items based on query results40 ms008484
Scenario: Delete items by date ranges0.33 sec0-20-37132+39132
Scenario: Delete items by the datastore ID47 ms0-20-2666+2866
Scenario: Delete nonexisting account3 ms0044
Scenario: Delete permissions from role14 ms001818
Scenario: Delete scheduler10 ms0088
Scenario: Delete scheduler which doesn't exist6 ms0055
Scenario: Delete the Kapua system account3 ms0055
Scenario: Delete user5 ms0066
Scenario: Delete user that doesn't exist4 ms0055
Scenario: Deleting "Cron Schedule" Triggering8 ms001313
Scenario: Deleting "Device Schedule" Triggering9 ms001111
Scenario: Deleting "Interval Schedule" Triggering6 ms001313
Scenario: Deleting Device With Disabled Status5 ms001010
Scenario: Deleting Device With Enabled Status8 ms001010
Scenario: Deleting Existing Tag And Creating It Again With Same Name4 ms0077
Scenario: Deleting Non-Existent Tag3 ms0077
Scenario: Deleting Tag From Device4 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description3 ms0055
Scenario: Deleting a Permission11 ms002121
Scenario: Deleting a non-existing Access Group3 ms0066
Scenario: Deleting a role twice2 ms0077
Scenario: Deleting admin role10 ms0077
Scenario: Deleting an existing Access Group2 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name3 ms0077
Scenario: Deleting an existing role2 ms0066
Scenario: Deleting default permissions from admin role9 ms001212
Scenario: Deleting existing tag5 ms0099
Scenario: Deleting role after adding it to user12 ms001414
Scenario: Deleting role after it has been added to user in child account13 ms001616
Scenario: Deleting user in account that is higher in hierarchy20 ms002323
Scenario: Deleting user in account that is lower in hierarchy10 ms002424
Scenario: Device connection update3 ms0077
Scenario: Device factory sanity checks5 ms0022
Scenario: Device queries4 ms001010
Scenario: Device query - find by BIOS version4 ms0077
Scenario: Editing Access Group description to description with numbers2 ms0055
Scenario: Editing Access Group description to description with only numbers7 ms0055
Scenario: Editing Access Group description to description with special symbols3 ms0044
Scenario: Editing Access Group description to long description3 ms0055
Scenario: Editing Access Group description to non-unique one2 ms0055
Scenario: Editing Access Group description to short description3 ms0055
Scenario: Editing Access Group description to unique one3 ms0077
Scenario: Editing Access Group name to a long one3 ms0077
Scenario: Editing Access Group name to a too long one2 ms0055
Scenario: Editing Access Group name to empty name3 ms0055
Scenario: Editing Access Group name to name that contains numbers4 ms0077
Scenario: Editing Access Group name to name that contains only numbers3 ms0077
Scenario: Editing Access Group name to name with invalid special symbols in name0 ms0055
Scenario: Editing Access Group name to name with valid special symbols3 ms0077
Scenario: Editing Access Group name to non-unique one3 ms0066
Scenario: Editing Access Group name to short one3 ms0077
Scenario: Editing Access Group name to too short one5 ms0055
Scenario: Editing Access Group name to valid one2 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description4 ms0077
Scenario: Event factory sanity checks5 ms0022
Scenario: Event service domain check4 ms0022
Scenario: Every account must have the default configuration items5 ms0033
Scenario: Executing Job And Then Restarting Device12 ms2162745
Scenario: Executing Job When Device Connected After End Date And Time24 ms003838
Scenario: Executing Job When Device Connected After The Specified Start Date And Time59 ms263038
Scenario: Executing Job When Device Connected Before End Date And Time15 ms263139
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time42 ms003737
Scenario: Executing Job Without Steps27 ms004040
Scenario: Find a connection by its IDs2 ms0066
Scenario: Find a connection by its client ID3 ms0066
Scenario: Find a non existing event5 ms0066
Scenario: Find account by Id4 ms0044
Scenario: Find account by Ids6 ms0044
Scenario: Find account by name3 ms0044
Scenario: Find account by random Id6 ms0033
Scenario: Find all child accounts8 ms0033
Scenario: Find an event by its ID7 ms0066
Scenario: Find by name nonexisting account4 ms0033
Scenario: Find correct number of messages by corresponding metric0.2 sec005858
Scenario: Find device by client ID4 ms0033
Scenario: Find device by registry ID3 ms0044
Scenario: Find multiple users3 ms0055
Scenario: Find user by id4 ms0055
Scenario: Find user by its email3 ms0066
Scenario: Find user by its phone number10 ms0066
Scenario: Find user by name3 ms0055
Scenario: Find user by name that doesn't exist3 ms0033
Scenario: Find user with id and scope id that doesn't exist3 ms0033
Scenario: Finding all messages by selecting all metrics0.24 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.16 sec005252
Scenario: Finding messages with incorrect metric parameters0.18 sec007272
Scenario: Finding user by expiration date in the future5 ms0055
Scenario: Finding user by expiration date in the past3 ms0066
Scenario: Finding user by expiration date in the present3 ms0066
Scenario: Generic connection query3 ms0088
Scenario: Get metadata3 ms0033
Scenario: Handle account creation26 ms0033
Scenario: Handle duplicate account names8 ms0055
Scenario: Handle null account name8 ms0044
Scenario: Handling of 2 birth messages6 ms001212
Scenario: Handling of a disconnect message from a non existing device15 ms001010
Scenario: I try to find a non-existing connection3 ms0066
Scenario: If user credential expiration date is before today, user can not login6 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive8 ms001414
Scenario: If user credential expiration date is tomorrow, user can login4 ms001313
Scenario: If user credential is in state disabled, user can not login7 ms001414
Scenario: If user credential is in state enabled, user can login4 ms001313
Scenario: If user expiration date is before today, user can not login9 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 login3 ms001212
Scenario: Init Security Context for all scenarios76 ms0012-3612-36
Scenario: Installing a package15 ms001313
Scenario: Interval Job" Schedule With Too Long Name7 ms001111
Scenario: It should not be possible to change the configuration items3 ms0055
Scenario: MetricsInfo client ID and topic data based on the client id34 ms003434
Scenario: MetricsInfo last published date36 ms004848
Scenario: Modify an existing account4 ms0044
Scenario: Modify nonexisting account4 ms0066
Scenario: Modifying Sub-account of a different parent account10 ms002525
Scenario: Negative scenario when client connects twice with same client id31 ms001111
Scenario: Positive scenario without stealing link45 ms001212
Scenario: Query based on message ordering22 ms002020
Scenario: Query based on metrics ordering24 ms002020
Scenario: Query before schema search31 ms008282
Scenario: Query for step definitions5 ms0077
Scenario: Query user7 ms0066
Scenario: Querying Other Items With All Account Permissions14 ms003939
Scenario: Regular connection3 ms0077
Scenario: Regular step definition creation6 ms0077
Scenario: Regular step definition with a property list6 ms0044
Scenario: Reset Security Context for all scenarios55 ms0012-3612-36
Scenario: Search By Client ID And Get Multiple Matches24 ms003737
Scenario: Search By Client ID And Get No Matches6 ms001010
Scenario: Search By Client ID And Get One Match9 ms0088
Scenario: Search By Client ID and Display Name5 ms001212
Scenario: Search By Client ID and Serial Number7 ms001212
Scenario: Search By Client ID and Status6 ms001212
Scenario: Search By Client ID, Display Name and Serial Number6 ms001212
Scenario: Search By Client ID, Display Name and Status5 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status7 ms001212
Scenario: Search By Device Status And Get No Matches8 ms0088
Scenario: Search By Device's Display Name And Get One Match7 ms0088
Scenario: Search By Display Name and Serial Number9 ms001212
Scenario: Search By Display Name and Status11 ms001212
Scenario: Search By Full Client ID And Get One Match6 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches8 ms0088
Scenario: Search By One Letter Of Display Name6 ms0088
Scenario: Search By One Letter Of Serial Number6 ms001212
Scenario: Search By Serial Number And Get Multiple Matches9 ms001414
Scenario: Search By Serial Number And Get No Matches6 ms001010
Scenario: Search By Serial Number And Get One Match6 ms001111
Scenario: Search By Serial Number and Status10 ms001212
Scenario: Search By Serial Number, Display Name and Status8 ms001212
Scenario: Search By Specific Serial Number9 ms001010
Scenario: Search By Status And Get Multiple Matches4 ms001010
Scenario: Search by Device Status And Get One Match6 ms001010
Scenario: Search for a non existent client ID4 ms0066
Scenario: Send BIRTH message and then DC message27 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set39 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System42 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file62 ms0088
Scenario: Set environment variables0.1 sec0043-1843-18
Scenario: Setting configuration without mandatory items must raise an error3 ms0055
Scenario: Simple positive scenario for creating daily index13 ms001414
Scenario: Simple positive scenario for creating default - weekly index14 ms001212
Scenario: Simple positive scenario for creating hourly index16 ms001414
Scenario: Start broker for all scenarios0.31 sec0030-1430-14
Scenario: Start datastore for all scenarios0.69 sec003030
Scenario: Start event broker for all scenarios0.33 sec0036-1436-14
Scenario: Starting and stopping the simulator should create a device entry and properly set its status11 ms002020
Scenario: Stealing link scenario17 ms002828
Scenario: Step definition factory sanity checks5 ms0022
Scenario: Step definition with a duplicate name7 ms0066
Scenario: Step definition with a null name4 ms0066
Scenario: Step definition with a null scope ID6 ms0066
Scenario: Step definition with an empty name6 ms0055
Scenario: Stop broker after all scenarios0.26 sec0032-1432-14
Scenario: Stop datastore after all scenarios0.22 sec003030
Scenario: Stop event broker for all scenarios0.31 sec0036-1436-14
Scenario: Test account query3 ms0044
Scenario: Test the message store with server timestamp indexing29 ms002626
Scenario: Test the message store with timestamp indexing29 ms002626
Scenario: The Client ID is case sensitive5 ms0088
Scenario: To be defined8 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"25 ms0044
Scenario: Translating CommandRequestMessage to null8 ms0044
Scenario: Translating empty message to empty message5 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"5 ms0044
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message2 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message3 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message2 ms0055
Scenario: Translating kura data message with null channel, and payload without body and with metrics3 ms0055
Scenario: Translating kura data message with valid channel and with null payload5 ms0055
Scenario: Translating kura data message with valid channel and without body and metrics into jms message3 ms0055
Scenario: Translating kura data message with valid channel, and with null payload1 ms0055
Scenario: Translating kura data message with valid channel, body and metrics into jms message1 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into jms message3 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message6 ms0055
Scenario: Translating null to KuraRequestMessage6 ms0044
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message2 ms0055
Scenario: Translating of jms message with empty payload and valid topic into kura data message3 ms0066
Scenario: Translating of jms message with invalid payload and valid topic into kura data message3 ms0066
Scenario: Translating of jms message with valid payload and valid topic into kura data message3 ms0066
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message4 ms0055
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message3 ms0055
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message4 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message3 ms0055
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message3 ms0055
Scenario: Translation of mqtt message with empty payload into kura data message5 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message6 ms0055
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message5 ms0066
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message5 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message3 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message5 ms0066
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message5 ms0066
Scenario: Try to add two different roles with same permissions14 ms002121
Scenario: Try to change an existing connection ID3 ms0077
Scenario: Try to delete a non existing device from the registry3 ms0044
Scenario: Try to find a device with an invalid client ID3 ms0033
Scenario: Try to find a device with an invalid registry ID3 ms0033
Scenario: Try to find users granted to "admin" role10 ms001212
Scenario: Try to find users that have assigned specific role12 ms001212
Scenario: Try to modify the connection client ID4 ms0077
Scenario: Try to update the device client ID3 ms0044
Scenario: Update a non existing device3 ms0055
Scenario: Update a nonexistent step definition6 ms0077
Scenario: Update a step definition name6 ms0077
Scenario: Update a step definition processor name5 ms0088
Scenario: Update a step definition target type10 ms0088
Scenario: Update schedule which doesn't exist5 ms0055
Scenario: Update scheduler end date9 ms0099
Scenario: Update scheduler name6 ms0088
Scenario: Update scheduler start date7 ms0088
Scenario: Update trigger definition13 ms0088
Scenario: Update user8 ms0077
Scenario: Update user that doesn't exist3 ms0055
Scenario: User locking itself out by using out login attempts8 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock13 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock5 ms001717
Scenario: User login with wrong pass, but with enough time between login failures6 ms001919
Scenario: User not locking itself out by using less than max failed login attempts6 ms001717
Scenario: Validate a device client based search with a null client ID3 ms0055
Scenario: Validate a device client based search with an empty client ID3 ms0055
Scenario: Validate a device client search with null scope3 ms0055
Scenario: Validate a device creator with a null client ID3 ms0066
Scenario: Validate a device creator with a null scope ID3 ms0066
Scenario: Validate a device query with a null Scope ID3 ms0044
Scenario: Validate a device search with a null device ID6 ms0066
Scenario: Validate a device search with a null scope ID5 ms0066
Scenario: Validate a null creator3 ms0055
Scenario: Validate a null device2 ms0055
Scenario: Validate a null device count12 ms0055
Scenario: Validate a null device query3 ms0055
Scenario: Validate a regular creator3 ms0044
Scenario: Validate a regular device client search4 ms0044
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device query3 ms0044
Scenario: Validate a regular device search3 ms0055
Scenario: Validate deleting a device with a null device ID3 ms0066
Scenario: Validate deleting a device with a null scope ID2 ms0066
empty) scope0 ms0044