Test Result : (root)

2 failures (-120) , 1 skipped (-1348)
3,649 tests (-1175)
Took 8.9 sec.

All Failed Tests

Test NameDurationAge
 Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description15 ms23
 Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"15 ms23

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 topic6 ms0088
Scenario: Account based ClientInfo data check28 ms0024+1224+12
Scenario: Account name must not be mutable3 ms0066
Scenario: Account wide metrics check31 ms0028+1428+14
Scenario: Adding "Empty" Tag To Device7 ms005+55+5
Scenario: Adding Previously Deleted Tag From Device Again10 ms0011+1111+11
Scenario: Adding Regular Tag Without Description To Device4 ms006+66+6
Scenario: Adding Tag With Long Name Without Description To Device4 ms006+66+6
Scenario: Adding Tag With Numbers Without Description To Device4 ms006+66+6
Scenario: Adding Tag With Short Name Without Description To Device4 ms006+66+6
Scenario: Adding Tag With Special Symbols Without Description To Device4 ms006+66+6
Scenario: All device parameters must match the device creator4 ms0033
Scenario: B1 Broker publish to CTRL_ACC_REPLY15 ms0-20-29+49
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed35 ms0-20-29+49
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed4 ms0-20-28+48
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI17 ms0099
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed12 ms0-20-29+49
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed8 ms0-20-28+48
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY24 ms0-20-29+49
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY18 ms0099
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account19 ms0-20-29+49
Scenario: B5 Broker publish to CTRL_ACC is not allowed12 ms0099
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed11 ms0099
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed7 ms0-20-28+48
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI10 ms0099
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed19 ms0-20-29+49
Scenario: Basic Device Event queries6 ms0010-410-4
Scenario: Captured date based ClientInfo data check31 ms0030+1530+15
Scenario: Case sensitiveness of named device searches4 ms004+44+4
Scenario: Change role name so it is too short0 ms006+66+6
Scenario: Change the account parent path3 ms0055
Scenario: Changing Description On Tag With Long Description5 ms004+44+4
Scenario: Changing Description On Tag With Long Name3 ms005+55+5
Scenario: Changing Description On Tag With Numbers In Name5 ms006+66+6
Scenario: Changing Description On Tag With Permitted Symbols In Name4 ms004+44+4
Scenario: Changing Description On Tag With Short Description4 ms004+44+4
Scenario: Changing Description On Tag With Short Name3 ms004+44+4
Scenario: Changing Tag's Description To Non-Unique One4 ms005+55+5
Scenario: Changing Tag's Description To Unique One4 ms007+77+7
Scenario: Changing Tag's Name To Contain Invalid Symbols In Name Without Description4 ms005+55+5
Scenario: Changing Tag's Name To Contain Permitted Symbols In Name Without Description4 ms005+55+5
Scenario: Changing Tag's Name To Non-Unique One4 ms006+66+6
Scenario: Changing Tag's Name To Short One Without Description4 ms007+77+7
Scenario: Changing Tag's Name To Unique One4 ms007+77+7
Scenario: Changing Tag's Name To a Long One Without Description3 ms007+77+7
Scenario: Changing Tag's Name To a Too Long One Without Description4 ms005+55+5
Scenario: Changing Tag's Name To a Too Short One Without Description4 ms005+55+5
Scenario: Changing description of a nonexisting role4 ms007+77+7
Scenario: Changing job description to non-unique one6 ms007+77+7
Scenario: Changing job description to the long one7 ms006+66+6
Scenario: Changing job description to unique one6 ms006+66+6
Scenario: Changing job description to very short one7 ms007+77+7
Scenario: Changing job name to a long one without description12 ms007+77+7
Scenario: Changing job name to a too long one without description7 ms005+55+5
Scenario: Changing job name to a too short one without description9 ms006+66+6
Scenario: Changing job name to contain invalid symbols in name without description6 ms004+44+4
Scenario: Changing job name to contain permitted symbols in name without description5 ms005+55+5
Scenario: Changing job name to non-unique one5 ms008+88+8
Scenario: Changing job name to short one without description9 ms007+77+7
Scenario: Changing job name to unique one4 ms009+99+9
Scenario: Changing name of a nonexisting role6 ms007+77+7
Scenario: Changing role description to a valid one3 ms006+66+6
Scenario: Changing role name so it is too long3 ms006+66+6
Scenario: Changing role name to contain special character3 ms004+44+4
Scenario: Changing role name to null4 ms006+66+6
Scenario: Changing role's name to a valid one5 ms006+66+6
Scenario: Channel info queries based on datastore channel filters32 ms0050+2550+25
Scenario: ChannelInfo client ID and topic data based on the client id26 ms0028+1428+14
Scenario: ChannelInfo client ID based on the account id32 ms0026+1326+13
Scenario: ChannelInfo last published date26 ms0030+1530+15
Scenario: ChannelInfo topic data based on the account id31 ms0026+1326+13
Scenario: Check account properties6 ms0044
Scenario: Check the Device Connection Domain data seetting3 ms0022
Scenario: Check the database cache coherency20 ms0030+1530+15
Scenario: Check the mapping for message semantic topics26 ms0030+1530+15
Scenario: Check the message store26 ms0020+1020+10
Scenario: Check the sanity of the Device Connection Domain data initialization2 ms0022
Scenario: Client Id based ClientInfo data check25 ms0028+1428+14
Scenario: Connection Service factory sanity checks3 ms0022
Scenario: Count connections in empty scope4 ms0044
Scenario: Count connections in scope5 ms0055
Scenario: Count devices with a specific BIOS version4 ms0066
Scenario: Count events in empty scope6 ms006-46-4
Scenario: Count step definition items5 ms0044
Scenario: Count step definitions in wrong (empty) scope5 ms0011
Scenario: Count user5 ms0066
Scenario: Counting created roles items in the DB4 ms005+55+5
Scenario: Create a regular event34 ms008-28-2
Scenario: Create a single device with an empty string for clientID5 ms004+44+4
Scenario: Create a single device with null clientID value4 ms004+44+4
Scenario: Create a valid job entry36 ms006+66+6
Scenario: Create an event with a null scope ID9 ms007-37-3
Scenario: Create index with specific prefix9 ms0012-112-1
Scenario: Create multiple users3 ms0055
Scenario: Create scheduler with correct end date9 ms008+88+8
Scenario: Create scheduler with empty schedule name17 ms008+88+8
Scenario: Create scheduler with end date before start date13 ms009+99+9
Scenario: Create scheduler with invalid Retry Interval property6 ms009+99+9
Scenario: Create scheduler with invalid cron job trigger property6 ms009+99+9
Scenario: Create scheduler with invalid schedule name12 ms008+88+8
Scenario: Create scheduler with short schedule name11 ms008+88+8
Scenario: Create scheduler with too long schedule name16 ms008+88+8
Scenario: Create scheduler with valid Retry Interval property8 ms007+77+7
Scenario: Create scheduler with valid cron job trigger property10 ms007+77+7
Scenario: Create scheduler with valid schedule name42 ms006+66+6
Scenario: Create scheduler without Cron Job Trigger property12 ms009+99+9
Scenario: Create scheduler without Retry Interval property8 ms009+99+9
Scenario: Create scheduler without start date10 ms007+77+7
Scenario: Create user that already exist4 ms0077
Scenario: Create user that has more than DB allowed length11 ms0055
Scenario: Create user with short name9 ms0055
Scenario: Create user with special characters in his name7 ms0055
Scenario: Creating Non-Unique Tag With Valid Description4 ms005+55+5
Scenario: Creating Non-unique Tag Without Description9 ms004+44+4
Scenario: Creating Tag With Invalid Symbols In Name With Valid Description4 ms004+44+4
Scenario: Creating Tag With Invalid Symbols In Name Without Description4 ms004+44+4
Scenario: Creating Tag With Long Name With Valid Description7 ms004+44+4
Scenario: Creating Tag With Long Name Without Description7 ms004+44+4
Scenario: Creating Tag With Numbers In Name With Valid Description5 ms004+44+4
Scenario: Creating Tag With Numbers In Name Without Description9 ms004+44+4
Scenario: Creating Tag With Permitted Symbols In Name With Valid Description3 ms004+44+4
Scenario: Creating Tag With Permitted Symbols In Name Without Description5 ms004+44+4
Scenario: Creating Tag With Short Name With Valid Description9 ms004+44+4
Scenario: Creating Tag With Short Name Without Description8 ms004+44+4
Scenario: Creating Tag With Too Long Name With Valid Description3 ms004+44+4
Scenario: Creating Tag With Too Long Name Without Description8 ms004+44+4
Scenario: Creating Tag With Too Short Name With Valid Description3 ms004+44+4
Scenario: Creating Tag With Too Short Name Without Description5 ms004+44+4
Scenario: Creating Tag Without a Name And With Valid Description4 ms004+44+4
Scenario: Creating Tag Without a Name And Without Description5 ms004+44+4
Scenario: Creating Unique Tag With Long Description7 ms004+44+4
Scenario: Creating Unique Tag With Non-unique Description4 ms005+55+5
Scenario: Creating Unique Tag With Short Description4 ms004+44+4
Scenario: Creating Unique Tag With Unique Description5 ms004+44+4
Scenario: Creating Unique Tag Without Description24 ms004+44+4
Scenario: Creating a Access Group with invalid special symbols in name3 ms004+44+4
Scenario: Creating a job with name only12 ms006+66+6
Scenario: Creating a job with null name15 ms005+55+5
Scenario: Creating a job without name with valid description3 ms005+55+5
Scenario: Creating a new PASSWORD Credential meeting a custom length requirement8 ms004+44+4
Scenario: Creating a new PASSWORD Credential meeting the standard length requirement24 ms003+33+3
Scenario: Creating a new PASSWORD Credential not meeting a custom length requirement6 ms005+55+5
Scenario: Creating a new PASSWORD Credential not meeting the standard length requirement9 ms004+44+4
Scenario: Creating a role name with allowed symbols in its name4 ms005+55+5
Scenario: Creating a role with 255 characters long description2 ms005+55+5
Scenario: Creating a role with a name and description that contain digits only22 ms005+55+5
Scenario: Creating a role with forbidden symbols in its name0 ms004+44+4
Scenario: Creating a role with name only3 ms005+55+5
Scenario: Creating a role with null name3 ms005+55+5
Scenario: Creating a role with regular name and very short description" as description cannot be too short, as even one character is enough3 ms005+55+5
Scenario: Creating a role with special characters in the description3 ms004+44+4
Scenario: Creating a role with the name that contains digits2 ms005+55+5
Scenario: Creating a role with too long name1 ms005+55+5
Scenario: Creating a role with too short name3 ms005+55+5
Scenario: Creating a role with valid name and with too long description9 ms003+33+3
Scenario: Creating a role wtih 255 characters long name5 ms005+55+5
Scenario: Creating a single device with case sensitive clientID4 ms005+55+5
Scenario: Creating a single device with clientID that contains 255 characters5 ms005+55+5
Scenario: Creating a single device with clientID that contains 256 characters3 ms004+44+4
Scenario: Creating a single device with clientID that contains invalid character4 ms004+44+4
Scenario: Creating a single device with clientID that contains invalid characters1 ms004+44+4
Scenario: Creating a single device with spaces in clientID6 ms005+55+5
Scenario: Creating a single device with valid clientID5 ms005+55+5
Scenario: Creating a valid Access Group with numbers in name4 ms005+55+5
Scenario: Creating a valid Access Group with only numbers in name5 ms005+55+5
Scenario: Creating a valid Access Group with unique name6 ms005+55+5
Scenario: Creating a valid Access Group with valid special symbols in name4 ms005+55+5
Scenario: Creating a valid role5 ms005+55+5
Scenario: Creating an Access Group with empty name7 ms004+44+4
Scenario: Creating an Access Group with long name4 ms005+55+5
Scenario: Creating an Access Group with short name8 ms005+55+5
Scenario: Creating an Access Group with too long name5 ms004+44+4
Scenario: Creating an Access Group with too short name7 ms004+44+4
Scenario: Creating an Access Group without name and with description8 ms004+44+4
Scenario: Creating index with regular user19 ms002525
Scenario: Creating job with invalid symbols in name without description4 ms004+44+4
Scenario: Creating job with long name and valid description7 ms006+66+6
Scenario: Creating job with long name without description13 ms006+66+6
Scenario: Creating job with numbers in name and valid description5 ms006+66+6
Scenario: Creating job with numbers in name without description6 ms006+66+6
Scenario: Creating job with permitted symbols in name without description10 ms003+33+3
Scenario: Creating job with short name and valid job description6 ms006+66+6
Scenario: Creating job with short name without description13 ms006+66+6
Scenario: Creating job with too long name and valid description5 ms005+55+5
Scenario: Creating job with too long name without description7 ms005+55+5
Scenario: Creating job with too short name and valid description6 ms005+55+5
Scenario: Creating job with too short name without description11 ms005+55+5
Scenario: Creating job without name and without description8 ms005+55+5
Scenario: Creating non-unique Access Group4 ms005+55+5
Scenario: Creating non-unique Access Group with unique description4 ms005+55+5
Scenario: Creating non-unique job name with valid job description6 ms007+77+7
Scenario: Creating two device with the same clientID8 ms005+55+5
Scenario: Creating two indexes with daily index9 ms001717
Scenario: Creating two indexes with hourly index19 ms001717
Scenario: Creating two indexes with weekly index15 ms001717
Scenario: Creating two roles with the same description5 ms006+66+6
Scenario: Creating two roles with the same name6 ms007+77+7
Scenario: Creating unique Access Group with long description5 ms005+55+5
Scenario: Creating unique Access Group with non-unique description5 ms006+66+6
Scenario: Creating unique Access Group with numbers in description8 ms005+55+5
Scenario: Creating unique Access Group with only numbers in description5 ms005+55+5
Scenario: Creating unique Access Group with short description4 ms005+55+5
Scenario: Creating unique Access Group with special symbols in description30 ms2+21+11+14+4
Scenario: Creating unique Access Group with unique description5 ms005+55+5
Scenario: Creating unique job with long description5 ms006+66+6
Scenario: Creating unique job with non-unique description8 ms0010+1010+10
Scenario: Creating unique job with short description6 ms006+66+6
Scenario: Creating user22 ms0055
Scenario: D1 Device publish to CTRL_ACC_REPLY8 ms0-20-29+49
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI9 ms0099
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed9 ms0-20-29+49
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed12 ms0077
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY12 ms0-20-29+49
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY18 ms0099
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account5 ms0-20-29+49
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC9 ms0099
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI9 ms0099
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed9 ms0-20-29+49
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed13 ms0-20-29+49
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed13 ms0-20-28+48
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed16 ms0-20-29+49
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI15 ms0099
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed12 ms0-20-29+49
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed7 ms0-20-28+48
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY13 ms0-20-29+49
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY14 ms0099
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account8 ms0-20-29+49
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed14 ms0099
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed14 ms0099
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed4 ms0-20-28+48
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI10 ms0099
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC16 ms0099
Scenario: DV1 Data view publish to CTRL_ACC_REPLY5 ms0-20-29+49
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed13 ms0-20-29+49
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed8 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 allowed14 ms0099
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed15 ms0-20-29+49
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed9 ms0-20-28+48
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY21 ms0-20-29+49
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY18 ms0099
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account5 ms0-20-29+49
Scenario: DV5 Data view publish to CTRL_ACC is not allowed3 ms0099
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed19 ms0099
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed4 ms0-20-28+48
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI12 ms0099
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed17 ms0-20-29+49
Scenario: Delete Kapua system user4 ms0055
Scenario: Delete a connection from the database6 ms008+18+1
Scenario: Delete a non existent event8 ms007-47-4
Scenario: Delete a non existing connection3 ms007+17+1
Scenario: Delete a step definition4 ms0088
Scenario: Delete a step definition twice6 ms0077
Scenario: Delete an existing account6 ms0055
Scenario: Delete an existing device from the registry4 ms0044
Scenario: Delete an existing event8 ms009-49-4
Scenario: Delete items based on query results33 ms0084+4284+42
Scenario: Delete items by date ranges1 sec00132+132132+132
Scenario: Delete items by the datastore ID26 ms0066+3366+33
Scenario: Delete nonexisting account4 ms0044
Scenario: Delete scheduler6 ms008+88+8
Scenario: Delete scheduler which doesn't exist5 ms005+55+5
Scenario: Delete the Kapua system account5 ms0055
Scenario: Delete user9 ms0066
Scenario: Delete user that doesn't exist4 ms0055
Scenario: Deleting Existing Tag And Creating It Again With Same Name10 ms007+77+7
Scenario: Deleting Non-Existent Tag4 ms007+77+7
Scenario: Deleting Tag From Device4 ms008+88+8
Scenario: Deleting Tag's Name And Leaving It Empty Without Description7 ms005+55+5
Scenario: Deleting a non-existing Access Group3 ms006+66+6
Scenario: Deleting a role twice3 ms007+77+7
Scenario: Deleting an existing Access Group5 ms005+55+5
Scenario: Deleting an existing Access Group and creating it again with the same name4 ms007+77+7
Scenario: Deleting an existing role1 ms006+66+6
Scenario: Deleting existing tag7 ms009+99+9
Scenario: Device connection update8 ms007+17+1
Scenario: Device factory sanity checks7 ms0022
Scenario: Device queries5 ms0010-310-3
Scenario: Device query - find by BIOS version6 ms0077
Scenario: Editing Access Group description to description with numbers3 ms005+55+5
Scenario: Editing Access Group description to description with only numbers3 ms005+55+5
Scenario: Editing Access Group description to description with special symbols3 ms004+44+4
Scenario: Editing Access Group description to long description6 ms005+55+5
Scenario: Editing Access Group description to non-unique one4 ms005+55+5
Scenario: Editing Access Group description to short description3 ms005+55+5
Scenario: Editing Access Group description to unique one3 ms007+77+7
Scenario: Editing Access Group name to a long one3 ms007+77+7
Scenario: Editing Access Group name to a too long one4 ms005+55+5
Scenario: Editing Access Group name to empty name8 ms005+55+5
Scenario: Editing Access Group name to name that contains numbers6 ms007+77+7
Scenario: Editing Access Group name to name that contains only numbers6 ms007+77+7
Scenario: Editing Access Group name to name with invalid special symbols in name0 ms005+55+5
Scenario: Editing Access Group name to name with valid special symbols6 ms007+77+7
Scenario: Editing Access Group name to non-unique one5 ms006+66+6
Scenario: Editing Access Group name to short one4 ms007+77+7
Scenario: Editing Access Group name to too short one3 ms005+55+5
Scenario: Editing Access Group name to valid one4 ms007+77+7
Scenario: Editing Tag's Name To Contain Numbers Without Description3 ms007+77+7
Scenario: Event factory sanity checks6 ms002-42-4
Scenario: Event service domain check5 ms002-42-4
Scenario: Every account must have the default configuration items6 ms0033
Scenario: Find a connection by its IDs3 ms006+16+1
Scenario: Find a connection by its client ID4 ms006+16+1
Scenario: Find a non existing event7 ms006-46-4
Scenario: Find account by Id9 ms0044
Scenario: Find account by Ids9 ms0044
Scenario: Find account by name12 ms0044
Scenario: Find account by random Id5 ms0033
Scenario: Find all child accounts10 ms0033
Scenario: Find an event by its ID7 ms006-46-4
Scenario: Find by name nonexisting account9 ms0033
Scenario: Find correct number of messages by corresponding metric1 sec0058+5858+58
Scenario: Find device by client ID4 ms0033
Scenario: Find device by registry ID8 ms0044
Scenario: Find multiple users3 ms0055
Scenario: Find user by id10 ms0055
Scenario: Find user by its email4 ms006+66+6
Scenario: Find user by its phone number4 ms006+66+6
Scenario: Find user by name5 ms0055
Scenario: Find user by name that doesn't exist4 ms0033
Scenario: Find user with id and scope id that doesn't exist6 ms0033
Scenario: Finding all messages by selecting all metrics1.2 sec0040+4040+40
Scenario: Finding correct number of messages by corresponding two metrics0.61 sec0052+5252+52
Scenario: Finding messages with incorrect metric parameters0.53 sec0072+7272+72
Scenario: Finding user by expiration date in the future7 ms005+55+5
Scenario: Finding user by expiration date in the past7 ms006+66+6
Scenario: Finding user by expiration date in the present4 ms006+66+6
Scenario: Generic connection query4 ms008+18+1
Scenario: Get metadata6 ms0033
Scenario: Handle account creation23 ms0033
Scenario: Handle duplicate account names9 ms0055
Scenario: Handle null account name10 ms0044
Scenario: I try to find a non-existing connection4 ms006+16+1
Scenario: It should not be possible to change the configuration items3 ms005+55+5
Scenario: MetricsInfo client ID and topic data based on the client id33 ms0034+1734+17
Scenario: MetricsInfo last published date33 ms0048+2448+24
Scenario: Modify an existing account4 ms0044
Scenario: Modify nonexisting account4 ms0066
Scenario: Query based on message ordering30 ms0020+1020+10
Scenario: Query based on metrics ordering26 ms0020+1020+10
Scenario: Query before schema search9 ms0082+4182+41
Scenario: Query for step definitions5 ms0077
Scenario: Query user11 ms0066
Scenario: Regular connection6 ms007+17+1
Scenario: Regular step definition creation5 ms0077
Scenario: Regular step definition with a property list5 ms0044
Scenario: Search for a non existent client ID3 ms006+16+1
Scenario: Set a correct minimum for password length8 ms003+33+3
Scenario: Set an incorrect minimum for password length6 ms006+66+6
Scenario: Set environment variables29 ms0012-3112-31
Scenario: Setting configuration without mandatory items must raise an error4 ms0055
Scenario: Simple positive scenario for creating daily index19 ms001414
Scenario: Simple positive scenario for creating default - weekly index16 ms001212
Scenario: Simple positive scenario for creating hourly index15 ms001414
Scenario: Start broker for all scenarios0.11 sec0-30012+1012-20
Scenario: Start datastore for all scenarios0.48 sec0012-1812-18
Scenario: Start event broker for all scenarios0.11 sec0012-2412-24
Scenario: Step definition factory sanity checks4 ms0022
Scenario: Step definition with a duplicate name6 ms0066
Scenario: Step definition with a null name11 ms0066
Scenario: Step definition with a null scope ID5 ms0066
Scenario: Step definition with an empty name6 ms0055
Scenario: Stop broker after all scenarios83 ms0012-2012-20
Scenario: Stop datastore after all scenarios84 ms0012-1812-18
Scenario: Stop event broker for all scenarios90 ms0012-2412-24
Scenario: Test account query4 ms0044
Scenario: Test the message store with server timestamp indexing21 ms0026+1326+13
Scenario: Test the message store with timestamp indexing20 ms0026+1326+13
Scenario: The Client ID is case sensitive3 ms008+18+1
Scenario: Translating "CommandRequestMessage" to "KuraRequestMessage"34 ms004+44+4
Scenario: Translating CommandRequestMessage to null8 ms004+44+4
Scenario: Translating empty message to empty message7 ms004+44+4
Scenario: Translating from "AssetRequestMessage" to "AssetResponseMessage"4 ms004+44+4
Scenario: Translating invalid jms data message with valid channel, body and metrics into kura data message3 ms005+55+5
Scenario: Translating invalid kura data message with valid channel, body and metrics into jms message3 ms005+55+5
Scenario: Translating invalid kura data message with valid channel, body and metrics into mqtt message3 ms005+55+5
Scenario: Translating kura data message with null channel, and payload without body and with metrics3 ms005+55+5
Scenario: Translating kura data message with valid channel and with null payload4 ms005+55+5
Scenario: Translating kura data message with valid channel and without body and metrics into jms message4 ms005+55+5
Scenario: Translating kura data message with valid channel, and with null payload3 ms005+55+5
Scenario: Translating kura data message with valid channel, body and metrics into jms message5 ms005+55+5
Scenario: Translating kura data message with valid channel, metrics and without body into jms message3 ms005+55+5
Scenario: Translating kura data message with valid channel, metrics and without body into mqtt message3 ms005+55+5
Scenario: Translating null to KuraRequestMessage6 ms004+44+4
Scenario: Translating of jms message with empty payload and invalid topic that contain only userName into kura data message3 ms005+55+5
Scenario: Translating of jms message with empty payload and valid topic into kura data message3 ms006+66+6
Scenario: Translating of jms message with invalid payload and valid topic into kura data message7 ms006+66+6
Scenario: Translating of jms message with valid payload and valid topic into kura data message2 ms006+66+6
Scenario: Translating of mqtt message with invalid payload and invalid topic into kura data message4 ms005+55+5
Scenario: Translating of mqtt message with invalid payload and with null topic into kura data message4 ms005+55+5
Scenario: Translation of kura data message with valid channel and without body and metrics into mqtt message4 ms005+55+5
Scenario: Translation of kura data message with valid channel, body and metrics into mqtt message3 ms005+55+5
Scenario: Translation of kura data message with valid channel, metrics and without body into mqtt message3 ms005+55+5
Scenario: Translation of mqtt message with empty payload into kura data message4 ms006+66+6
Scenario: Translation of mqtt message with invalid payload and invalid topic into kura response message5 ms005+55+5
Scenario: Translation of mqtt message with invalid payload and valid topic into kura data message6 ms006+66+6
Scenario: Translation of mqtt message with invalid payload and valid topic into kura response message5 ms006+66+6
Scenario: Translation of mqtt message with valid payload and invalid topic into kura response message4 ms005+55+5
Scenario: Translation of mqtt message with valid payload and valid topic into kura data message5 ms006+66+6
Scenario: Translation of mqtt message with valid payload and valid topic into kura response message4 ms006+66+6
Scenario: Try to change an existing connection ID3 ms007+17+1
Scenario: Try to delete a non existing device from the registry4 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 modify the connection client ID3 ms007+17+1
Scenario: Try to update the device client ID3 ms0044
Scenario: Update a non existing device5 ms0055
Scenario: Update a nonexistent step definition5 ms0077
Scenario: Update a step definition name6 ms0077
Scenario: Update a step definition processor name4 ms0088
Scenario: Update a step definition target type8 ms0088
Scenario: Update schedule which doesn't exist6 ms005+55+5
Scenario: Update scheduler end date6 ms009+99+9
Scenario: Update scheduler name8 ms008+88+8
Scenario: Update scheduler start date6 ms008+88+8
Scenario: Update trigger definition10 ms008+88+8
Scenario: Update user11 ms0077
Scenario: Update user that doesn't exist5 ms0055
Scenario: Validate a device client based search with a null client ID2 ms005+15+1
Scenario: Validate a device client based search with an empty client ID6 ms005+15+1
Scenario: Validate a device client search with null scope4 ms005+15+1
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 ms004-14-1
Scenario: Validate a device search with a null device ID10 ms006+26+2
Scenario: Validate a device search with a null scope ID1 ms006+26+2
Scenario: Validate a null creator3 ms0055
Scenario: Validate a null device4 ms0055
Scenario: Validate a null device count3 ms0055
Scenario: Validate a null device query3 ms0055
Scenario: Validate a regular creator3 ms0044
Scenario: Validate a regular device client search5 ms004+14+1
Scenario: Validate a regular device count3 ms0044
Scenario: Validate a regular device query4 ms0044
Scenario: Validate a regular device search4 ms005+25+2
Scenario: Validate deleting a device with a null device ID6 ms006+26+2
Scenario: Validate deleting a device with a null scope ID4 ms006+26+2
empty) scope1 ms004-44-4