Test Result : (root)

8 failures (-12) , 29 skipped (-130)
8,970 tests (-7544)
Took 13 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 description10 ms29
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"9 ms29
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device7 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 finished35 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 Time38 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 Time6 ms6

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A newly created account must have some metadata4 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic10 ms0088
Scenario: Account based ClientInfo data check28 ms002424
Scenario: Account name must not be mutable3 ms0066
Scenario: Account wide metrics check36 ms002828
Scenario: Add Access Info domain permissions to new user34 ms002626
Scenario: Add Account permissions to the role in child account9 ms002828
Scenario: Add Credential domain permissions to new user17 ms001818
Scenario: Add Datastore domain permissions to new user0.27 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user10 ms001111
Scenario: Add Device Connection domain permissions to new user9 ms002323
Scenario: Add Device Event domain permissions to new user19 ms001616
Scenario: Add Device domain permissions to new user15 ms001717
Scenario: Add Domain domain permissions to kapua-sys user14 ms001717
Scenario: Add Domain domain permissions to new user12 ms003232
Scenario: Add Endpoint Permission To The User13 ms003030
Scenario: Add Endpoint_info permissions to the role in child account16 ms003030
Scenario: Add Group domain permissions to new user13 ms001717
Scenario: Add Group permissions to the role in child account15 ms002626
Scenario: Add Job domain permissions to new user14 ms001919
Scenario: Add Role domain permissions to new user19 ms001717
Scenario: Add Role permissions to the role in child account16 ms002626
Scenario: Add Scheduler Permissions With Job Permissions22 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions13 ms002121
Scenario: Add Scheduler permissions to the role in child account17 ms003636
Scenario: Add Tag domain permissions to new user13 ms001515
Scenario: Add Tag permissions to the role in child account20 ms002626
Scenario: Add User domain permissions to new user14 ms002020
Scenario: Add account permissions to the role11 ms001919
Scenario: Add admin role to the user18 ms004444
Scenario: Add and delete Account permissions from the "admin" role21 ms001414
Scenario: Add and delete Device permissions from the "admin" role9 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role11 ms001414
Scenario: Add and delete Group permissions from the "admin" role14 ms001414
Scenario: Add and delete Job permissions from the "admin" role20 ms001414
Scenario: Add and delete Role permissions from the "admin" role4 ms001414
Scenario: Add and delete User permissions from the "admin" role9 ms001515
Scenario: Add datastore permissions to the role17 ms002727
Scenario: Add deleted role again23 ms001010
Scenario: Add device event permissions to the role18 ms003232
Scenario: Add device permissions to the role17 ms001919
Scenario: Add device permissions to the role in child account13 ms002626
Scenario: Add domain, user and access_info permissions to the role13 ms002323
Scenario: Add endpoint_info permissions to the role21 ms003131
Scenario: Add group permissions to the role12 ms001818
Scenario: Add job permissions to the role21 ms001919
Scenario: Add job permissions to the role in child account8 ms002626
Scenario: Add role permissions to the role17 ms001919
Scenario: Add same permission twice to the same role14 ms001414
Scenario: Add same role to user twice17 ms001313
Scenario: Add scheduler permissions to the role14 ms003131
Scenario: Add tag permissions to the role14 ms001818
Scenario: Add user permissions to the role19 ms001919
Scenario: Add user permissions to the role in child account15 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters10 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters And Null Cron Value9 ms001010
Scenario: Adding "Cron Job" Schedule With All Valid Parameters Except Cron Format7 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only20 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time7 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter13 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter5 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only11 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time7 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter7 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters7 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only5 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time6 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name8 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name8 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only16 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 Parameter6 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only8 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 Parameter20 ms0099
Scenario: Adding "Empty" Tag To Device5 ms0055
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 time12 ms001212
Scenario: Adding "Interval Job" Schedule With Max Length Name6 ms001010
Scenario: Adding "Interval Job" Schedule With Min Length Name8 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only10 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter26 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name24 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter16 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number6 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only6 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time8 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number19 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter17 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name8 ms001111
Scenario: Adding "admin" role to a user in a child account20 ms001414
Scenario: Adding "admin" role to multiple users18 ms001818
Scenario: Adding "admin" role twice20 ms001313
Scenario: Adding Account:Delete permission to user in same scope13 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope11 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope16 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope11 ms001919
Scenario: Adding Account:Read permission to user in same scope10 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 scope20 ms002323
Scenario: Adding Account:Write permission to user in same scope13 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope12 ms003131
Scenario: Adding Multiple Permissions To User14 ms002020
Scenario: Adding One Permission To User20 ms001111
Scenario: Adding Permissions To Child User18 ms001818
Scenario: Adding Permissions To Parallel User15 ms001818
Scenario: Adding Previously Deleted Permission12 ms002828
Scenario: Adding Previously Deleted Tag From Device Again6 ms001111
Scenario: Adding Regular Tag Without Description To Device8 ms0066
Scenario: Adding Tag With Long Name Without Description To Device6 ms0066
Scenario: Adding Tag With Numbers Without Description To Device3 ms0066
Scenario: Adding Tag With Short Name Without Description To Device4 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device4 ms0066
Scenario: Adding all Account permissions to user in same scope13 ms001717
Scenario: Adding all Account permissions to user in sub-account scope17 ms002424
Scenario: Adding existing roles to user11 ms001515
Scenario: Adding role from child account to user in new child account13 ms001515
Scenario: Adding role to multiple users in child account17 ms001818
Scenario: Adding same role twice to user in child account13 ms001515
Scenario: Adding the same role to user twice in child account9 ms001313
Scenario: All device parameters must match the device creator4 ms0033
Scenario: B1 Broker publish to CTRL_ACC_REPLY22 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed19 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed13 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI20 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed15 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed6 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY17 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY19 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed10 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed21 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed8 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI22 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed14 ms0099
Scenario: Basic Device Event queries7 ms001010
Scenario: Birth and applications event handling4 ms001212
Scenario: Birth and death message handling12 ms001212
Scenario: Birth and missing event handling10 ms001212
Scenario: Birth message handling from a new device8 ms001313
Scenario: Birth message handling from an existing device10 ms001212
Scenario: Captured date based ClientInfo data check25 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 ID10 ms0099
Scenario: Changing Description On Tag With Long Description7 ms0044
Scenario: Changing Description On Tag With Long Name4 ms0055
Scenario: Changing Description On Tag With Numbers In Name5 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name7 ms0044
Scenario: Changing Description On Tag With Short Description4 ms0044
Scenario: Changing Description On Tag With Short Name4 ms0044
Scenario: Changing Device Status To Disabled8 ms0099
Scenario: Changing Device Status To Enabled10 ms0099
Scenario: Changing Tag's Description To Non-Unique One6 ms0055
Scenario: Changing Tag's Description To Unique One5 ms0077
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description3 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 Description5 ms0077
Scenario: Changing Tag's Name To Unique One9 ms0077
Scenario: Changing Tag's Name To a Long One Without Description5 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 Description11 ms0055
Scenario: Changing description of a nonexisting role3 ms0077
Scenario: Changing job description to non-unique one5 ms0077
Scenario: Changing job description to the long one10 ms0066
Scenario: Changing job description to unique one7 ms0066
Scenario: Changing job description to very short one7 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 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 description6 ms0055
Scenario: Changing job name to non-unique one13 ms0088
Scenario: Changing job name to short one without description13 ms0077
Scenario: Changing job name to unique one12 ms0099
Scenario: Changing name of a nonexisting role6 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 character4 ms0044
Scenario: Changing role name to null2 ms0066
Scenario: Changing role's name to a valid one3 ms0066
Scenario: Channel info queries based on datastore channel filters29 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id34 ms002828
Scenario: ChannelInfo client ID based on the account id41 ms002626
Scenario: ChannelInfo last published date36 ms003030
Scenario: ChannelInfo topic data based on the account id28 ms002626
Scenario: Check account properties4 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency35 ms003030
Scenario: Check the mapping for message semantic topics33 ms003030
Scenario: Check the message store34 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization3 ms0022
Scenario: Client Id based ClientInfo data check23 ms002828
Scenario: Connect to the system and publish some data0.25 sec002222
Scenario: Connection Service factory sanity checks1 ms0022
Scenario: Count connections in empty scope4 ms0044
Scenario: Count connections in scope6 ms0055
Scenario: Count devices with a specific BIOS version4 ms0066
Scenario: Count events in empty scope6 ms0066
Scenario: Count step definition items7 ms0044
Scenario: Count step definitions in wrong (empty) scope12 ms0011
Scenario: Count user8 ms0066
Scenario: Counting created roles items in the DB4 ms0055
Scenario: Create a regular event21 ms0088
Scenario: Create a single device with an empty string for clientID4 ms0044
Scenario: Create a single device with null clientID value4 ms0044
Scenario: Create a valid job entry25 ms0066
Scenario: Create an event with a null scope ID7 ms0077
Scenario: Create index with specific prefix19 ms001212
Scenario: Create multiple users5 ms0055
Scenario: Create same user in different accounts17 ms001515
Scenario: Create scheduler with correct end date7 ms0088
Scenario: Create scheduler with empty schedule name10 ms0088
Scenario: Create scheduler with end date before start date8 ms0099
Scenario: Create scheduler with invalid Retry Interval property6 ms0099
Scenario: Create scheduler with invalid cron job trigger property11 ms0099
Scenario: Create scheduler with invalid schedule name14 ms0088
Scenario: Create scheduler with short schedule name15 ms0088
Scenario: Create scheduler with too long schedule name12 ms0088
Scenario: Create scheduler with valid Retry Interval property8 ms0077
Scenario: Create scheduler with valid cron job trigger property14 ms0077
Scenario: Create scheduler with valid schedule name42 ms0066
Scenario: Create scheduler without Cron Job Trigger property7 ms0099
Scenario: Create scheduler without Retry Interval property8 ms0099
Scenario: Create scheduler without start date11 ms0077
Scenario: Create user that already exist4 ms0077
Scenario: Create user that has more than DB allowed length10 ms0055
Scenario: Create user with short name10 ms0055
Scenario: Create user with special characters in his name8 ms0055
Scenario: Creating A Device With Disabled Status8 ms0077
Scenario: Creating A Device With Enabled Status14 ms0077
Scenario: Creating A Device With Long Display Name11 ms0077
Scenario: Creating A Device With Long Name10 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols13 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols4 ms0077
Scenario: Creating A Device With No Name7 ms0088
Scenario: Creating A Device With Non-unique Display Name7 ms0077
Scenario: Creating A Device With Non-unique Name9 ms001010
Scenario: Creating A Device With Short Display Name8 ms0077
Scenario: Creating A Device With Short Name10 ms0077
Scenario: Creating A Device With Too Long Display Name4 ms0088
Scenario: Creating A Device With Too Long Name9 ms0088
Scenario: Creating A Device With Unique Name8 ms0099
Scenario: Creating Non-Unique Tag With Valid Description6 ms0055
Scenario: Creating Non-unique Tag Without Description9 ms0044
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description4 ms0044
Scenario: Creating Tag With Invalid Symbols In Name Without Description2 ms0044
Scenario: Creating Tag With Long Name With Valid Description10 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 Description7 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description5 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 Description8 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description10 ms0044
Scenario: Creating Tag With Too Long Name Without Description6 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description5 ms0044
Scenario: Creating Tag With Too Short Name Without Description7 ms0044
Scenario: Creating Tag Without a Name And With Valid Description4 ms0044
Scenario: Creating Tag Without a Name And Without Description5 ms0044
Scenario: Creating Unique Tag With Long Description4 ms0044
Scenario: Creating Unique Tag With Non-unique Description5 ms0055
Scenario: Creating Unique Tag With Short Description5 ms0044
Scenario: Creating Unique Tag With Unique Description4 ms0044
Scenario: Creating Unique Tag Without Description22 ms0044
Scenario: Creating a Access Group with invalid special symbols in name15 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name8 ms0077
Scenario: Creating a Device With Unique Display Name7 ms0088
Scenario: Creating a job with name only12 ms0066
Scenario: Creating a job with null name16 ms0055
Scenario: Creating a job without name with valid description6 ms0055
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement6 ms0044
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement18 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 requirement10 ms0044
Scenario: Creating a role name with allowed symbols in its name4 ms0055
Scenario: Creating a role with 255 characters long description3 ms0055
Scenario: Creating a role with a name and description that contain digits only4 ms0055
Scenario: Creating a role with forbidden symbols in its name1 ms0044
Scenario: Creating a role with name only2 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 enough3 ms0055
Scenario: Creating a role with special characters in the description3 ms0044
Scenario: Creating a role with the name that contains digits8 ms0055
Scenario: Creating a role with too long name5 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 characters7 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 clientID4 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 name3 ms0055
Scenario: Creating a valid Access Group with unique name7 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name3 ms0055
Scenario: Creating a valid role6 ms0055
Scenario: Creating an Access Group with empty name4 ms0044
Scenario: Creating an Access Group with long name4 ms0055
Scenario: Creating an Access Group with short name6 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 description4 ms0044
Scenario: Creating index with regular user16 ms002525
Scenario: Creating job with invalid symbols in name without description3 ms0044
Scenario: Creating job with long name and valid description9 ms0066
Scenario: Creating job with long name without description17 ms0066
Scenario: Creating job with numbers in name and valid description5 ms0066
Scenario: Creating job with numbers in name without description9 ms0066
Scenario: Creating job with permitted symbols in name without description8 ms0033
Scenario: Creating job with short name and valid job description6 ms0066
Scenario: Creating job with short name without description13 ms0066
Scenario: Creating job with too long name and valid description6 ms0055
Scenario: Creating job with too long name without description10 ms0055
Scenario: Creating job with too short name and valid description5 ms0055
Scenario: Creating job with too short name without description10 ms0055
Scenario: Creating job without name and without description9 ms0055
Scenario: Creating new device and tagging it with specific Tag21 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag7 ms001616
Scenario: Creating non-unique Access Group5 ms0055
Scenario: Creating non-unique Access Group with unique description2 ms0055
Scenario: Creating non-unique job name with valid job description12 ms0077
Scenario: Creating two device with the same clientID4 ms0055
Scenario: Creating two indexes with daily index21 ms001717
Scenario: Creating two indexes with hourly index20 ms001717
Scenario: Creating two indexes with weekly index14 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 description3 ms0066
Scenario: Creating unique Access Group with numbers in description4 ms0055
Scenario: Creating unique Access Group with only numbers in description8 ms0055
Scenario: Creating unique Access Group with short description2 ms0055
Scenario: Creating unique Access Group with special symbols in description19 ms2114
Scenario: Creating unique Access Group with unique description3 ms0055
Scenario: Creating unique job with long description10 ms0066
Scenario: Creating unique job with non-unique description7 ms001010
Scenario: Creating unique job with short description6 ms0066
Scenario: Creating user15 ms0055
Scenario: D1 Device publish to CTRL_ACC_REPLY19 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI16 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed14 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed17 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY14 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY5 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account10 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC12 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI15 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed15 ms0099
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed17 ms0099
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed5 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed13 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI27 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed16 ms0099
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed12 ms0088
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY24 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY16 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account10 ms0099
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed14 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed12 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed10 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI8 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC22 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY18 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed21 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed11 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed27 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed16 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed17 ms0099
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed12 ms0088
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY20 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY11 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account11 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 allowed13 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed5 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI14 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 database2 ms0088
Scenario: Delete a non existent event6 ms0077
Scenario: Delete a non existing connection3 ms0077
Scenario: Delete a step definition6 ms0088
Scenario: Delete a step definition twice5 ms0077
Scenario: Delete access role from user11 ms001212
Scenario: Delete an existing account5 ms0055
Scenario: Delete an existing device from the registry4 ms0044
Scenario: Delete an existing event5 ms0099
Scenario: Delete items based on query results51 ms008484
Scenario: Delete items by date ranges1.1 sec0-20-37132+39132
Scenario: Delete items by the datastore ID41 ms006666
Scenario: Delete nonexisting account4 ms0044
Scenario: Delete permissions from role15 ms001818
Scenario: Delete scheduler6 ms0088
Scenario: Delete scheduler which doesn't exist7 ms0055
Scenario: Delete the Kapua system account4 ms0055
Scenario: Delete user9 ms0066
Scenario: Delete user that doesn't exist3 ms0055
Scenario: Deleting "Cron Schedule" Triggering11 ms001313
Scenario: Deleting "Device Schedule" Triggering19 ms001111
Scenario: Deleting "Interval Schedule" Triggering10 ms001313
Scenario: Deleting Device With Disabled Status9 ms001010
Scenario: Deleting Device With Enabled Status12 ms001010
Scenario: Deleting Existing Tag And Creating It Again With Same Name4 ms0077
Scenario: Deleting Non-Existent Tag4 ms0077
Scenario: Deleting Tag From Device7 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description4 ms0055
Scenario: Deleting a Permission14 ms002121
Scenario: Deleting a non-existing Access Group3 ms0066
Scenario: Deleting a role twice3 ms0077
Scenario: Deleting admin role10 ms0077
Scenario: Deleting an existing Access Group4 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name3 ms0077
Scenario: Deleting an existing role3 ms0066
Scenario: Deleting default permissions from admin role10 ms001212
Scenario: Deleting existing tag7 ms0099
Scenario: Deleting role after adding it to user16 ms001414
Scenario: Deleting role after it has been added to user in child account9 ms001616
Scenario: Deleting user in account that is higher in hierarchy18 ms002323
Scenario: Deleting user in account that is lower in hierarchy17 ms002424
Scenario: Device connection update4 ms0077
Scenario: Device factory sanity checks2 ms0022
Scenario: Device queries3 ms001010
Scenario: Device query - find by BIOS version7 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 symbols3 ms0044
Scenario: Editing Access Group description to long description3 ms0055
Scenario: Editing Access Group description to non-unique one3 ms0055
Scenario: Editing Access Group description to short description4 ms0055
Scenario: Editing Access Group description to unique one7 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 name3 ms0055
Scenario: Editing Access Group name to name that contains numbers3 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 symbols20 ms0077
Scenario: Editing Access Group name to non-unique one4 ms0066
Scenario: Editing Access Group name to short one3 ms0077
Scenario: Editing Access Group name to too short one3 ms0055
Scenario: Editing Access Group name to valid one4 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description8 ms0077
Scenario: Event factory sanity checks4 ms0022
Scenario: Event service domain check3 ms0022
Scenario: Every account must have the default configuration items3 ms0033
Scenario: Executing Job And Then Restarting Device13 ms2162745
Scenario: Executing Job When Device Connected After End Date And Time40 ms003838
Scenario: Executing Job When Device Connected After The Specified Start Date And Time77 ms263038
Scenario: Executing Job When Device Connected Before End Date And Time11 ms263139
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time42 ms003737
Scenario: Executing Job Without Steps47 ms004040
Scenario: Find a connection by its IDs4 ms0066
Scenario: Find a connection by its client ID3 ms0066
Scenario: Find a non existing event13 ms0066
Scenario: Find account by Id5 ms0044
Scenario: Find account by Ids7 ms0044
Scenario: Find account by name5 ms0044
Scenario: Find account by random Id5 ms0033
Scenario: Find all child accounts8 ms0033
Scenario: Find an event by its ID9 ms0066
Scenario: Find by name nonexisting account7 ms0033
Scenario: Find correct number of messages by corresponding metric0.52 sec005858
Scenario: Find device by client ID3 ms0033
Scenario: Find device by registry ID4 ms0044
Scenario: Find multiple users3 ms0055
Scenario: Find user by id4 ms0055
Scenario: Find user by its email4 ms0066
Scenario: Find user by its phone number3 ms0066
Scenario: Find user by name7 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.46 sec004040
Scenario: Finding correct number of messages by corresponding two metrics0.49 sec005252
Scenario: Finding messages with incorrect metric parameters0.46 sec007272
Scenario: Finding user by expiration date in the future3 ms0055
Scenario: Finding user by expiration date in the past4 ms0066
Scenario: Finding user by expiration date in the present3 ms0066
Scenario: Generic connection query4 ms0088
Scenario: Get metadata3 ms0033
Scenario: Handle account creation19 ms0033
Scenario: Handle duplicate account names7 ms0055
Scenario: Handle null account name7 ms0044
Scenario: Handling of 2 birth messages11 ms001212
Scenario: Handling of a disconnect message from a non existing device11 ms001010
Scenario: I try to find a non-existing connection4 ms0066
Scenario: If user credential expiration date is before today, user can not login4 ms001414
Scenario: If user credential expiration date is today, user can not login it is day inclusive4 ms001414
Scenario: If user credential expiration date is tomorrow, user can login7 ms001313
Scenario: If user credential is in state disabled, user can not login2 ms001414
Scenario: If user credential is in state enabled, user can login17 ms001313
Scenario: If user expiration date is before today, user can not login4 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 login4 ms001212
Scenario: Init Security Context for all scenarios58 ms0012-3612-36
Scenario: Installing a package23 ms001313
Scenario: Interval Job" Schedule With Too Long Name9 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 date27 ms004848
Scenario: Modify an existing account4 ms0044
Scenario: Modify nonexisting account3 ms0066
Scenario: Modifying Sub-account of a different parent account19 ms002525
Scenario: Negative scenario when client connects twice with same client id39 ms001111
Scenario: Positive scenario without stealing link30 ms001212
Scenario: Query based on message ordering34 ms002020
Scenario: Query based on metrics ordering22 ms002020
Scenario: Query before schema search20 ms008282
Scenario: Query for step definitions7 ms0077
Scenario: Query user4 ms0066
Scenario: Querying Other Items With All Account Permissions18 ms003939
Scenario: Regular connection8 ms0077
Scenario: Regular step definition creation6 ms0077
Scenario: Regular step definition with a property list6 ms0044
Scenario: Reset Security Context for all scenarios59 ms0012-3612-36
Scenario: Restarting a job with Asset Write and Bundle Start steps23 ms002828
Scenario: Restarting a job with Command Execution and Bundle Start steps26 ms002828
Scenario: Restarting a job with Configuration Put and Bundle Start steps22 ms002828
Scenario: Restarting a job with Package Uninstall and Bundle Start steps21 ms002828
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices24 ms003131
Scenario: Restarting job with Asset Write step19 ms002525
Scenario: Restarting job with Asset Write step and multiple devices23 ms002828
Scenario: Restarting job with Bundle Start step22 ms002525
Scenario: Restarting job with Bundle Start step and multiple devices25 ms002727
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices28 ms003131
Scenario: Restarting job with Bundle Stop and Bundle Start steps21 ms002929
Scenario: Restarting job with Bundle Stop step20 ms002525
Scenario: Restarting job with Bundle Stop step and multiple devices39 ms002727
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices26 ms003131
Scenario: Restarting job with Command Execution step26 ms002525
Scenario: Restarting job with Command Execution step and multiple devices27 ms002727
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices21 ms003131
Scenario: Restarting job with Configuration Put step30 ms002525
Scenario: Restarting job with Configuration Put step and multiple devices22 ms002727
Scenario: Restarting job with Package Download/Install and Bundle Start steps and multiple devices56 ms005959
Scenario: Restarting job with Package Download/Install step and multiple devices27 ms002727
Scenario: Restarting job with Package Install step24 ms002525
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device23 ms003131
Scenario: Restarting job with Package Uninstall step24 ms002525
Scenario: Restarting job with Package Uninstall step and multiple device26 ms002727
Scenario: Restarting job with two Bundle Start steps20 ms002929
Scenario: Restarting job with two Bundle Start steps and multiple devices20 ms003131
Scenario: Search By Client ID And Get Multiple Matches22 ms003737
Scenario: Search By Client ID And Get No Matches4 ms001010
Scenario: Search By Client ID And Get One Match11 ms0088
Scenario: Search By Client ID and Display Name5 ms001212
Scenario: Search By Client ID and Serial Number6 ms001212
Scenario: Search By Client ID and Status5 ms001212
Scenario: Search By Client ID, Display Name and Serial Number9 ms001212
Scenario: Search By Client ID, Display Name and Status5 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status18 ms001212
Scenario: Search By Device Status And Get No Matches6 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 Status14 ms001212
Scenario: Search By Full Client ID And Get One Match5 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches4 ms0088
Scenario: Search By One Letter Of Display Name5 ms0088
Scenario: Search By One Letter Of Serial Number4 ms001212
Scenario: Search By Serial Number And Get Multiple Matches8 ms001414
Scenario: Search By Serial Number And Get No Matches7 ms001010
Scenario: Search By Serial Number And Get One Match7 ms001111
Scenario: Search By Serial Number and Status7 ms001212
Scenario: Search By Serial Number, Display Name and Status7 ms001212
Scenario: Search By Specific Serial Number9 ms001010
Scenario: Search By Status And Get Multiple Matches6 ms001010
Scenario: Search by Device Status And Get One Match10 ms001010
Scenario: Search for a non existent client ID4 ms0066
Scenario: Send BIRTH message and then DC message35 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set40 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System41 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file59 ms0088
Scenario: Set a correct minimum for password length7 ms0033
Scenario: Set an incorrect minimum for password length8 ms0066
Scenario: Set environment variables0.11 sec0049-1249-12
Scenario: Setting configuration without mandatory items must raise an error3 ms0055
Scenario: Simple positive scenario for creating daily index17 ms001414
Scenario: Simple positive scenario for creating default - weekly index14 ms001212
Scenario: Simple positive scenario for creating hourly index23 ms001414
Scenario: Start broker for all scenarios0.3 sec0034-1034-10
Scenario: Start datastore for all scenarios0.6 sec003030
Scenario: Start event broker for all scenarios0.39 sec0040-1040-10
Scenario: Starting a job with Asset Write and Bundle Start steps28 ms003636
Scenario: Starting a job with Asset Write step19 ms002525
Scenario: Starting a job with Bundle Start step24 ms003434
Scenario: Starting a job with Bundle Stop and Bundle Start steps27 ms003939
Scenario: Starting a job with Bundle Stop step29 ms003535
Scenario: Starting a job with Command Execution and Bundle Start steps24 ms003737
Scenario: Starting a job with Command Execution step30 ms002525
Scenario: Starting a job with Configuration Put and Bundle Start steps25 ms003737
Scenario: Starting a job with Configuration Put step18 ms002525
Scenario: Starting a job with Package Install and Bundle Start steps26 ms003939
Scenario: Starting a job with Package Install step29 ms003232
Scenario: Starting a job with Package Uninstall and Bundle Start steps31 ms003636
Scenario: Starting a job with Package Uninstall step24 ms003333
Scenario: Starting a job with two Bundle Start steps21 ms003939
Scenario: Starting and stopping the simulator should create a device entry and properly set its status14 ms002020
Scenario: Starting job with Asset Write and Bundle Start steps and multiple devices27 ms003232
Scenario: Starting job with Asset Write step and multiple devices40 ms002828
Scenario: Starting job with Bundle Start step and multiple devices22 ms002828
Scenario: Starting job with Bundle Stop and Bundle Start step and multiple devices19 ms003232
Scenario: Starting job with Bundle Stop step and multiple devices30 ms002828
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices23 ms003232
Scenario: Starting job with Command Execution step and multiple devices24 ms002828
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices18 ms003232
Scenario: Starting job with Configuration Put step and multiple devices23 ms002828
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices26 ms003838
Scenario: Starting job with Package Download/Install step and multiple devices43 ms003434
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device24 ms003232
Scenario: Starting job with Package Uninstall step and multiple device23 ms002727
Scenario: Starting job with two Bundle Start steps and multiple devices28 ms003232
Scenario: Stealing link scenario21 ms002828
Scenario: Step definition factory sanity checks5 ms0022
Scenario: Step definition with a duplicate name7 ms0066
Scenario: Step definition with a null name6 ms0066
Scenario: Step definition with a null scope ID5 ms0066
Scenario: Step definition with an empty name5 ms0055
Scenario: Stop broker after all scenarios0.29 sec0036-1036-10
Scenario: Stop datastore after all scenarios0.24 sec003030
Scenario: Stop event broker for all scenarios0.32 sec0040-1040-10
Scenario: Test account query4 ms0044
Scenario: Test the message store with server timestamp indexing31 ms002626
Scenario: Test the message store with timestamp indexing25 ms002626
Scenario: The Client ID is case sensitive4 ms0088
Scenario: To be defined17 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"28 ms0044
Scenario: Translating CommandRequestMessage to null8 ms0044
Scenario: Translating empty message to empty message7 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"6 ms0044
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message4 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 message5 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 payload3 ms0055
Scenario: Translating kura data message with valid channel and without body and metrics into jms message5 ms0055
Scenario: Translating kura data message with valid channel, and with null payload3 ms0055
Scenario: Translating kura data message with valid channel, body and metrics into jms message3 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 message3 ms0055
Scenario: Translating null to KuraRequestMessage9 ms0044
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message3 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 message8 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 message8 ms0055
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message4 ms0055
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 message3 ms0055
Scenario: Translation of mqtt message with empty payload into kura data message3 ms0066
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message3 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 message5 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 message4 ms0066
Scenario: Try to add two different roles with same permissions13 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 ID4 ms0033
Scenario: Try to find a device with an invalid registry ID4 ms0033
Scenario: Try to find users granted to "admin" role12 ms001212
Scenario: Try to find users that have assigned specific role13 ms001212
Scenario: Try to modify the connection client ID3 ms0077
Scenario: Try to update the device client ID4 ms0044
Scenario: Update a non existing device4 ms0055
Scenario: Update a nonexistent step definition4 ms0077
Scenario: Update a step definition name6 ms0077
Scenario: Update a step definition processor name5 ms0088
Scenario: Update a step definition target type12 ms0088
Scenario: Update schedule which doesn't exist9 ms0055
Scenario: Update scheduler end date7 ms0099
Scenario: Update scheduler name8 ms0088
Scenario: Update scheduler start date6 ms0088
Scenario: Update trigger definition8 ms0088
Scenario: Update user10 ms0077
Scenario: Update user that doesn't exist5 ms0055
Scenario: User locking itself out by using out login attempts3 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock6 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock16 ms001717
Scenario: User login with wrong pass, but with enough time between login failures8 ms001919
Scenario: User not locking itself out by using less than max failed login attempts17 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 scope5 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 ID2 ms0044
Scenario: Validate a device search with a null device ID3 ms0066
Scenario: Validate a device search with a null scope ID1 ms0066
Scenario: Validate a null creator3 ms0055
Scenario: Validate a null device6 ms0055
Scenario: Validate a null device count2 ms0055
Scenario: Validate a null device query6 ms0055
Scenario: Validate a regular creator3 ms0044
Scenario: Validate a regular device client search4 ms0044
Scenario: Validate a regular device count5 ms0044
Scenario: Validate a regular device query4 ms0044
Scenario: Validate a regular device search4 ms0055
Scenario: Validate deleting a device with a null device ID8 ms0066
Scenario: Validate deleting a device with a null scope ID8 ms0066
empty) scope0 ms0044