Test Result : (root)

6 failures (-10) , 28 skipped (-93)
6,896 tests (-9703)
Took 10 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device5 ms14
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events3 ms633
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.And I confirm the executed job is finished30 ms633
 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 Time30 ms14
 Scenario: Executing Job When Device Connected Before End Date And Time.And I confirm the executed job is finished5 ms633
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time7 ms14

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 topic25 ms0088
Scenario: Account based ClientInfo data check23 ms002424
Scenario: Account name must not be mutable3 ms0066
Scenario: Account wide metrics check21 ms002828
Scenario: Add Access Info domain permissions to new user18 ms002626
Scenario: Add Account permissions to the role in child account20 ms002828
Scenario: Add Credential domain permissions to new user13 ms001818
Scenario: Add Datastore domain permissions to new user87 ms001919
Scenario: Add Device Connection domain permissions to kapua-sys user9 ms001111
Scenario: Add Device Connection domain permissions to new user11 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 user11 ms001717
Scenario: Add Domain domain permissions to new user9 ms003232
Scenario: Add Endpoint Permission To The User10 ms003030
Scenario: Add Endpoint_info permissions to the role in child account14 ms003030
Scenario: Add Group domain permissions to new user22 ms001717
Scenario: Add Group permissions to the role in child account16 ms002626
Scenario: Add Job domain permissions to new user14 ms001919
Scenario: Add Role domain permissions to new user15 ms001717
Scenario: Add Role permissions to the role in child account24 ms002626
Scenario: Add Scheduler Permissions With Job Permissions13 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions12 ms002121
Scenario: Add Scheduler permissions to the role in child account19 ms003636
Scenario: Add Tag domain permissions to new user12 ms001515
Scenario: Add Tag permissions to the role in child account17 ms002626
Scenario: Add User domain permissions to new user11 ms002020
Scenario: Add account permissions to the role17 ms001919
Scenario: Add admin role to the user22 ms004444
Scenario: Add and delete Account permissions from the "admin" role14 ms001414
Scenario: Add and delete Device permissions from the "admin" role15 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role16 ms001414
Scenario: Add and delete Group permissions from the "admin" role22 ms001414
Scenario: Add and delete Job permissions from the "admin" role12 ms001414
Scenario: Add and delete Role permissions from the "admin" role17 ms001414
Scenario: Add and delete User permissions from the "admin" role13 ms001515
Scenario: Add datastore permissions to the role20 ms002727
Scenario: Add deleted role again15 ms001010
Scenario: Add device event permissions to the role12 ms003232
Scenario: Add device permissions to the role30 ms001919
Scenario: Add device permissions to the role in child account15 ms002626
Scenario: Add domain, user and access_info permissions to the role11 ms002323
Scenario: Add endpoint_info permissions to the role14 ms003131
Scenario: Add group permissions to the role16 ms001818
Scenario: Add job permissions to the role10 ms001919
Scenario: Add job permissions to the role in child account20 ms002626
Scenario: Add role permissions to the role27 ms001919
Scenario: Add same permission twice to the same role10 ms001414
Scenario: Add same role to user twice17 ms001313
Scenario: Add scheduler permissions to the role40 ms003131
Scenario: Add tag permissions to the role16 ms001818
Scenario: Add user permissions to the role18 ms001919
Scenario: Add user permissions to the role in child account17 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters8 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 Format9 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only7 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time8 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter10 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter9 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only8 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time5 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter7 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters17 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only8 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time10 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name10 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name13 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only11 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter7 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name8 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter10 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only11 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time8 ms001111
Scenario: Adding "Device Connect" Schedule Without Name9 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter9 ms0099
Scenario: Adding "Interval Job" Schedule With All Valid Parameters10 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only5 ms001010
Scenario: Adding "Interval Job" Schedule With End Time before Start time7 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name9 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name15 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only8 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter6 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name9 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter30 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number6 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only8 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time8 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number8 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter10 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name11 ms001111
Scenario: Adding "admin" role to a user in a child account20 ms001414
Scenario: Adding "admin" role to multiple users15 ms001818
Scenario: Adding "admin" role twice14 ms001313
Scenario: Adding Account:Delete permission to user in same scope18 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope14 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope14 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope15 ms001919
Scenario: Adding Account:Read permission to user in same scope13 ms002323
Scenario: Adding Account:Read permission to user in sub-account scope12 ms002929
Scenario: Adding Account:Write and Account:Delete permission to user in same scope11 ms002323
Scenario: Adding Account:Write permission to user in same scope10 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope13 ms003131
Scenario: Adding Multiple Permissions To User18 ms002020
Scenario: Adding One Permission To User17 ms001111
Scenario: Adding Permissions To Child User14 ms001818
Scenario: Adding Permissions To Parallel User16 ms001818
Scenario: Adding Previously Deleted Permission15 ms002828
Scenario: Adding all Account permissions to user in same scope14 ms001717
Scenario: Adding all Account permissions to user in sub-account scope13 ms002424
Scenario: Adding existing roles to user24 ms001515
Scenario: Adding role from child account to user in new child account12 ms001515
Scenario: Adding role to multiple users in child account12 ms001818
Scenario: Adding same role twice to user in child account9 ms001515
Scenario: Adding the same role to user twice in child account18 ms001313
Scenario: All device parameters must match the device creator5 ms0033
Scenario: B1 Broker publish to CTRL_ACC_REPLY33 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 allowed12 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI27 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed18 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed13 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY30 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY19 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account16 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed21 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed20 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed14 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI18 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed25 ms0099
Scenario: Basic Device Event queries12 ms001010
Scenario: Birth and applications event handling7 ms001212
Scenario: Birth and death message handling5 ms001212
Scenario: Birth and missing event handling6 ms001212
Scenario: Birth message handling from a new device17 ms001313
Scenario: Birth message handling from an existing device4 ms001212
Scenario: Captured date based ClientInfo data check22 ms003030
Scenario: Case sensitiveness of named device searches3 ms0044
Scenario: Change role name so it is too short2 ms0066
Scenario: Change the account parent path3 ms0055
Scenario: Changing Client ID11 ms0099
Scenario: Changing Device Status To Disabled7 ms0099
Scenario: Changing Device Status To Enabled7 ms0099
Scenario: Changing description of a nonexisting role3 ms0077
Scenario: Changing job description to non-unique one5 ms0077
Scenario: Changing job description to the long one5 ms0066
Scenario: Changing job description to unique one5 ms0066
Scenario: Changing job description to very short one8 ms0077
Scenario: Changing job name to a long one without description7 ms0077
Scenario: Changing job name to a too long one without description1 ms0055
Scenario: Changing job name to a too short one without description5 ms0066
Scenario: Changing job name to contain invalid symbols in name without description12 ms0044
Scenario: Changing job name to contain permitted symbols in name without description5 ms0055
Scenario: Changing job name to non-unique one11 ms0088
Scenario: Changing job name to short one without description10 ms0077
Scenario: Changing job name to unique one5 ms0099
Scenario: Changing name of a nonexisting role9 ms0077
Scenario: Changing role description to a valid one5 ms0066
Scenario: Changing role name so it is too long2 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 filters18 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id27 ms002828
Scenario: ChannelInfo client ID based on the account id33 ms002626
Scenario: ChannelInfo last published date19 ms003030
Scenario: ChannelInfo topic data based on the account id19 ms002626
Scenario: Check account properties5 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency18 ms003030
Scenario: Check the mapping for message semantic topics22 ms003030
Scenario: Check the message store22 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization2 ms0022
Scenario: Client Id based ClientInfo data check26 ms002828
Scenario: Connect to the system and publish some data0.11 sec002222
Scenario: Connection Service factory sanity checks3 ms0022
Scenario: Count connections in empty scope3 ms0044
Scenario: Count connections in scope4 ms0055
Scenario: Count devices with a specific BIOS version5 ms0066
Scenario: Count events in empty scope8 ms0066
Scenario: Count step definition items4 ms0044
Scenario: Count step definitions in wrong (empty) scope6 ms0011
Scenario: Count user5 ms0066
Scenario: Counting created roles items in the DB4 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 entry44 ms0066
Scenario: Create an event with a null scope ID10 ms0077
Scenario: Create index with specific prefix9 ms001212
Scenario: Create multiple users3 ms0055
Scenario: Create same user in different accounts22 ms001515
Scenario: Create scheduler with correct end date13 ms0088
Scenario: Create scheduler with empty schedule name13 ms0088
Scenario: Create scheduler with end date before start date9 ms0099
Scenario: Create scheduler with invalid Retry Interval property9 ms0099
Scenario: Create scheduler with invalid cron job trigger property6 ms0099
Scenario: Create scheduler with invalid schedule name17 ms0088
Scenario: Create scheduler with short schedule name9 ms0088
Scenario: Create scheduler with too long schedule name11 ms0088
Scenario: Create scheduler with valid Retry Interval property5 ms0077
Scenario: Create scheduler with valid cron job trigger property13 ms0077
Scenario: Create scheduler with valid schedule name30 ms0066
Scenario: Create scheduler without Cron Job Trigger property10 ms0099
Scenario: Create scheduler without Retry Interval property7 ms0099
Scenario: Create scheduler without start date8 ms0077
Scenario: Create user that already exist6 ms0077
Scenario: Create user that has more than DB allowed length10 ms0055
Scenario: Create user with short name8 ms0055
Scenario: Create user with special characters in his name8 ms0055
Scenario: Creating A Device With Disabled Status6 ms0077
Scenario: Creating A Device With Enabled Status12 ms0077
Scenario: Creating A Device With Long Display Name7 ms0077
Scenario: Creating A Device With Long Name9 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols16 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols9 ms0077
Scenario: Creating A Device With No Name8 ms0088
Scenario: Creating A Device With Non-unique Display Name5 ms0077
Scenario: Creating A Device With Non-unique Name11 ms001010
Scenario: Creating A Device With Short Display Name12 ms0077
Scenario: Creating A Device With Short Name7 ms0077
Scenario: Creating A Device With Too Long Display Name8 ms0088
Scenario: Creating A Device With Too Long Name12 ms0088
Scenario: Creating A Device With Unique Name15 ms0099
Scenario: Creating a Access Group with invalid special symbols in name1 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name4 ms0077
Scenario: Creating a Device With Unique Display Name11 ms0088
Scenario: Creating a job with name only10 ms0066
Scenario: Creating a job with null name15 ms0055
Scenario: Creating a job without name with valid description3 ms0055
Scenario: Creating a role name with allowed symbols in its name3 ms0055
Scenario: Creating a role with 255 characters long description3 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 name4 ms0055
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough2 ms0055
Scenario: Creating a role with special characters in the description3 ms0044
Scenario: Creating a role with the name that contains digits2 ms0055
Scenario: Creating a role with too long name2 ms0055
Scenario: Creating a role with too short name2 ms0055
Scenario: Creating a role with valid name and with too long description6 ms0033
Scenario: Creating a role wtih 255 characters long name3 ms0055
Scenario: Creating a single device with case sensitive clientID5 ms0055
Scenario: Creating a single device with clientID that contains 255 characters4 ms0055
Scenario: Creating a single device with clientID that contains 256 characters3 ms0044
Scenario: Creating a single device with clientID that contains invalid character4 ms0044
Scenario: Creating a single device with clientID that contains invalid characters2 ms0044
Scenario: Creating a single device with spaces in clientID5 ms0055
Scenario: Creating a single device with valid clientID4 ms0055
Scenario: Creating a valid Access Group with numbers in name6 ms0055
Scenario: Creating a valid Access Group with only numbers in name6 ms0055
Scenario: Creating a valid Access Group with unique name22 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name6 ms0055
Scenario: Creating a valid role2 ms0055
Scenario: Creating an Access Group with empty name8 ms0044
Scenario: Creating an Access Group with long name7 ms0055
Scenario: Creating an Access Group with short name6 ms0055
Scenario: Creating an Access Group with too long name6 ms0044
Scenario: Creating an Access Group with too short name8 ms0044
Scenario: Creating an Access Group without name and with description4 ms0044
Scenario: Creating index with regular user19 ms002525
Scenario: Creating job with invalid symbols in name without description6 ms0044
Scenario: Creating job with long name and valid description7 ms0066
Scenario: Creating job with long name without description9 ms0066
Scenario: Creating job with numbers in name and valid description6 ms0066
Scenario: Creating job with numbers in name without description7 ms0066
Scenario: Creating job with permitted symbols in name without description8 ms0033
Scenario: Creating job with short name and valid job description5 ms0066
Scenario: Creating job with short name without description19 ms0066
Scenario: Creating job with too long name and valid description6 ms0055
Scenario: Creating job with too long name without description6 ms0055
Scenario: Creating job with too short name and valid description5 ms0055
Scenario: Creating job with too short name without description7 ms0055
Scenario: Creating job without name and without description6 ms0055
Scenario: Creating new device and tagging it with specific Tag9 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag7 ms001616
Scenario: Creating non-unique Access Group6 ms0055
Scenario: Creating non-unique Access Group with unique description4 ms0055
Scenario: Creating non-unique job name with valid job description6 ms0077
Scenario: Creating tag51 ms0044
Scenario: Creating two device with the same clientID5 ms0055
Scenario: Creating two indexes with daily index11 ms001717
Scenario: Creating two indexes with hourly index9 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 name3 ms0077
Scenario: Creating unique Access Group with long description2 ms0055
Scenario: Creating unique Access Group with non-unique description5 ms0066
Scenario: Creating unique Access Group with numbers in description4 ms0055
Scenario: Creating unique Access Group with only numbers in description5 ms0055
Scenario: Creating unique Access Group with short description3 ms0055
Scenario: Creating unique Access Group with special symbols in description3 ms0044
Scenario: Creating unique Access Group with unique description4 ms0055
Scenario: Creating unique job with long description6 ms0066
Scenario: Creating unique job with non-unique description7 ms001010
Scenario: Creating unique job with short description6 ms0066
Scenario: Creating user23 ms0055
Scenario: D1 Device publish to CTRL_ACC_REPLY14 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI9 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed11 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed10 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY19 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY12 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account11 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC14 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI15 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed23 ms0099
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed9 ms0099
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed7 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed20 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI18 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed19 ms0099
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed9 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY21 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY14 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account10 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed15 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed23 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed6 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI23 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC18 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY13 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed14 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed11 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 allowed17 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed12 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_REPLY14 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY9 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account12 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed11 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed13 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed10 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI13 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed8 ms0099
Scenario: Delete Kapua system user8 ms0055
Scenario: Delete a connection from the database4 ms0088
Scenario: Delete a non existent event5 ms0077
Scenario: Delete a non existing connection2 ms0077
Scenario: Delete a step definition6 ms0088
Scenario: Delete a step definition twice9 ms0077
Scenario: Delete access role from user11 ms001212
Scenario: Delete an existing account4 ms0055
Scenario: Delete an existing device from the registry3 ms0044
Scenario: Delete an existing event5 ms0099
Scenario: Delete items based on query results28 ms008484
Scenario: Delete items by date ranges0.62 sec00132132
Scenario: Delete items by the datastore ID25 ms006666
Scenario: Delete nonexisting account5 ms0044
Scenario: Delete permissions from role17 ms001818
Scenario: Delete scheduler5 ms0088
Scenario: Delete scheduler which doesn't exist6 ms0055
Scenario: Delete the Kapua system account3 ms0055
Scenario: Delete user8 ms0066
Scenario: Delete user that doesn't exist3 ms0055
Scenario: Deleting "Cron Schedule" Triggering8 ms001313
Scenario: Deleting "Device Schedule" Triggering7 ms001111
Scenario: Deleting "Interval Schedule" Triggering7 ms001313
Scenario: Deleting Device With Disabled Status8 ms001010
Scenario: Deleting Device With Enabled Status7 ms001010
Scenario: Deleting a Permission16 ms002121
Scenario: Deleting a non-existing Access Group4 ms0066
Scenario: Deleting a role twice2 ms0077
Scenario: Deleting admin role11 ms0077
Scenario: Deleting an existing Access Group3 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name4 ms0077
Scenario: Deleting an existing role3 ms0066
Scenario: Deleting default permissions from admin role12 ms001212
Scenario: Deleting role after adding it to user14 ms001414
Scenario: Deleting role after it has been added to user in child account9 ms001616
Scenario: Deleting tag16 ms0044
Scenario: Deleting user in account that is higher in hierarchy18 ms002323
Scenario: Deleting user in account that is lower in hierarchy21 ms002424
Scenario: Device connection update3 ms0077
Scenario: Device factory sanity checks1 ms0022
Scenario: Device queries3 ms001010
Scenario: Device query - find by BIOS version5 ms0077
Scenario: Editing Access Group description to description with numbers3 ms0055
Scenario: Editing Access Group description to description with only numbers3 ms0055
Scenario: Editing Access Group description to description with special symbols2 ms0044
Scenario: Editing Access Group description to long description2 ms0055
Scenario: Editing Access Group description to non-unique one6 ms0055
Scenario: Editing Access Group description to short description2 ms0055
Scenario: Editing Access Group description to unique one3 ms0077
Scenario: Editing Access Group name to a long one4 ms0077
Scenario: Editing Access Group name to a too long one3 ms0055
Scenario: Editing Access Group name to empty name4 ms0055
Scenario: Editing Access Group name to name that contains numbers2 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 symbols2 ms0077
Scenario: Editing Access Group name to non-unique one2 ms0066
Scenario: Editing Access Group name to short one5 ms0077
Scenario: Editing Access Group name to too short one2 ms0055
Scenario: Editing Access Group name to valid one3 ms0077
Scenario: Event factory sanity checks6 ms0022
Scenario: Event service domain check3 ms0022
Scenario: Every account must have the default configuration items5 ms0033
Scenario: Executing Job And Then Restarting Device7 ms2162745
Scenario: Executing Job When Device Connected After End Date And Time21 ms003838
Scenario: Executing Job When Device Connected After The Specified Start Date And Time60 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 Time34 ms003737
Scenario: Executing Job Without Steps25 ms004040
Scenario: Find a connection by its IDs3 ms0066
Scenario: Find a connection by its client ID3 ms0066
Scenario: Find a non existing event6 ms0066
Scenario: Find account by Id10 ms0044
Scenario: Find account by Ids5 ms0044
Scenario: Find account by name4 ms0044
Scenario: Find account by random Id6 ms0033
Scenario: Find all child accounts9 ms0033
Scenario: Find an event by its ID6 ms0066
Scenario: Find by name nonexisting account3 ms0033
Scenario: Find correct number of messages by corresponding metric0.2 sec005858
Scenario: Find device by client ID3 ms0033
Scenario: Find device by registry ID4 ms0044
Scenario: Find multiple users4 ms0055
Scenario: Find user by id5 ms0055
Scenario: Find user by its email3 ms0066
Scenario: Find user by its phone number3 ms0066
Scenario: Find user by name4 ms0055
Scenario: Find user by name that doesn't exist3 ms0033
Scenario: Find user with id and scope id that doesn't exist4 ms0033
Scenario: Finding all messages by selecting all metrics0.16 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.18 sec005252
Scenario: Finding messages with incorrect metric parameters0.22 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 present2 ms0066
Scenario: Generic connection query4 ms0088
Scenario: Get metadata4 ms0033
Scenario: Handle account creation29 ms0033
Scenario: Handle duplicate account names7 ms0055
Scenario: Handle null account name8 ms0044
Scenario: Handling of 2 birth messages8 ms001212
Scenario: Handling of a disconnect message from a non existing device8 ms001010
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 inclusive6 ms001414
Scenario: If user credential expiration date is tomorrow, user can login3 ms001313
Scenario: If user credential is in state disabled, user can not login9 ms001414
Scenario: If user credential is in state enabled, user can login3 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 reached11 ms001313
Scenario: If user expiration date is tomorrow, user can login7 ms001212
Scenario: Init Security Context for all scenarios69 ms0012-3812-38
Scenario: Installing a package21 ms001313
Scenario: Interval Job" Schedule With Too Long Name6 ms001111
Scenario: It should not be possible to change the configuration items3 ms0055
Scenario: MetricsInfo client ID and topic data based on the client id19 ms003434
Scenario: MetricsInfo last published date18 ms004848
Scenario: Modify an existing account3 ms0044
Scenario: Modify nonexisting account3 ms0066
Scenario: Modifying Sub-account of a different parent account10 ms002525
Scenario: Negative scenario when client connects twice with same client id18 ms001111
Scenario: Positive scenario without stealing link13 ms001212
Scenario: Query based on message ordering19 ms002020
Scenario: Query based on metrics ordering27 ms002020
Scenario: Query before schema search26 ms008282
Scenario: Query for step definitions5 ms0077
Scenario: Query user6 ms0066
Scenario: Querying Other Items With All Account Permissions22 ms003939
Scenario: Regular connection6 ms0077
Scenario: Regular step definition creation6 ms0077
Scenario: Regular step definition with a property list5 ms0044
Scenario: Reset Security Context for all scenarios58 ms0012-3812-38
Scenario: Search By Client ID And Get Multiple Matches24 ms003737
Scenario: Search By Client ID And Get No Matches9 ms001010
Scenario: Search By Client ID And Get One Match6 ms0088
Scenario: Search By Client ID and Display Name5 ms001212
Scenario: Search By Client ID and Serial Number10 ms001212
Scenario: Search By Client ID and Status9 ms001212
Scenario: Search By Client ID, Display Name and Serial Number11 ms001212
Scenario: Search By Client ID, Display Name and Status5 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status9 ms001212
Scenario: Search By Device Status And Get No Matches6 ms0088
Scenario: Search By Device's Display Name And Get One Match8 ms0088
Scenario: Search By Display Name and Serial Number9 ms001212
Scenario: Search By Display Name and Status6 ms001212
Scenario: Search By Full Client ID And Get One Match5 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches6 ms0088
Scenario: Search By One Letter Of Display Name15 ms0088
Scenario: Search By One Letter Of Serial Number10 ms001212
Scenario: Search By Serial Number And Get Multiple Matches12 ms001414
Scenario: Search By Serial Number And Get No Matches9 ms001010
Scenario: Search By Serial Number And Get One Match7 ms001111
Scenario: Search By Serial Number and Status8 ms001212
Scenario: Search By Serial Number, Display Name and Status9 ms001212
Scenario: Search By Specific Serial Number10 ms001010
Scenario: Search By Status And Get Multiple Matches7 ms001010
Scenario: Search by Device Status And Get One Match10 ms001010
Scenario: Search for a non existent client ID3 ms0066
Scenario: Send BIRTH message and then DC message17 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set46 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System36 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file44 ms0088
Scenario: Set environment variables90 ms0043-1843-18
Scenario: Setting configuration without mandatory items must raise an error3 ms0055
Scenario: Simple positive scenario for creating daily index10 ms001414
Scenario: Simple positive scenario for creating default - weekly index9 ms001212
Scenario: Simple positive scenario for creating hourly index12 ms001414
Scenario: Start broker for all scenarios0.27 sec0030-1430-14
Scenario: Start datastore for all scenarios1.3 sec003030
Scenario: Start event broker for all scenarios0.38 sec0036-1436-14
Scenario: Starting and stopping the simulator should create a device entry and properly set its status15 ms002020
Scenario: Stealing link scenario21 ms002828
Scenario: Step definition factory sanity checks3 ms0022
Scenario: Step definition with a duplicate name6 ms0066
Scenario: Step definition with a null name3 ms0066
Scenario: Step definition with a null scope ID5 ms0066
Scenario: Step definition with an empty name5 ms0055
Scenario: Stop broker after all scenarios0.25 sec0032-1432-14
Scenario: Stop datastore after all scenarios0.17 sec003030
Scenario: Stop event broker for all scenarios0.29 sec0036-1436-14
Scenario: Test account query2 ms0044
Scenario: Test the message store with server timestamp indexing19 ms002626
Scenario: Test the message store with timestamp indexing18 ms002626
Scenario: The Client ID is case sensitive5 ms0088
Scenario: To be defined7 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"26 ms0044
Scenario: Translating CommandRequestMessage to null9 ms0044
Scenario: Translating empty message to empty message7 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"4 ms0044
Scenario: Translating null to KuraRequestMessage6 ms0044
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message3 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 message4 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 message9 ms0066
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message4 ms0055
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message6 ms0066
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message3 ms0066
Scenario: Try to add two different roles with same permissions12 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 ID2 ms0033
Scenario: Try to find a device with an invalid registry ID4 ms0033
Scenario: Try to find users granted to "admin" role13 ms001212
Scenario: Try to find users that have assigned specific role9 ms001212
Scenario: Try to modify the connection client ID3 ms0077
Scenario: Try to update the device client ID3 ms0044
Scenario: Update a non existing device2 ms0055
Scenario: Update a nonexistent step definition23 ms0077
Scenario: Update a step definition name5 ms0077
Scenario: Update a step definition processor name10 ms0088
Scenario: Update a step definition target type11 ms0088
Scenario: Update schedule which doesn't exist5 ms0055
Scenario: Update scheduler end date8 ms0099
Scenario: Update scheduler name6 ms0088
Scenario: Update scheduler start date5 ms0088
Scenario: Update trigger definition10 ms0088
Scenario: Update user7 ms0077
Scenario: Update user that doesn't exist3 ms0055
Scenario: User locking itself out by using out login attempts11 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock5 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock4 ms001717
Scenario: User login with wrong pass, but with enough time between login failures5 ms001919
Scenario: User not locking itself out by using less than max failed login attempts4 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 ID2 ms0055
Scenario: Validate a device client search with null scope2 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 ID9 ms0044
Scenario: Validate a device search with a null device ID3 ms0066
Scenario: Validate a device search with a null scope ID3 ms0066
Scenario: Validate a null creator2 ms0055
Scenario: Validate a null device1 ms0055
Scenario: Validate a null device count2 ms0055
Scenario: Validate a null device query2 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 query2 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 ID3 ms0066
empty) scope0 ms0044