Test Result : (root)

16 failures (-2) , 91 skipped (-31)
13,874 tests (-2653)
Took 16 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 description12 ms14
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"12 ms14
 Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device8 ms14
 Scenario: Executing Job And Then Restarting Device.Then I find 4 device events2 ms14
 Scenario: Executing Job When Device Connected After The Specified Start Date And Time.And I confirm the executed job is finished24 ms4
 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 Time26 ms14
 Scenario: Executing Job When Device Connected Before End Date And Time.And I confirm the executed job is finished5 ms4
 Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time6 ms14
 Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms8
 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account2 ms8
 Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account2 ms8
 Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints2 ms4
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22221 ms8
 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account3 ms8
 Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 22222 ms8
 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account3 ms8

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope5 ms0044
Scenario: A newly created account must have some metadata3 ms0033
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic9 ms0088
Scenario: Access info service sanity checks6 ms0044
Scenario: Access service comparison sanity checks8 ms0033
Scenario: Account based ClientInfo data check25 ms002424
Scenario: Account name must not be mutable4 ms0066
Scenario: Account wide metrics check31 ms002828
Scenario: Add Access Info domain permissions to new user19 ms002626
Scenario: Add Account permissions to the role in child account11 ms002828
Scenario: Add Credential domain permissions to new user18 ms001818
Scenario: Add Datastore domain permissions to new user0.19 sec001919
Scenario: Add Device Connection domain permissions to kapua-sys user10 ms001111
Scenario: Add Device Connection domain permissions to new user11 ms002323
Scenario: Add Device Event domain permissions to new user12 ms001616
Scenario: Add Device domain permissions to new user26 ms001717
Scenario: Add Domain domain permissions to kapua-sys user11 ms001717
Scenario: Add Domain domain permissions to new user10 ms003232
Scenario: Add Endpoint Permission To The User14 ms003030
Scenario: Add Endpoint_info permissions to the role in child account12 ms003030
Scenario: Add Group domain permissions to new user22 ms001717
Scenario: Add Group permissions to the role in child account15 ms002626
Scenario: Add Job domain permissions to new user13 ms001919
Scenario: Add Role domain permissions to new user18 ms001717
Scenario: Add Role permissions to the role in child account18 ms002626
Scenario: Add Scheduler Permissions With Job Permissions22 ms003131
Scenario: Add Scheduler Permissions Without Job Permissions11 ms002121
Scenario: Add Scheduler permissions to the role in child account15 ms003636
Scenario: Add Tag domain permissions to new user13 ms001515
Scenario: Add Tag permissions to the role in child account11 ms002626
Scenario: Add User domain permissions to new user17 ms002020
Scenario: Add account permissions to the role20 ms001919
Scenario: Add admin role to the user19 ms004444
Scenario: Add and delete Account permissions from the "admin" role10 ms001414
Scenario: Add and delete Device permissions from the "admin" role12 ms001414
Scenario: Add and delete Endpoint_info permissions from the "admin" role10 ms001414
Scenario: Add and delete Group permissions from the "admin" role8 ms001414
Scenario: Add and delete Job permissions from the "admin" role15 ms001414
Scenario: Add and delete Role permissions from the "admin" role12 ms001414
Scenario: Add and delete User permissions from the "admin" role11 ms001515
Scenario: Add datastore permissions to the role11 ms002727
Scenario: Add deleted role again15 ms001010
Scenario: Add device event permissions to the role10 ms003232
Scenario: Add device permissions to the role11 ms001919
Scenario: Add device permissions to the role in child account10 ms002626
Scenario: Add domain, user and access_info permissions to the role25 ms002323
Scenario: Add endpoint_info permissions to the role10 ms003131
Scenario: Add group permissions to the role14 ms001818
Scenario: Add job permissions to the role12 ms001919
Scenario: Add job permissions to the role in child account3 ms002626
Scenario: Add role permissions to the role10 ms001919
Scenario: Add same permission twice to the same role15 ms001414
Scenario: Add same role to user twice13 ms001313
Scenario: Add scheduler permissions to the role10 ms003131
Scenario: Add tag permissions to the role10 ms001818
Scenario: Add user permissions to the role14 ms001919
Scenario: Add user permissions to the role in child account16 ms002626
Scenario: Adding "Cron Job" Schedule With All Valid Parameters6 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 Format6 ms001111
Scenario: Adding "Cron Job" Schedule With End Date Only5 ms001010
Scenario: Adding "Cron Job" Schedule With End Time before Start time6 ms001212
Scenario: Adding "Cron Job" Schedule With Non-Unique End Date Parameter7 ms001616
Scenario: Adding "Cron Job" Schedule With Non-Unique Start Date Parameter9 ms001515
Scenario: Adding "Cron Job" Schedule With Start Date Only5 ms001111
Scenario: Adding "Cron Job" Schedule With the same Start and End time10 ms001212
Scenario: Adding "Cron Job" Schedule Without The Start Date Parameter7 ms001010
Scenario: Adding "Device Connect" Schedule With All Valid Parameters5 ms0088
Scenario: Adding "Device Connect" Schedule With End Date Only7 ms001010
Scenario: Adding "Device Connect" Schedule With End Time before Start time4 ms001111
Scenario: Adding "Device Connect" Schedule With Max Length Name7 ms0088
Scenario: Adding "Device Connect" Schedule With Min Length Name6 ms0088
Scenario: Adding "Device Connect" Schedule With Name Only9 ms0099
Scenario: Adding "Device Connect" Schedule With Non-Unique End Date Parameter10 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Name5 ms001313
Scenario: Adding "Device Connect" Schedule With Non-Unique Start Date Parameter9 ms001111
Scenario: Adding "Device Connect" Schedule With Start Date Only15 ms001010
Scenario: Adding "Device Connect" Schedule With the same Start and End time6 ms001111
Scenario: Adding "Device Connect" Schedule Without Name6 ms001010
Scenario: Adding "Device Connect" Schedule Without The Start Date Parameter7 ms0099
Scenario: Adding "Empty" Tag To Device7 ms0055
Scenario: Adding "Interval Job" Schedule With All Valid Parameters6 ms001010
Scenario: Adding "Interval Job" Schedule With End Date Only11 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 Name13 ms001010
Scenario: Adding "Interval Job" Schedule With Name Only8 ms001010
Scenario: Adding "Interval Job" Schedule With Non-Unique End Date Parameter5 ms001616
Scenario: Adding "Interval Job" Schedule With Non-Unique Name6 ms001515
Scenario: Adding "Interval Job" Schedule With Non-Unique Start Date Parameter6 ms001515
Scenario: Adding "Interval Job" Schedule With Null Interval Number4 ms001212
Scenario: Adding "Interval Job" Schedule With Start Date Only4 ms001111
Scenario: Adding "Interval Job" Schedule With the same Start and End time5 ms001212
Scenario: Adding "Interval Job" Schedule Without Interval Number5 ms001111
Scenario: Adding "Interval Job" Schedule Without The Start Date Parameter12 ms0099
Scenario: Adding "Interval Job" Schedule Without a Name8 ms001111
Scenario: Adding "admin" role to a user in a child account13 ms001414
Scenario: Adding "admin" role to multiple users11 ms001818
Scenario: Adding "admin" role twice10 ms001313
Scenario: Adding Account:Delete permission to user in same scope8 ms002525
Scenario: Adding Account:Delete permission to user in sub-account scope9 ms003030
Scenario: Adding Account:Read and Account:Delete permissions to user in same scope10 ms002121
Scenario: Adding Account:Read and Account:Write permissions to user in same scope13 ms001919
Scenario: Adding Account:Read permission to user in same scope16 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 scope12 ms002323
Scenario: Adding Account:Write permission to user in same scope10 ms002525
Scenario: Adding Account:Write permission to user in sub-account scope11 ms003131
Scenario: Adding Multiple Permissions To User11 ms002020
Scenario: Adding One Permission To User16 ms001111
Scenario: Adding Permissions To Child User19 ms001818
Scenario: Adding Permissions To Parallel User24 ms001818
Scenario: Adding Previously Deleted Permission13 ms002828
Scenario: Adding Previously Deleted Tag From Device Again5 ms001111
Scenario: Adding Regular Device to a Group With Description7 ms001010
Scenario: Adding Regular Device to a Group Without a Description11 ms001212
Scenario: Adding Regular Group Without Description to Device5 ms001010
Scenario: Adding Regular Tag Without Description To Device5 ms0066
Scenario: Adding Same Regular Group Without Description to Device6 ms001414
Scenario: Adding Tag With Long Name Without Description To Device5 ms0066
Scenario: Adding Tag With Numbers Without Description To Device3 ms0066
Scenario: Adding Tag With Short Name Without Description To Device6 ms0066
Scenario: Adding Tag With Special Symbols Without Description To Device5 ms0066
Scenario: Adding all Account permissions to user in same scope9 ms001717
Scenario: Adding all Account permissions to user in sub-account scope13 ms002424
Scenario: Adding existing roles to user14 ms001515
Scenario: Adding role from child account to user in new child account15 ms001515
Scenario: Adding role to multiple users in child account9 ms001818
Scenario: Adding same role twice to user in child account9 ms001515
Scenario: Adding the same role to user twice in child account10 ms001313
Scenario: All device parameters must match the device creator5 ms0033
Scenario: Assign 100 Devices to One Group16 ms001111
Scenario: B1 Broker publish to CTRL_ACC_REPLY17 ms0099
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed25 ms0099
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed10 ms0088
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI19 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed17 ms0099
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed9 ms0088
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY15 ms0099
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY12 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account7 ms0099
Scenario: B5 Broker publish to CTRL_ACC is not allowed14 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed15 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed8 ms0088
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI10 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed14 ms0099
Scenario: Basic Device Event queries5 ms001010
Scenario: Birth and applications event handling5 ms001212
Scenario: Birth and death message handling5 ms001212
Scenario: Birth and missing event handling6 ms001212
Scenario: Birth message handling from a new device12 ms001313
Scenario: Birth message handling from an existing device6 ms001212
Scenario: Captured date based ClientInfo data check30 ms003030
Scenario: Case sensitiveness of named device searches4 ms0044
Scenario: Change role name so it is too short3 ms0066
Scenario: Change the account parent path4 ms0055
Scenario: Changing Client ID6 ms0099
Scenario: Changing Description On Group With Long Description8 ms0077
Scenario: Changing Description On Group With Long Name22 ms0077
Scenario: Changing Description On Group With Numbers In Name6 ms001010
Scenario: Changing Description On Group With Permitted Symbols5 ms0077
Scenario: Changing Description On Group With Short Description4 ms0077
Scenario: Changing Description On Group With Short Name6 ms0077
Scenario: Changing Description On Tag With Long Description4 ms0044
Scenario: Changing Description On Tag With Long Name5 ms0055
Scenario: Changing Description On Tag With Numbers In Name3 ms0066
Scenario: Changing Description On Tag With Permitted Symbols In Name4 ms0044
Scenario: Changing Description On Tag With Short Description3 ms0044
Scenario: Changing Description On Tag With Short Name4 ms0044
Scenario: Changing Device Status To Disabled4 ms0099
Scenario: Changing Device Status To Enabled6 ms0099
Scenario: Changing Group's Description To Non-Uniqe One5 ms0077
Scenario: Changing Group's Description To Uniqe One5 ms0077
Scenario: Changing Group's Name To Contain Invalid Symbols In Name Without Changing Description6 ms0088
Scenario: Changing Group's Name To Contain Permitted Symbols In Name Without Changing Description5 ms0077
Scenario: Changing Group's Name To Non-Unique One7 ms0099
Scenario: Changing Group's Name To Short One Without Changing Description5 ms0077
Scenario: Changing Group's Name To Unique One4 ms0077
Scenario: Changing Group's Name To a Long One Without Changing Description7 ms0077
Scenario: Changing Group's Name To a Too Long One Without Changing Description6 ms0088
Scenario: Changing Group's Name To a Too Short One Without Changing Description6 ms0088
Scenario: Changing Tag's Description To Non-Unique One4 ms0055
Scenario: Changing Tag's Description To Unique One4 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 Description7 ms0055
Scenario: Changing Tag's Name To Non-Unique One10 ms0066
Scenario: Changing Tag's Name To Short One Without Description4 ms0077
Scenario: Changing Tag's Name To Unique One7 ms0077
Scenario: Changing Tag's Name To a Long One Without Description5 ms0077
Scenario: Changing Tag's Name To a Too Long One Without Description7 ms0055
Scenario: Changing Tag's Name To a Too Short One Without Description3 ms0055
Scenario: Changing description of a nonexisting role6 ms0077
Scenario: Changing job description to non-unique one7 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 description6 ms0077
Scenario: Changing job name to a too long one without description2 ms0055
Scenario: Changing job name to a too short one without description9 ms0066
Scenario: Changing job name to contain invalid symbols in name without description5 ms0044
Scenario: Changing job name to contain permitted symbols in name without description7 ms0055
Scenario: Changing job name to non-unique one10 ms0088
Scenario: Changing job name to short one without description8 ms0077
Scenario: Changing job name to unique one7 ms0099
Scenario: Changing name of a nonexisting role5 ms0077
Scenario: Changing role description to a valid one10 ms0066
Scenario: Changing role name so it is too long4 ms0066
Scenario: Changing role name to contain special character4 ms0044
Scenario: Changing role name to null6 ms0066
Scenario: Changing role's name to a valid one4 ms0066
Scenario: Channel info queries based on datastore channel filters27 ms005050
Scenario: ChannelInfo client ID and topic data based on the client id29 ms002828
Scenario: ChannelInfo client ID based on the account id24 ms002626
Scenario: ChannelInfo last published date32 ms003030
Scenario: ChannelInfo topic data based on the account id38 ms002626
Scenario: Check account properties4 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency26 ms003030
Scenario: Check the mapping for message semantic topics30 ms003030
Scenario: Check the message store30 ms002020
Scenario: Check the sanity of the Device Connection Domain data initialization8 ms0022
Scenario: Client Id based ClientInfo data check25 ms002828
Scenario: Compare domain entries5 ms0033
Scenario: Connect to the system and publish some data82 ms002222
Scenario: Connection Service factory sanity checks2 ms0022
Scenario: Count access info entities in a specific scope9 ms002424
Scenario: Count access role entities by scope7 ms003939
Scenario: Count connections in empty scope3 ms0044
Scenario: Count connections in scope3 ms0055
Scenario: Count devices with a specific BIOS version4 ms0066
Scenario: Count domains in a blank database9 ms0044
Scenario: Count domains in the database6 ms0077
Scenario: Count events in empty scope7 ms0066
Scenario: Count groups6 ms001414
Scenario: Count groups in a blank database12 ms0055
Scenario: Count role permissions in specific scopes10 ms001818
Scenario: Count roles in specific scopes6 ms001515
Scenario: Count step definition items5 ms0044
Scenario: Count step definitions in wrong (empty) scope6 ms0011
Scenario: Count user6 ms0066
Scenario: Counting created roles items in the DB8 ms0055
Scenario: Create a regular event24 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 entry31 ms0066
Scenario: Create an event with a null scope ID10 ms0077
Scenario: Create index with specific prefix12 ms001212
Scenario: Create multiple users5 ms0055
Scenario: Create regular access permissions8 ms002020
Scenario: Create same user in different accounts17 ms001515
Scenario: Create scheduler with correct end date7 ms0088
Scenario: Create scheduler with empty schedule name12 ms0088
Scenario: Create scheduler with end date before start date7 ms0099
Scenario: Create scheduler with invalid Retry Interval property11 ms0099
Scenario: Create scheduler with invalid cron job trigger property6 ms0099
Scenario: Create scheduler with invalid schedule name14 ms0088
Scenario: Create scheduler with short schedule name26 ms0088
Scenario: Create scheduler with too long schedule name10 ms0088
Scenario: Create scheduler with valid Retry Interval property7 ms0077
Scenario: Create scheduler with valid cron job trigger property9 ms0077
Scenario: Create scheduler with valid schedule name26 ms0066
Scenario: Create scheduler without Cron Job Trigger property7 ms0099
Scenario: Create scheduler without Retry Interval property6 ms0099
Scenario: Create scheduler without start date17 ms0077
Scenario: Create some regular role permissions5 ms0099
Scenario: Create user that already exist7 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 name6 ms0055
Scenario: Create with permissions7 ms001414
Scenario: Create with permissions and a role6 ms001717
Scenario: Create with permissions and a role in the wrong scope8 ms001515
Scenario: Creating A Device With Disabled Status5 ms0077
Scenario: Creating A Device With Enabled Status28 ms0077
Scenario: Creating A Device With Long Display Name6 ms0077
Scenario: Creating A Device With Long Name5 ms0077
Scenario: Creating A Device With Name Containing Invalid Symbols9 ms0088
Scenario: Creating A Device With Name Containing Permitted Symbols7 ms0077
Scenario: Creating A Device With No Name5 ms0088
Scenario: Creating A Device With Non-unique Display Name6 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 Name7 ms0077
Scenario: Creating A Device With Too Long Display Name6 ms0088
Scenario: Creating A Device With Too Long Name7 ms0088
Scenario: Creating A Device With Unique Name6 ms0099
Scenario: Creating Endpoint Non-Unique "Domain Name"5 ms0088
Scenario: Creating Endpoint Non-Unique "Port"8 ms0088
Scenario: Creating Endpoint Non-Unique "Schema"4 ms0099
Scenario: Creating Endpoint With "Domain Name" Only5 ms0066
Scenario: Creating Endpoint With "Port" Only5 ms0066
Scenario: Creating Endpoint With "Schema" Only3 ms0066
Scenario: Creating Endpoint With Disabled Secure Field7 ms0066
Scenario: Creating Endpoint With Enabled Secure Field11 ms0066
Scenario: Creating Endpoint With Invalid "Domain Name"5 ms0066
Scenario: Creating Endpoint With Invalid "Schema" containing symbols5 ms0066
Scenario: Creating Endpoint With Long "Domain Name"4 ms0055
Scenario: Creating Endpoint With Max Length "Port"4 ms0055
Scenario: Creating Endpoint With NULL parameters6 ms0066
Scenario: Creating Endpoint With Schema Containing "http://"4 ms0066
Scenario: Creating Endpoint With Schema Containing "https://"3 ms0066
Scenario: Creating Endpoint With Short "Domain Name"5 ms0066
Scenario: Creating Endpoint With Short "Schema"5 ms0066
Scenario: Creating Endpoint With Small Number "Port"11 ms0066
Scenario: Creating Endpoint With Too Big "Port"5 ms0066
Scenario: Creating Endpoint With Too Long "Domain Name"5 ms0066
Scenario: Creating Endpoint With Too Long "Schema"8 ms0066
Scenario: Creating Endpoint Without "Domain Name"7 ms0066
Scenario: Creating Endpoint Without "Port"5 ms0066
Scenario: Creating Endpoint Without "Schema"9 ms0066
Scenario: Creating Endpoint Without Long "Schema"3 ms0055
Scenario: Creating Endpoint with invalid "Schema" which contains only numbers5 ms0066
Scenario: Creating Group Invalid Symbols In Name Without Description3 ms0077
Scenario: Creating Group With Invalid Symbols In Name With Valid Description8 ms0077
Scenario: Creating Group With Long Name With Valid Description6 ms0066
Scenario: Creating Group With Long Name Without Description3 ms0066
Scenario: Creating Group With Numbers In Name With Valid Description8 ms0088
Scenario: Creating Group With Permitted Symbols And Numbers In Name Without Description7 ms0066
Scenario: Creating Group With Permitted Symbols In Name With Valid Description6 ms0066
Scenario: Creating Group With Short Name With Valid Description6 ms0066
Scenario: Creating Group With Short Name Without Description5 ms0066
Scenario: Creating Group With Too Long Name With Valid Description6 ms0077
Scenario: Creating Group With Too Long Name Without Description8 ms0077
Scenario: Creating Group With Too Short Name With Valid Description6 ms0077
Scenario: Creating Group With Too Short Name Without Description6 ms0077
Scenario: Creating Group Without a Name And With Valid Description8 ms0077
Scenario: Creating Group Without a Name And Without Description5 ms0077
Scenario: Creating Non-Unique Group With Valid Description6 ms0088
Scenario: Creating Non-Unique Tag With Valid Description6 ms0055
Scenario: Creating Non-unique Group Without Description6 ms0088
Scenario: Creating Non-unique Tag Without Description11 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 Description7 ms0044
Scenario: Creating Tag With Long Name Without Description7 ms0044
Scenario: Creating Tag With Numbers In Name With Valid Description4 ms0044
Scenario: Creating Tag With Numbers In Name Without Description7 ms0044
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description4 ms0044
Scenario: Creating Tag With Permitted Symbols In Name Without Description7 ms0044
Scenario: Creating Tag With Short Name With Valid Description4 ms0044
Scenario: Creating Tag With Short Name Without Description13 ms0044
Scenario: Creating Tag With Too Long Name With Valid Description3 ms0044
Scenario: Creating Tag With Too Long Name Without Description9 ms0044
Scenario: Creating Tag With Too Short Name With Valid Description4 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 Group With Long Description6 ms0066
Scenario: Creating Unique Group With Non-unique Description4 ms0077
Scenario: Creating Unique Group With Short Description5 ms0066
Scenario: Creating Unique Group With Unique Description6 ms0066
Scenario: Creating Unique Group Without Description4 ms0066
Scenario: Creating Unique Tag With Long Description4 ms0044
Scenario: Creating Unique Tag With Non-unique Description5 ms0055
Scenario: Creating Unique Tag With Short Description4 ms0044
Scenario: Creating Unique Tag With Unique Description4 ms0044
Scenario: Creating Unique Tag Without Description24 ms0044
Scenario: Creating Valid Endpoint10 ms0066
Scenario: Creating a Access Group with invalid special symbols in name0 ms0044
Scenario: Creating a Device With Permitted Symbols in its Display Name7 ms0077
Scenario: Creating a Device With Unique Display Name7 ms0088
Scenario: Creating a job with name only21 ms0066
Scenario: Creating a job with null name17 ms0055
Scenario: Creating a job without name with valid description2 ms0055
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement11 ms0044
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement31 ms0033
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement6 ms0055
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement7 ms0044
Scenario: Creating a role name with allowed symbols in its name7 ms0055
Scenario: Creating a role with 255 characters long description3 ms0055
Scenario: Creating a role with a name and description that contain digits only5 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 enough3 ms0055
Scenario: Creating a role with special characters in the description4 ms0044
Scenario: Creating a role with the name that contains digits7 ms0055
Scenario: Creating a role with too long name1 ms0055
Scenario: Creating a role with too short name3 ms0055
Scenario: Creating a role with valid name and with too long description5 ms0033
Scenario: Creating a role wtih 255 characters long name4 ms0055
Scenario: Creating a single device with case sensitive clientID6 ms0055
Scenario: Creating a single device with clientID that contains 255 characters8 ms0055
Scenario: Creating a single device with clientID that contains 256 characters6 ms0044
Scenario: Creating a single device with clientID that contains invalid character3 ms0044
Scenario: Creating a single device with clientID that contains invalid characters4 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 name5 ms0055
Scenario: Creating a valid Access Group with only numbers in name4 ms0055
Scenario: Creating a valid Access Group with unique name5 ms0055
Scenario: Creating a valid Access Group with valid special symbols in name4 ms0055
Scenario: Creating a valid role3 ms0055
Scenario: Creating an Access Group with empty name6 ms0044
Scenario: Creating an Access Group with long name6 ms0055
Scenario: Creating an Access Group with short name4 ms0055
Scenario: Creating an Access Group with too long name4 ms0044
Scenario: Creating an Access Group with too short name7 ms0044
Scenario: Creating an Access Group without name and with description2 ms0044
Scenario: Creating and Deleting Endpoint Two Times10 ms002525
Scenario: Creating index with regular user13 ms002525
Scenario: Creating job with invalid symbols in name without description18 ms0044
Scenario: Creating job with long name and valid description5 ms0066
Scenario: Creating job with long name without description10 ms0066
Scenario: Creating job with numbers in name and valid description12 ms0066
Scenario: Creating job with numbers in name without description5 ms0066
Scenario: Creating job with permitted symbols in name without description10 ms0033
Scenario: Creating job with short name and valid job description16 ms0066
Scenario: Creating job with short name without description11 ms0066
Scenario: Creating job with too long name and valid description2 ms0055
Scenario: Creating job with too long name without description8 ms0055
Scenario: Creating job with too short name and valid description5 ms0055
Scenario: Creating job with too short name without description14 ms0055
Scenario: Creating job without name and without description9 ms0055
Scenario: Creating new device and tagging it with specific Tag8 ms001414
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag5 ms001616
Scenario: Creating non-unique Access Group6 ms0055
Scenario: Creating non-unique Access Group with unique description2 ms0055
Scenario: Creating non-unique job name with valid job description7 ms0077
Scenario: Creating two device with the same clientID5 ms0055
Scenario: Creating two indexes with daily index13 ms001717
Scenario: Creating two indexes with hourly index15 ms001717
Scenario: Creating two indexes with weekly index13 ms001717
Scenario: Creating two roles with the same description3 ms0066
Scenario: Creating two roles with the same name3 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 description3 ms0055
Scenario: Creating unique Access Group with only numbers in description3 ms0055
Scenario: Creating unique Access Group with short description3 ms0055
Scenario: Creating unique Access Group with special symbols in description24 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 description11 ms001010
Scenario: Creating unique job with short description5 ms0066
Scenario: Creating user22 ms0055
Scenario: Creation of access role with neither acess info and role entities12 ms001212
Scenario: Creation of access role without an acess info entity10 ms001212
Scenario: D1 Device publish to CTRL_ACC_REPLY10 ms0099
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI18 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed8 ms0099
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed11 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY17 ms0099
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY17 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account5 ms0099
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC19 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI19 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed14 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 allowed10 ms0088
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed31 ms0099
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI14 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed9 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_REPLY15 ms0099
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY15 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account9 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 allowed20 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed10 ms0088
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI14 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC12 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY13 ms0099
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed23 ms0099
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed13 ms001010
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed15 ms0099
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed21 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed8 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_REPLY16 ms0099
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY15 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account12 ms0099
Scenario: DV5 Data view publish to CTRL_ACC is not allowed9 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 allowed7 ms0088
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI10 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed14 ms0099
Scenario: Delete Kapua system user4 ms0055
Scenario: Delete a access info entity with permissions and roles11 ms001717
Scenario: Delete a connection from the database7 ms0088
Scenario: Delete a group from the database7 ms001010
Scenario: Delete a group from the database - Unknown group ID3 ms0066
Scenario: Delete a non existent event7 ms0077
Scenario: Delete a non existing connection3 ms0077
Scenario: Delete a non existing permission entity7 ms001616
Scenario: Delete a non existing role entry6 ms001111
Scenario: Delete a nonexistent domain6 ms0055
Scenario: Delete a step definition6 ms0088
Scenario: Delete a step definition twice5 ms0077
Scenario: Delete access role from user12 ms001212
Scenario: Delete an access info entity twice14 ms001111
Scenario: Delete an access info entity using the wrong scope ID11 ms001111
Scenario: Delete an existing access info entity7 ms001212
Scenario: Delete an existing access permission entity7 ms001515
Scenario: Delete an existing access role entry5 ms002222
Scenario: Delete an existing account4 ms0055
Scenario: Delete an existing device from the registry3 ms0044
Scenario: Delete an existing event5 ms0099
Scenario: Delete an existing role7 ms001010
Scenario: Delete an existing role twice12 ms001616
Scenario: Delete items based on query results41 ms008484
Scenario: Delete items by date ranges0.26 sec00132132
Scenario: Delete items by the datastore ID33 ms006666
Scenario: Delete nonexisting account4 ms0044
Scenario: Delete nonexisting role permission6 ms001313
Scenario: Delete permissions from role10 ms001818
Scenario: Delete role permissions7 ms001010
Scenario: Delete scheduler7 ms0088
Scenario: Delete scheduler which doesn't exist6 ms0055
Scenario: Delete the Kapua system account8 ms0055
Scenario: Delete the last created domain entry6 ms0088
Scenario: Delete user6 ms0066
Scenario: Delete user that doesn't exist4 ms0055
Scenario: Deleting "Cron Schedule" Triggering8 ms001313
Scenario: Deleting "Device Schedule" Triggering7 ms001111
Scenario: Deleting "Interval Schedule" Triggering7 ms001313
Scenario: Deleting Device With Disabled Status6 ms001010
Scenario: Deleting Device With Enabled Status12 ms001010
Scenario: Deleting Endpoint Domain Name And Leaving it Empty8 ms0088
Scenario: Deleting Endpoint Which Does Not Exist5 ms0066
Scenario: Deleting Existing Group5 ms0088
Scenario: Deleting Existing Group And Creating It Again With Same Name9 ms001212
Scenario: Deleting Existing Tag And Creating It Again With Same Name4 ms0077
Scenario: Deleting Group's Name And Leaving It Empty Without Changing Description4 ms0088
Scenario: Deleting Non-Existent Tag4 ms0077
Scenario: Deleting Tag From Device3 ms0088
Scenario: Deleting Tag's Name And Leaving It Empty Without Description7 ms0055
Scenario: Deleting Unexisitng Group11 ms001111
Scenario: Deleting a Permission21 ms002121
Scenario: Deleting a non-existing Access Group6 ms0066
Scenario: Deleting a role twice3 ms0077
Scenario: Deleting admin role29 ms0077
Scenario: Deleting an existing Access Group6 ms0055
Scenario: Deleting an existing Access Group and creating it again with the same name3 ms0077
Scenario: Deleting an existing role7 ms0066
Scenario: Deleting default permissions from admin role9 ms001212
Scenario: Deleting existing tag4 ms0099
Scenario: Deleting role after adding it to user10 ms001414
Scenario: Deleting role after it has been added to user in child account9 ms001616
Scenario: Deleting user in account that is higher in hierarchy15 ms002323
Scenario: Deleting user in account that is lower in hierarchy14 ms002424
Scenario: Device connection update3 ms0077
Scenario: Device factory sanity checks2 ms0022
Scenario: Device queries5 ms001010
Scenario: Device query - find by BIOS version2 ms0077
Scenario: Domain entry query4 ms0055
Scenario: Domain with null actions6 ms0055
Scenario: Domain with null name5 ms0055
Scenario: Domains with duplicate names5 ms0088
Scenario: Duplicate group name in root scope8 ms001010
Scenario: Duplicate role names5 ms0077
Scenario: Editing Access Group description to description with numbers6 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 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 one3 ms0055
Scenario: Editing Access Group name to empty name3 ms0055
Scenario: Editing Access Group name to name that contains numbers5 ms0077
Scenario: Editing Access Group name to name that contains only numbers4 ms0077
Scenario: Editing Access Group name to name with invalid special symbols in 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 one4 ms0077
Scenario: Editing Access Group name to too short one3 ms0055
Scenario: Editing Access Group name to valid one5 ms0077
Scenario: Editing Endpoint Domain Name So It Contains Invalid Symbols4 ms0088
Scenario: Editing Endpoint Domain Name So It Contains Only Numbers10 ms0088
Scenario: Editing Endpoint Domain Name So It Has Max Value5 ms0077
Scenario: Editing Endpoint Domain Name So It Has Min Value11 ms0077
Scenario: Editing Endpoint Domain Name To Non-unique Value6 ms0099
Scenario: Editing Endpoint Domain Name To Unique Value3 ms0077
Scenario: Editing Endpoint Port To Non-unique Value4 ms0099
Scenario: Editing Endpoint Port To Unique Value7 ms0077
Scenario: Editing Endpoint Schema And Leaving It Empty5 ms0088
Scenario: Editing Endpoint Schema So It Contains "http://"5 ms0088
Scenario: Editing Endpoint Schema So It Contains "https://"5 ms0088
Scenario: Editing Endpoint Schema So It Contains Invalid Symbols10 ms0088
Scenario: Editing Endpoint Schema So It Contains Only Numbers7 ms0088
Scenario: Editing Endpoint Schema So It Has Max Length6 ms0077
Scenario: Editing Endpoint Schema So It Has Min Length5 ms0077
Scenario: Editing Endpoint Schema To Non-unique Value9 ms0088
Scenario: Editing Endpoint Schema To Unique Value4 ms0077
Scenario: Editing Endpoint Secure Field To Non-unique Value6 ms0099
Scenario: Editing Endpoint Secure Field To Unique Value5 ms0077
Scenario: Editing Endpoint To NULL Values5 ms001414
Scenario: Editing Endpoint To Non-unique Endpoint8 ms001010
Scenario: Editing Group's Name To Contain Numbers Without Changing Description5 ms0077
Scenario: Editing Tag's Name To Contain Numbers Without Description10 ms0077
Scenario: Empty query results are supported5 ms0088
Scenario: Event factory sanity checks4 ms0022
Scenario: Event service domain check4 ms0022
Scenario: Every account must have the default configuration items5 ms0033
Scenario: Executing Job And Then Restarting Device10 ms2162745
Scenario: Executing Job When Device Connected After End Date And Time34 ms003838
Scenario: Executing Job When Device Connected After The Specified Start Date And Time50 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 Time28 ms003737
Scenario: Executing Job Without Steps53 ms004040
Scenario: Find a connection by its IDs8 ms0066
Scenario: Find a connection by its client ID4 ms0066
Scenario: Find a group entry in the database11 ms0099
Scenario: Find a non existing event9 ms0066
Scenario: Find account by Id5 ms0044
Scenario: Find account by Ids5 ms0044
Scenario: Find account by name12 ms0044
Scenario: Find account by random Id12 ms0033
Scenario: Find all child accounts10 ms0033
Scenario: Find an access info entity6 ms001111
Scenario: Find an access info entity by user ID5 ms001010
Scenario: Find an event by its ID12 ms0066
Scenario: Find an existing access role entity11 ms001313
Scenario: Find by name nonexisting account7 ms0033
Scenario: Find correct number of messages by corresponding metric0.21 sec005858
Scenario: Find device by client ID4 ms0033
Scenario: Find device by registry ID3 ms0044
Scenario: Find last created permission8 ms001212
Scenario: Find multiple users7 ms0055
Scenario: Find role by ID5 ms0077
Scenario: Find the last created domain entry6 ms0055
Scenario: Find user by id5 ms0055
Scenario: Find user by its email3 ms0066
Scenario: Find user by its phone number6 ms0066
Scenario: Find user by name4 ms0055
Scenario: Find user by name that doesn't exist4 ms0033
Scenario: Find user with id and scope id that doesn't exist5 ms0033
Scenario: Finding all messages by selecting all metrics0.15 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 past5 ms0066
Scenario: Finding user by expiration date in the present4 ms0066
Scenario: Generic connection query4 ms0088
Scenario: Get metadata4 ms0033
Scenario: Group with a null name13 ms0077
Scenario: Handle account creation22 ms0033
Scenario: Handle duplicate account names9 ms0055
Scenario: Handle null account name8 ms0044
Scenario: Handling of 2 birth messages7 ms001212
Scenario: Handling of a disconnect message from a non existing device7 ms001010
Scenario: Have Two Devices in The Same Group Without Description9 ms001313
Scenario: I try to find a non-existing connection7 ms0066
Scenario: If user credential expiration date is before today, user can not login5 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 login4 ms001414
Scenario: If user credential is in state enabled, user can login7 ms001313
Scenario: If user expiration date is before today, user can not login5 ms001313
Scenario: If user expiration date is today, user can not login because expiration date was reached6 ms001313
Scenario: If user expiration date is tomorrow, user can login4 ms001212
Scenario: Init Security Context for all scenarios87 ms0022-2622-26
Scenario: Installing a package17 ms001313
Scenario: Interval Job" Schedule With Too Long Name9 ms001111
Scenario: It must be possible to query for specific entries in the role database4 ms0088
Scenario: It should not be possible to change the configuration items4 ms0055
Scenario: List Endpoints Created From Sub-Account3 ms223126
Scenario: List Endpoints From "kapua-sys" Account4 ms24511
Scenario: List Endpoints From Sub-Account Of Another Sub-Account4 ms223126
Scenario: List Endpoints From Sub-account5 ms212115
Scenario: MetricsInfo client ID and topic data based on the client id35 ms003434
Scenario: MetricsInfo last published date34 ms004848
Scenario: Modify a role that was deleted7 ms0099
Scenario: Modify an existing account5 ms0044
Scenario: Modify nonexisting account5 ms0066
Scenario: Modifying Sub-account of a different parent account13 ms002525
Scenario: Moving Device From One Group With Description to Another10 ms001414
Scenario: Nameless role entry5 ms0077
Scenario: Negative scenario when client connects twice with same client id33 ms001111
Scenario: Permission factory sanity checks5 ms0033
Scenario: Positive scenario without stealing link31 ms001212
Scenario: Query based on message ordering41 ms002020
Scenario: Query based on metrics ordering21 ms002020
Scenario: Query before schema search36 ms008282
Scenario: Query for a specific group by name9 ms001616
Scenario: Query for all the access info entities of a specific user24 ms001818
Scenario: Query for all the access info entities of an invalid user9 ms001010
Scenario: Query for step definitions7 ms0077
Scenario: Query user5 ms0066
Scenario: Querying Other Items With All Account Permissions18 ms003939
Scenario: Regular connection7 ms0077
Scenario: Regular creation of Access Role entity11 ms001414
Scenario: Regular domain6 ms0055
Scenario: Regular group in random scope9 ms0077
Scenario: Regular group in root scope13 ms0077
Scenario: Regular role creation5 ms0099
Scenario: Regular step definition creation6 ms0077
Scenario: Regular step definition with a property list5 ms0044
Scenario: Reset Security Context for all scenarios97 ms0022-2622-26
Scenario: Restarting a job with Asset Write and Bundle Start steps19 ms002828
Scenario: Restarting a job with Command Execution and Bundle Start steps21 ms002828
Scenario: Restarting a job with Configuration Put and Bundle Start steps26 ms002828
Scenario: Restarting a job with Package Uninstall and Bundle Start steps24 ms002828
Scenario: Restarting a job with invalid Configuration Put and multiple devices two times27 ms003333
Scenario: Restarting a job with invalid Configuration Put step two times27 ms003636
Scenario: Restarting a job with invalid Package Install step and multiple devices two times46 ms003131
Scenario: Restarting a job with invalid Package Install step two times27 ms003434
Scenario: Restarting a job with invalid Package Uninstall step and multiple devices two times20 ms003232
Scenario: Restarting a job with invalid Package Uninstall step two times22 ms003434
Scenario: Restarting a job with valid Configuration Put step and multiple devices two times47 ms003333
Scenario: Restarting a job with valid Configuration Put step two times44 ms003636
Scenario: Restarting a job with valid Package Install step and multiple devices two times34 ms002929
Scenario: Restarting a job with valid Package Install step two times23 ms003434
Scenario: Restarting a job with valid Package Uninstall step and multiple devices two times25 ms003030
Scenario: Restarting a job with valid Package Uninstall step two times24 ms003232
Scenario: Restarting job With invalid Asset Write and multiple two times24 ms003434
Scenario: Restarting job With valid Asset Write step two times30 ms003636
Scenario: Restarting job with Asset Write and Bundle Start steps and multiple devices24 ms003131
Scenario: Restarting job with Asset Write step22 ms002525
Scenario: Restarting job with Asset Write step and multiple devices19 ms002828
Scenario: Restarting job with Bundle Start step21 ms002525
Scenario: Restarting job with Bundle Start step and multiple devices31 ms002727
Scenario: Restarting job with Bundle Stop and Bundle Start step and multiple devices23 ms003131
Scenario: Restarting job with Bundle Stop and Bundle Start steps18 ms002929
Scenario: Restarting job with Bundle Stop step18 ms002525
Scenario: Restarting job with Bundle Stop step and multiple devices22 ms002727
Scenario: Restarting job with Command Execution and Bundle Start steps and multiple devices23 ms003131
Scenario: Restarting job with Command Execution step21 ms002525
Scenario: Restarting job with Command Execution step and multiple devices19 ms002727
Scenario: Restarting job with Configuration Put and Bundle Start steps and multiple devices22 ms003131
Scenario: Restarting job with Configuration Put step29 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 devices50 ms005959
Scenario: Restarting job with Package Download/Install step and multiple devices23 ms002727
Scenario: Restarting job with Package Install step19 ms002525
Scenario: Restarting job with Package Uninstall and Bundle start steps and multiple device20 ms003131
Scenario: Restarting job with Package Uninstall step21 ms002525
Scenario: Restarting job with Package Uninstall step and multiple device20 ms002727
Scenario: Restarting job with invalid Asset Write step two times23 ms003636
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps and multiple devices two times29 ms004141
Scenario: Restarting job with invalid Bundle Start and Bundle Stop steps two times25 ms004343
Scenario: Restarting job with invalid Bundle Start step and multiple devices two times24 ms003535
Scenario: Restarting job with invalid Bundle Start step two times51 ms003737
Scenario: Restarting job with invalid Bundle Stop step and multiple devices two times29 ms003535
Scenario: Restarting job with invalid Bundle Stop step two times22 ms003737
Scenario: Restarting job with invalid Command Execution and Package Install step two times35 ms003636
Scenario: Restarting job with invalid Command Execution and Package Install steps and multiple devices two times40 ms003737
Scenario: Restarting job with invalid Command Execution step and multiple devices two times48 ms003131
Scenario: Restarting job with invalid Command Execution step two times40 ms003232
Scenario: Restarting job with invalid Configuration Put And Command Execution steps two times26 ms003838
Scenario: Restarting job with invalid Configuration Put and Command Execution steps and multiple devices two times34 ms003737
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps and multiple devices two times50 ms003838
Scenario: Restarting job with invalid Package Uninstall and Asset Write steps two times31 ms004040
Scenario: Restarting job with two Bundle Start steps21 ms002929
Scenario: Restarting job with two Bundle Start steps and multiple devices12 ms003131
Scenario: Restarting job with valid Asset Write step and multiple devices two times27 ms003434
Scenario: Restarting job with valid Bundle Start And Bundle Stop steps two times20 ms004343
Scenario: Restarting job with valid Bundle Start and Bundle Stop steps and multiple devices two times52 ms004141
Scenario: Restarting job with valid Bundle Start step and multiple devices two times32 ms003535
Scenario: Restarting job with valid Bundle Start step two times42 ms003737
Scenario: Restarting job with valid Bundle Stop step and multiple devices two times36 ms003535
Scenario: Restarting job with valid Bundle Stop step two times20 ms003737
Scenario: Restarting job with valid Command Execution and Package Install steps and multiple devices two times33 ms003333
Scenario: Restarting job with valid Command Execution and Package Install steps two times28 ms003434
Scenario: Restarting job with valid Command Execution step and multiple devices two times66 ms003131
Scenario: Restarting job with valid Command Execution step two times47 ms003232
Scenario: Restarting job with valid Configuration Put and Command Execution steps and multiple devices two times27 ms003737
Scenario: Restarting job with valid Configuration Put and Command Execution steps two times33 ms003838
Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times25 ms003636
Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times26 ms003838
Scenario: Role creator sanity checks5 ms0022
Scenario: Role entry with no actions6 ms0066
Scenario: Role object equality check6 ms0022
Scenario: Role service related objects sanity checks6 ms0044
Scenario: Search By Client ID And Get Multiple Matches35 ms003737
Scenario: Search By Client ID And Get No Matches5 ms001010
Scenario: Search By Client ID And Get One Match12 ms0088
Scenario: Search By Client ID and Display Name10 ms001212
Scenario: Search By Client ID and Serial Number11 ms001212
Scenario: Search By Client ID and Status11 ms001212
Scenario: Search By Client ID, Display Name and Serial Number5 ms001212
Scenario: Search By Client ID, Display Name and Status8 ms001212
Scenario: Search By Client ID, Display Name, Serial Number and Status5 ms001212
Scenario: Search By Device Status And Get No Matches10 ms0088
Scenario: Search By Device's Display Name And Get One Match13 ms0088
Scenario: Search By Display Name and Serial Number5 ms001212
Scenario: Search By Display Name and Status12 ms001212
Scenario: Search By Full Client ID And Get One Match11 ms001010
Scenario: Search By Non-existing Client ID And Get No Matches11 ms0088
Scenario: Search By One Letter Of Display Name10 ms0088
Scenario: Search By One Letter Of Serial Number4 ms001212
Scenario: Search By Serial Number And Get Multiple Matches12 ms001414
Scenario: Search By Serial Number And Get No Matches7 ms001010
Scenario: Search By Serial Number And Get One Match10 ms001111
Scenario: Search By Serial Number and Status14 ms001212
Scenario: Search By Serial Number, Display Name and Status4 ms001212
Scenario: Search By Specific Serial Number8 ms001010
Scenario: Search By Status And Get Multiple Matches7 ms001010
Scenario: Search by Device Status And Get One Match5 ms001010
Scenario: Search for a non existent client ID3 ms0066
Scenario: Search for an access info entity by an incorrect user ID4 ms001111
Scenario: Search the role database for a random ID7 ms0077
Scenario: Send BIRTH message and then DC message26 ms001515
Scenario: Send BIRTH message and then DC message while broker ip is NOT set34 ms0066
Scenario: Send BIRTH message and then DC message while broker ip is set by System44 ms0088
Scenario: Send BIRTH message and then DC message while broker ip is set by config file47 ms0088
Scenario: Set a correct minimum for password length7 ms0033
Scenario: Set an incorrect minimum for password length5 ms0066
Scenario: Set environment variables0.12 sec006161
Scenario: Setting configuration without mandatory items must raise an error4 ms0055
Scenario: Simple create6 ms001111
Scenario: Simple positive scenario for creating daily index14 ms001414
Scenario: Simple positive scenario for creating default - weekly index14 ms001212
Scenario: Simple positive scenario for creating hourly index17 ms001414
Scenario: Start broker for all scenarios0.33 sec0042-242-2
Scenario: Start datastore for all scenarios0.71 sec003030
Scenario: Start event broker for all scenarios0.38 sec0048-248-2
Scenario: Starting a job with Asset Write and Bundle Start steps20 ms003636
Scenario: Starting a job with Asset Write step53 ms002525
Scenario: Starting a job with Bundle Start step20 ms003434
Scenario: Starting a job with Bundle Stop and Bundle Start steps22 ms003939
Scenario: Starting a job with Bundle Stop step24 ms003535
Scenario: Starting a job with Command Execution and Bundle Start steps20 ms003737
Scenario: Starting a job with Command Execution step20 ms002525
Scenario: Starting a job with Configuration Put and Bundle Start steps21 ms003737
Scenario: Starting a job with Configuration Put step21 ms002525
Scenario: Starting a job with Package Install and Bundle Start steps23 ms003939
Scenario: Starting a job with Package Install step15 ms003232
Scenario: Starting a job with Package Uninstall and Bundle Start steps17 ms003636
Scenario: Starting a job with Package Uninstall step22 ms003333
Scenario: Starting a job with invalid Asset Write step39 ms003131
Scenario: Starting a job with invalid Asset Write step and multiple targets34 ms002929
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps35 ms003636
Scenario: Starting a job with invalid Bundle Start and Bundle Stop steps and multiple devices44 ms003535
Scenario: Starting a job with invalid Bundle Start step31 ms003131
Scenario: Starting a job with invalid Bundle Stop step38 ms003131
Scenario: Starting a job with invalid Bundle Stop step and multiple devices35 ms002929
Scenario: Starting a job with invalid Command Execution step40 ms002727
Scenario: Starting a job with invalid Configuration Put step19 ms003030
Scenario: Starting a job with invalid Configuration Put step and multiple devices77 ms002828
Scenario: Starting a job with invalid Package Install step36 ms002929
Scenario: Starting a job with invalid Package Install step and multiple devices54 ms002626
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps23 ms003434
Scenario: Starting a job with invalid Package Uninstall and Asset Write steps and multiple devices38 ms003232
Scenario: Starting a job with invalid Package Uninstall step29 ms002929
Scenario: Starting a job with invalid Package Uninstall step and multiple targets55 ms002626
Scenario: Starting a job with two Bundle Start steps21 ms003939
Scenario: Starting a job with valid Asset Write step27 ms003131
Scenario: Starting a job with valid Asset Write step and multiple targets27 ms002929
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps27 ms003636
Scenario: Starting a job with valid Bundle Start and Bundle Stop steps and multiple devices47 ms003434
Scenario: Starting a job with valid Bundle Start step43 ms003131
Scenario: Starting a job with valid Bundle Stop step28 ms003131
Scenario: Starting a job with valid Bundle Stop step and multiple devices48 ms002929
Scenario: Starting a job with valid Command Execution step73 ms002727
Scenario: Starting a job with valid Configuration Put step27 ms003131
Scenario: Starting a job with valid Configuration Put step and multiple devices37 ms002626
Scenario: Starting a job with valid Package Install step24 ms002929
Scenario: Starting a job with valid Package Install step and multiple devices30 ms002626
Scenario: Starting a job with valid Package Uninstall and Asset Write steps29 ms003333
Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices35 ms003232
Scenario: Starting a job with valid Package Uninstall step21 ms003030
Scenario: Starting a job with valid Package Uninstall step and multiple targets52 ms002626
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 devices21 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 devices26 ms003232
Scenario: Starting job with Bundle Stop step and multiple devices20 ms002828
Scenario: Starting job with Command Execution and Bundle Start steps and multiple devices30 ms003232
Scenario: Starting job with Command Execution step and multiple devices21 ms002828
Scenario: Starting job with Configuration Put and Bundle Start steps and multiple devices21 ms003232
Scenario: Starting job with Configuration Put step and multiple devices24 ms002828
Scenario: Starting job with Package Download/Install and Bundle Start steps and multiple devices20 ms003838
Scenario: Starting job with Package Download/Install step and multiple devices33 ms003434
Scenario: Starting job with Package Uninstall and Bundle start steps and multiple device19 ms003232
Scenario: Starting job with Package Uninstall step and multiple device29 ms002727
Scenario: Starting job with invalid Bundle Start step and multiple devices37 ms002929
Scenario: Starting job with invalid Command Execution and Package Install steps21 ms003131
Scenario: Starting job with invalid Command Execution step and multiple devices52 ms002828
Scenario: Starting job with invalid Command Execution, invalid Package Install steps and multiple devices36 ms002929
Scenario: Starting job with invalid Configuration Put and Command Execution steps23 ms003232
Scenario: Starting job with invalid Configuration Put and Command Execution steps and multiple devices52 ms003131
Scenario: Starting job with two Bundle Start steps and multiple devices19 ms003232
Scenario: Starting job with valid Bundle Start step and multiple devices40 ms002929
Scenario: Starting job with valid Command Execution and Package Install steps25 ms003131
Scenario: Starting job with valid Command Execution step and multiple devices41 ms002626
Scenario: Starting job with valid Command Execution, valid Package Install steps and multiple devices24 ms002929
Scenario: Starting job with valid Configuration Put and Command Execution steps40 ms003232
Scenario: Starting job with valid Configuration Put and Command Execution steps and multiple devices67 ms003030
Scenario: Stealing link scenario15 ms002828
Scenario: Step definition factory sanity checks5 ms0022
Scenario: Step definition with a duplicate name6 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.3 sec0044-244-2
Scenario: Stop datastore after all scenarios0.22 sec003030
Scenario: Stop event broker for all scenarios0.38 sec0048-248-2
Scenario: Stop job with multiple Asset Write and Package Install steps and one target20 ms003737
Scenario: Stop job with multiple Bundle Start and Package Install steps and one target44 ms003737
Scenario: Stop job with multiple Bundle Stop and Package Uninstall steps and one target60 ms003737
Scenario: Stop job with multiple Command Execution and Package Install steps and one target38 ms003434
Scenario: Stop job with multiple Configuration Put and Package Uninstall steps and one target27 ms003535
Scenario: Stop job with multiple targets and Asset Write and Package Install steps and one target34 ms003737
Scenario: Stop job with multiple targets and Bundle Start and Package Install steps43 ms003636
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps0.1 sec003737
Scenario: Stop job with multiple targets and Command Execution and Package Install steps27 ms003434
Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps82 ms003737
Scenario: Test account query4 ms0044
Scenario: Test the message store with server timestamp indexing30 ms002626
Scenario: Test the message store with timestamp indexing34 ms002626
Scenario: The Client ID is case sensitive4 ms0088
Scenario: To be defined4 ms001313
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"28 ms0044
Scenario: Translating CommandRequestMessage to null7 ms0044
Scenario: Translating empty message to empty message6 ms0044
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"5 ms0044
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message3 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message6 ms0055
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message3 ms0055
Scenario: Translating kura data message with null channel, and payload without body and with metrics2 ms0055
Scenario: Translating kura data message with valid channel and with null payload4 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 payload3 ms0055
Scenario: Translating kura data message with valid channel, body and metrics into jms message2 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into jms message2 ms0055
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message4 ms0055
Scenario: Translating null to KuraRequestMessage7 ms0044
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message4 ms0055
Scenario: Translating of jms message with empty payload and valid topic into kura data message2 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 message5 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 message6 ms0055
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message4 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 message4 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 message4 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 message7 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 permissions9 ms002121
Scenario: Try to change an existing connection ID3 ms0077
Scenario: Try to create an access into entity with an invalid role id5 ms001212
Scenario: Try to delete a non existing device from the registry6 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 ID5 ms0077
Scenario: Try to update the device client ID4 ms0044
Scenario: Update a group entry in the database12 ms0099
Scenario: Update a group entry with a false ID5 ms001010
Scenario: Update a non existing device3 ms0055
Scenario: Update a nonexistent step definition6 ms0077
Scenario: Update a step definition name9 ms0077
Scenario: Update a step definition processor name5 ms0088
Scenario: Update a step definition target type6 ms0088
Scenario: Update existing role name8 ms0088
Scenario: Update schedule which doesn't exist6 ms0055
Scenario: Update scheduler end date11 ms0099
Scenario: Update scheduler name8 ms0088
Scenario: Update scheduler start date6 ms0088
Scenario: Update trigger definition9 ms0088
Scenario: Update user4 ms0077
Scenario: Update user that doesn't exist5 ms0055
Scenario: User locking itself out by using out login attempts6 ms001616
Scenario: User locking itself out with failed attempts and not waiting to unlock3 ms001717
Scenario: User locking itself out with failed attempts and waiting to unlock8 ms001717
Scenario: User login with wrong pass, but with enough time between login failures4 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 ID10 ms0055
Scenario: Validate a device client based search with an empty client ID5 ms0055
Scenario: Validate a device client search with null scope6 ms0055
Scenario: Validate a device creator with a null client ID4 ms0066
Scenario: Validate a device creator with a null scope ID4 ms0066
Scenario: Validate a device query with a null Scope ID3 ms0044
Scenario: Validate a device search with a null device ID4 ms0066
Scenario: Validate a device search with a null scope ID3 ms0066
Scenario: Validate a null creator3 ms0055
Scenario: Validate a null device3 ms0055
Scenario: Validate a null device count6 ms0055
Scenario: Validate a null device query2 ms0055
Scenario: Validate a regular creator3 ms0044
Scenario: Validate a regular device client search3 ms0044
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device query4 ms0044
Scenario: Validate a regular device search4 ms0055
Scenario: Validate deleting a device with a null device ID6 ms0066
Scenario: Validate deleting a device with a null scope ID4 ms0066
empty) scope1 ms0044