#1 (Oct 4, 2018, 6:23:30 AM)

Started by user Alberto Codutti

• origin/release-1.0.x

• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Create index with specific prefix.And REST response containing text "custom-prefix-1-2018-01"
• Scenario: Create index with specific prefix.Scenario: Create index with specific prefix
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Simple positive scenario for creating daily index.And REST response containing text "1-2018-01-02"
• Scenario: Simple positive scenario for creating daily index.Scenario: Simple positive scenario for creating daily index
• Scenario: Simple positive scenario for creating hourly index.And REST response containing text "1-2018-01-02-10"
• Scenario: Simple positive scenario for creating hourly index.Scenario: Simple positive scenario for creating hourly index
• Scenario: Creating two indexes with daily index.And REST response containing text "1-2018-01-02"
• Scenario: Creating two indexes with daily index.Scenario: Creating two indexes with daily index
• Scenario: Creating two indexes with hourly index.And REST response containing text "1-2018-01-02-10"
• Scenario: Creating two indexes with hourly index.Scenario: Creating two indexes with hourly index
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Delete items by the datastore ID.Scenario: Delete items by the datastore ID
• Scenario: Delete items based on query results.Scenario: Delete items based on query results
• Scenario: Check the mapping for message semantic topics.Scenario: Check the mapping for message semantic topics
• Scenario: Query before schema search.Scenario: Query before schema search
• Scenario: Check the message store.Scenario: Check the message store
• Scenario: Query based on message ordering.Scenario: Query based on message ordering
• Scenario: Test the message store with timestamp indexing.Scenario: Test the message store with timestamp indexing
• Scenario: Test the message store with server timestamp indexing.Scenario: Test the message store with server timestamp indexing
• Scenario: ChannelInfo client ID based on the account id.Scenario: ChannelInfo client ID based on the account id
• Scenario: ChannelInfo last published date.Scenario: ChannelInfo last published date
• Scenario: ChannelInfo topic data based on the account id.Scenario: ChannelInfo topic data based on the account id
• Scenario: ChannelInfo client ID and topic data based on the client id.Scenario: ChannelInfo client ID and topic data based on the client id
• Scenario: Account wide metrics check.Scenario: Account wide metrics check
• Scenario: MetricsInfo last published date.Scenario: MetricsInfo last published date
• Scenario: MetricsInfo client ID and topic data based on the client id.Scenario: MetricsInfo client ID and topic data based on the client id
• Scenario: Query based on metrics ordering.Scenario: Query based on metrics ordering
• Scenario: Account based ClientInfo data check.Scenario: Account based ClientInfo data check
• Scenario: Client Id based ClientInfo data check.Scenario: Client Id based ClientInfo data check
• Scenario: Channel info queries based on datastore channel filters.Scenario: Channel info queries based on datastore channel filters
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed.Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed
• Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY.Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY
• Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY.Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY
• Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account.Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account
• Scenario: DM5 Data manage publish to CTRL_ACC is not allowed.Scenario: DM5 Data manage publish to CTRL_ACC is not allowed
• Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed.Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed
• Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme"
• Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed.Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed
• Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/foo"
• Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC.Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC
• Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI
• Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.When broker with clientId "client-1" and user "kapua-sys" and password "kapua-password" is listening on topic "#"
• Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic.Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic
• Scenario: B1 Broker publish to CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: B1 Broker publish to CTRL_ACC_REPLY.Scenario: B1 Broker publish to CTRL_ACC_REPLY
• Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY.Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY
• Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"
• Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY.Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY
• Scenario: B5 Broker publish to CTRL_ACC is not allowed.Scenario: B5 Broker publish to CTRL_ACC is not allowed
• Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed.Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed
• Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme"
• Scenario: B7 Broker subscribe on CTRL_ACC is not allowed.Scenario: B7 Broker subscribe on CTRL_ACC is not allowed
• Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI.Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed.Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed
• Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed.Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed
• Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed.Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed
• Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI
• Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: D1 Device publish to CTRL_ACC_REPLY.Scenario: D1 Device publish to CTRL_ACC_REPLY
• Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY.Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY
• Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"
• Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY.Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY
• Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/domino/client-1/CONF-V1/REPLY"
• Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account.Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account
• Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/foo"
• Scenario: D5 Device subscribe - publish - admin on CTRL_ACC.Scenario: D5 Device subscribe - publish - admin on CTRL_ACC
• Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/foo"
• Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI.Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: D7 Device publish to ACL_DATA_ACC is not allowed.Scenario: D7 Device publish to ACL_DATA_ACC is not allowed
• Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Then Broker doesn't receive string "Hello broker" on topic "acme/foo"
• Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed.Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed
• Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Then An exception was thrown
• Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed.Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed
• Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "acme/client-1/foo"
• Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI.Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI
• Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/foo/bar/NOTIFY/client-1"
• Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed
• Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY.Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY
• Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/CONF-V1/REPLY"
• Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY.Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY
• Scenario: DV5 Data view publish to CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: DV5 Data view publish to CTRL_ACC is not allowed.Scenario: DV5 Data view publish to CTRL_ACC is not allowed
• Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed.Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed
• Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic "$EDC/acme/client-1/foo"
• Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI.Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI
• Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed.Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed
• Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed.Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed
• Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed.Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed
• Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed.Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed
• Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed.Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed
• Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.When broker with clientId "client-1" and user "luise" and password "kapua-password" is listening on topic ""
• Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed.Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed
• Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed.Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Send BIRTH message and then DC message.Scenario: Send BIRTH message and then DC message
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker after all scenarios.Scenario: Stop event broker after all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Send BIRTH message and then DC message while broker ip is set by config file.Scenario: Send BIRTH message and then DC message while broker ip is set by config file
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Send BIRTH message and then DC message while broker ip is NOT set.And Device death message is sent
• Scenario: Send BIRTH message and then DC message while broker ip is NOT set.Scenario: Send BIRTH message and then DC message while broker ip is NOT set
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Positive scenario without stealing link.Scenario: Positive scenario without stealing link
• Scenario: Stealing link scenario.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1"
• Scenario: Stealing link scenario.Scenario: Stealing link scenario
• Scenario: Negative scenario when client connects twice with same client id.And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1-1"
• Scenario: Negative scenario when client connects twice with same client id.Scenario: Negative scenario when client connects twice with same client id
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Connect to the system and publish some data.Then Device sim-1 for account kapua-sys is registered after 5 seconds
• Scenario: Connect to the system and publish some data.Scenario: Connect to the system and publish some data
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Birth message handling from a new device.Scenario: Birth message handling from a new device
• Scenario: Birth message handling from an existing device.Scenario: Birth message handling from an existing device
• Scenario: Handling of 2 birth messages.Scenario: Handling of 2 birth messages
• Scenario: Birth and applications event handling.Scenario: Birth and applications event handling
• Scenario: Creating new device and tagging it with specific Tag.Scenario: Creating new device and tagging it with specific Tag
• Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag.Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start broker for all scenarios.Scenario: Start broker for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
• Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Then Device sim-1 for account kapua-sys is registered after 5 seconds
• Scenario: Starting and stopping the simulator should create a device entry and properly set its status.Scenario: Starting and stopping the simulator should create a device entry and properly set its status
• Scenario: Installing a package.Scenario: Installing a package
• Scenario: Stop broker after all scenarios.Scenario: Stop broker after all scenarios
• Scenario: Stop datastore after all scenarios.Scenario: Stop datastore after all scenarios
• Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios
• Scenario: Handle account creation.Scenario: Handle account creation
• Scenario: Find all child accounts.Scenario: Find all child accounts
• Scenario: Handle duplicate account names.Scenario: Handle duplicate account names
• Scenario: Handle null account name.Scenario: Handle null account name
• Scenario: Find account by Id.Given An existing account with the name "test_acc_42"
• Scenario: Find account by Id.Scenario: Find account by Id
• Scenario: Find account by Ids.Scenario: Find account by Ids
• Scenario: Find account by random Id.Scenario: Find account by random Id
• Scenario: Find account by name.Scenario: Find account by name
• Scenario: Find by name nonexisting account.Scenario: Find by name nonexisting account
• Scenario: Modify an existing account.Scenario: Modify an existing account
• Scenario: Modify nonexisting account.Scenario: Modify nonexisting account
• Scenario: Delete an existing account.Scenario: Delete an existing account
• Scenario: Delete the Kapua system account.Scenario: Delete the Kapua system account
• Scenario: Delete nonexisting account.Scenario: Delete nonexisting account
• Scenario: Change the account parent Id.Scenario: Change the account parent Id
• Scenario: Change the account parent path.Scenario: Change the account parent path
• Scenario: Check account properties.Scenario: Check account properties
• Scenario: Every account must have the default configuration items.Scenario: Every account must have the default configuration items
• Scenario: A newly created account must have some metadata.Scenario: A newly created account must have some metadata
• Scenario: It is possible to change the configuration items.Scenario: It is possible to change the configuration items
• Scenario: Unknown configuiration items are silently ignored.Scenario: Unknown configuiration items are silently ignored
• Scenario: Setting configuration without mandatory items must raise an error.Scenario: Setting configuration without mandatory items must raise an error
• Scenario: Test account query.Scenario: Test account query
• Scenario: Account service metadata.Scenario: Account service metadata
• Scenario: Account name must not be mutable.Scenario: Account name must not be mutable
• Scenario: Account expiration date test - Parent expiration set, child expiration null.Scenario: Account expiration date test - Parent expiration set, child expiration null
• Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration.Given An existing account that expires on "2018-07-11" with the name "exp-acc"
• Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration.Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration
• Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration.Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration
• Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date.Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.testMetricsInfoFindClientByPublishDateByAccount
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.queryBeforeSchema
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.checkRegistryCache
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.checkMappingForSameMetricNameAndDifferentType
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.testMessageOrderingMixedTest
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.deleteByDate
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.testStore
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.testChannelInfoFindClientIdByAccount
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.testMetricOrderingMixedTest
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.testClientInfoFindClientIdByPublishDateByAccount
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.testChannelInfoFindClientIdByPublishDateByAccount
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.testTopicsByAccount
• org.eclipse.kapua.service.datastore.internal.MessageStoreServiceTest.testClientInfoByClientId
• Scenario: Create a regular event.Scenario: Create a regular event
• Scenario: Create a regular event.Scenario: Create a regular event
• Scenario: Create an event with a null action.Scenario: Create an event with a null action
• Scenario: Create an event with a null action.Scenario: Create an event with a null action
• Scenario: Find an event by its ID.And I configure the device service
• Scenario: Find an event by its ID.Scenario: Find an event by its ID
• Scenario: Find a non existing event.Scenario: Find a non existing event
• Scenario: Delete an existing event.Scenario: Delete an existing event
• Scenario: Delete a non existent event.Scenario: Delete a non existent event
• Scenario: Find a connection by its client ID.Scenario: Find a connection by its client ID
• Scenario: Search for a non existent client ID.Scenario: Search for a non existent client ID
• Scenario: The Client ID is case sensitive.Scenario: The Client ID is case sensitive
• Scenario: The Client ID is case sensitive.Scenario: The Client ID is case sensitive
• Scenario: Delete a connection from the database.Scenario: Delete a connection from the database
• Scenario: Delete a connection from the database.Scenario: Delete a connection from the database
• Scenario: Delete a connection from the database.Scenario: Delete a connection from the database
• Scenario: Delete a non existing connection.Scenario: Delete a non existing connection
• Scenario: Delete a non existing connection.Scenario: Delete a non existing connection
• Scenario: Delete a non existing connection.Scenario: Delete a non existing connection
• Scenario: Generic connection query.Scenario: Generic connection query
• Scenario: Generic connection query.Scenario: Generic connection query
• Scenario: Generic connection query.Scenario: Generic connection query
• Scenario: Connection Service factory sanity checks.Scenario: Connection Service factory sanity checks
• Scenario: Connection Service factory sanity checks.Scenario: Connection Service factory sanity checks
• Scenario: Connection Service factory sanity checks.Scenario: Connection Service factory sanity checks
• Scenario: Check the sanity of the Device Connection Domain data initialization.Scenario: Check the sanity of the Device Connection Domain data initialization
• Scenario: Check the sanity of the Device Connection Domain data initialization.Scenario: Check the sanity of the Device Connection Domain data initialization
• Scenario: Check the Device Connection Domain data seetting.Scenario: Check the Device Connection Domain data seetting
• Scenario: Check the Device Connection Domain data seetting.Scenario: Check the Device Connection Domain data seetting
• Scenario: Check the Device Connection Domain data seetting.Scenario: Check the Device Connection Domain data seetting
• Scenario: Validate a regular creator.Scenario: Validate a regular creator
• Scenario: Validate a regular creator.Scenario: Validate a regular creator
• Scenario: Validate a regular creator.Scenario: Validate a regular creator
• Scenario: Validate a null creator.Scenario: Validate a null creator
• Scenario: Validate a null creator.Scenario: Validate a null creator
• Scenario: Validate a device creator with a null scope ID.Scenario: Validate a device creator with a null scope ID
• Scenario: Validate a device creator with a null scope ID.Scenario: Validate a device creator with a null scope ID
• Scenario: Validate a device creator with a null scope ID.Scenario: Validate a device creator with a null scope ID
• Scenario: Validate a device creator with a null client ID.Scenario: Validate a device creator with a null client ID
• Scenario: Validate a device creator with a null client ID.Scenario: Validate a device creator with a null client ID
• Scenario: Validate a device creator with a null client ID.Scenario: Validate a device creator with a null client ID
• Scenario: Validate a regular device.Scenario: Validate a regular device
• Scenario: Validate a regular device.Scenario: Validate a regular device
• Scenario: Validate a regular device.Scenario: Validate a regular device
• Scenario: Validate a null device.Scenario: Validate a null device
• Scenario: Validate a regular device search.Scenario: Validate a regular device search
• Scenario: Validate a regular device search.Scenario: Validate a regular device search
• Scenario: Validate a regular device search.Scenario: Validate a regular device search
• Scenario: Validate a device search with a null device ID.Scenario: Validate a device search with a null device ID
• Scenario: Validate a device search with a null device ID.Scenario: Validate a device search with a null device ID
• Scenario: Validate a device search with a null device ID.Scenario: Validate a device search with a null device ID
• Scenario: Validate a device search with a null scope ID.Scenario: Validate a device search with a null scope ID
• Scenario: Validate a device search with a null scope ID.Scenario: Validate a device search with a null scope ID
• Scenario: Validate a regular device deletion.Scenario: Validate a regular device deletion
• Scenario: Validate a regular device deletion.Scenario: Validate a regular device deletion
• Scenario: Validate deleting a device with a null device ID.Scenario: Validate deleting a device with a null device ID
• Scenario: Validate deleting a device with a null device ID.Scenario: Validate deleting a device with a null device ID
• Scenario: Validate deleting a device with a null scope ID.Scenario: Validate deleting a device with a null scope ID
• Scenario: Validate deleting a device with a null scope ID.Scenario: Validate deleting a device with a null scope ID
• Scenario: Validate a regular device client search.Scenario: Validate a regular device client search
• Scenario: Validate a regular device client search.Scenario: Validate a regular device client search
• Scenario: Validate a regular device client search.Scenario: Validate a regular device client search
• Scenario: Validate a device client search with null scope.Scenario: Validate a device client search with null scope
• Scenario: Validate a device client based search with a null client ID.Scenario: Validate a device client based search with a null client ID
• Scenario: Validate a device client based search with a null client ID.Scenario: Validate a device client based search with a null client ID
• Scenario: Validate a device client based search with an empty client ID.Scenario: Validate a device client based search with an empty client ID
• Scenario: Validate a device client based search with an empty client ID.Scenario: Validate a device client based search with an empty client ID
• Scenario: Validate a regular device query.Scenario: Validate a regular device query
• Scenario: Validate a regular device query.Scenario: Validate a regular device query
• Scenario: Validate a regular device query.Scenario: Validate a regular device query
• Scenario: Validate a null device query.Scenario: Validate a null device query
• Scenario: Validate a null device query.Scenario: Validate a null device query
• Scenario: Validate a device query with a null Scope ID.Scenario: Validate a device query with a null Scope ID
• Scenario: Validate a device query with a null Scope ID.Scenario: Validate a device query with a null Scope ID
• Scenario: Validate a regular device count.Scenario: Validate a regular device count
• Scenario: Validate a regular device count.Scenario: Validate a regular device count
• Scenario: Validate a regular device count.Scenario: Validate a regular device count
• Scenario: Validate a null device count.Scenario: Validate a null device count
• Scenario: Validate a null device count.Scenario: Validate a null device count
• Scenario: Validate a null device count.Scenario: Validate a null device count
• Scenario: Validate a device count with a null Scope ID.Scenario: Validate a device count with a null Scope ID
• Scenario: Validate a device count with a null Scope ID.Scenario: Validate a device count with a null Scope ID
• Scenario: Validate a device count with a null Scope ID.Scenario: Validate a device count with a null Scope ID
• Scenario: A mock test scenario.Scenario: A mock test scenario
• Scenario: A mock test scenario.Scenario: A mock test scenario
• Scenario: A mock test scenario.Scenario: A mock test scenario
• Scenario: A mock test scenario.Scenario: A mock test scenario
• Scenario: A mock test scenario.Scenario: A mock test scenario
• Scenario: Regular job execution creation.Scenario: Regular job execution creation
• Scenario: Regular job execution creation.Scenario: Regular job execution creation
• Scenario: Regular job execution creation.Scenario: Regular job execution creation
• Scenario: Regular job execution creation.Scenario: Regular job execution creation
• Scenario: Regular job execution creation.Scenario: Regular job execution creation
• Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item
• Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item
• Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item
• Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item
• Scenario: Update the end time of an existing execution item.Scenario: Update the end time of an existing execution item
• Scenario: Delete a job execution item.Scenario: Delete a job execution item
• Scenario: Delete a job execution item.Scenario: Delete a job execution item
• Scenario: Delete a job execution item.Scenario: Delete a job execution item
• Scenario: Delete a job execution item.Scenario: Delete a job execution item
• Scenario: Delete a job execution item.Scenario: Delete a job execution item
• Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice
• Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice
• Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice
• Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice
• Scenario: Delete a job execution item twice.Scenario: Delete a job execution item twice
• Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job
• Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job
• Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job
• Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job
• Scenario: Create and count several execution items for a job.Scenario: Create and count several execution items for a job
• Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job
• Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job
• Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job
• Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job
• Scenario: Query for executions of a specific job.Scenario: Query for executions of a specific job
• Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks
• Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks
• Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks
• Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks
• Scenario: Job execution factory sanity checks.Scenario: Job execution factory sanity checks
• Scenario: Regular job creation.Scenario: Regular job creation
• Scenario: Regular job creation.Scenario: Regular job creation
• Scenario: Regular job creation.Scenario: Regular job creation
• Scenario: Regular job creation.Scenario: Regular job creation
• Scenario: Regular job creation.Scenario: Regular job creation
• Scenario: Job with a null scope ID.Scenario: Job with a null scope ID
• Scenario: Job with a null scope ID.Scenario: Job with a null scope ID
• Scenario: Job with a null scope ID.Scenario: Job with a null scope ID
• Scenario: Job with a null scope ID.Scenario: Job with a null scope ID
• Scenario: Job with a null scope ID.Scenario: Job with a null scope ID
• Scenario: Job with a null name.Scenario: Job with a null name
• Scenario: Job with a null name.Scenario: Job with a null name
• Scenario: Job with a null name.Scenario: Job with a null name
• Scenario: Job with an empty name.Scenario: Job with an empty name
• Scenario: Job with an empty name.Scenario: Job with an empty name
• Scenario: Job with an empty name.Scenario: Job with an empty name
• Scenario: Job with an empty name.Scenario: Job with an empty name
• Scenario: Job with an empty name.Scenario: Job with an empty name
• Scenario: Job with a duplicate name.Scenario: Job with a duplicate name
• Scenario: Job with a duplicate name.Scenario: Job with a duplicate name
• Scenario: Job with a duplicate name.Scenario: Job with a duplicate name
• Scenario: Job with a duplicate name.Scenario: Job with a duplicate name
• Scenario: Delete a job.Scenario: Delete a job
• Scenario: Delete a job.Scenario: Delete a job
• Scenario: Delete a job.Scenario: Delete a job
• Scenario: Delete a job.Scenario: Delete a job
• Scenario: Delete a job.Scenario: Delete a job
• Scenario: Delete a job twice.Scenario: Delete a job twice
• Scenario: Delete a job twice.Scenario: Delete a job twice
• Scenario: Delete a job twice.Scenario: Delete a job twice
• Scenario: Delete a job twice.Scenario: Delete a job twice
• Scenario: Delete a job twice.Scenario: Delete a job twice
• Scenario: Update a job name.Scenario: Update a job name
• Scenario: Update a job name.Scenario: Update a job name
• Scenario: Update a job name.Scenario: Update a job name
• Scenario: Update a job name.Scenario: Update a job name
• Scenario: Update a job name.Scenario: Update a job name
• Scenario: Update a job description.Scenario: Update a job description
• Scenario: Update a job description.Scenario: Update a job description
• Scenario: Update a job description.Scenario: Update a job description
• Scenario: Update a job description.Scenario: Update a job description
• Scenario: Update a job description.Scenario: Update a job description
• Scenario: Update a job XML definition.Scenario: Update a job XML definition
• Scenario: Update a job XML definition.Scenario: Update a job XML definition
• Scenario: Update a job XML definition.Scenario: Update a job XML definition
• Scenario: Update a job XML definition.Scenario: Update a job XML definition
• Scenario: Update a job XML definition.Scenario: Update a job XML definition
• Scenario: Update a nonexistent job.Scenario: Update a nonexistent job
• Scenario: Update a nonexistent job.Scenario: Update a nonexistent job
• Scenario: Update a nonexistent job.Scenario: Update a nonexistent job
• Scenario: Update a nonexistent job.Scenario: Update a nonexistent job
• Scenario: Count job items.Scenario: Count job items
• Scenario: Count job items.Scenario: Count job items
• Scenario: Count job items.Scenario: Count job items
• Scenario: Count job items.Scenario: Count job items
• Scenario: Count job items.Scenario: Count job items
• Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong
• Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong
• Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong
• Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong
• Scenario: Count job items in wrong (empty) scope.Scenario: Count job items in wrong
• Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name
• Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name
• Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name
• Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name
• Scenario: Query for jobs with specified name.Scenario: Query for jobs with specified name
• Scenario: Job factory sanity checks.Scenario: Job factory sanity checks
• Scenario: Job factory sanity checks.Scenario: Job factory sanity checks
• Scenario: Job factory sanity checks.Scenario: Job factory sanity checks
• Scenario: Job factory sanity checks.Scenario: Job factory sanity checks
• Scenario: Job factory sanity checks.Scenario: Job factory sanity checks
• Scenario: Regular step definition creation.Scenario: Regular step definition creation
• Scenario: Regular step definition creation.Scenario: Regular step definition creation
• Scenario: Regular step definition creation.Scenario: Regular step definition creation
• Scenario: Regular step definition creation.Scenario: Regular step definition creation
• Scenario: Regular step definition creation.Scenario: Regular step definition creation
• Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list
• Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list
• Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list
• Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list
• Scenario: Regular step definition with a property list.Scenario: Regular step definition with a property list
• Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID
• Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID
• Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID
• Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID
• Scenario: Step definition with a null scope ID.Scenario: Step definition with a null scope ID
• Scenario: Step definition with a null name.Scenario: Step definition with a null name
• Scenario: Step definition with a null name.Scenario: Step definition with a null name
• Scenario: Step definition with a null name.Scenario: Step definition with a null name
• Scenario: Step definition with a null name.Scenario: Step definition with a null name
• Scenario: Step definition with a null name.Scenario: Step definition with a null name
• Scenario: Step definition with an empty name.Scenario: Step definition with an empty name
• Scenario: Step definition with an empty name.Scenario: Step definition with an empty name
• Scenario: Step definition with an empty name.Scenario: Step definition with an empty name
• Scenario: Step definition with an empty name.Scenario: Step definition with an empty name
• Scenario: Step definition with an empty name.Scenario: Step definition with an empty name
• Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name
• Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name
• Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name
• Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name
• Scenario: Step definition with a duplicate name.Scenario: Step definition with a duplicate name
• Scenario: Delete a step definition.Scenario: Delete a step definition
• Scenario: Delete a step definition.Scenario: Delete a step definition
• Scenario: Delete a step definition.Scenario: Delete a step definition
• Scenario: Delete a step definition.Scenario: Delete a step definition
• Scenario: Delete a step definition.Scenario: Delete a step definition
• Scenario: Delete a step definition twice.Scenario: Delete a step definition twice
• Scenario: Delete a step definition twice.Scenario: Delete a step definition twice
• Scenario: Delete a step definition twice.Scenario: Delete a step definition twice
• Scenario: Delete a step definition twice.Scenario: Delete a step definition twice
• Scenario: Delete a step definition twice.Scenario: Delete a step definition twice
• Scenario: Update a step definition name.Scenario: Update a step definition name
• Scenario: Update a step definition name.Scenario: Update a step definition name
• Scenario: Update a step definition name.Scenario: Update a step definition name
• Scenario: Update a step definition name.Scenario: Update a step definition name
• Scenario: Update a step definition name.Scenario: Update a step definition name
• Scenario: Update a step definition target type.Scenario: Update a step definition target type
• Scenario: Update a step definition target type.Scenario: Update a step definition target type
• Scenario: Update a step definition target type.Scenario: Update a step definition target type
• Scenario: Update a step definition target type.Scenario: Update a step definition target type
• Scenario: Update a step definition target type.Scenario: Update a step definition target type
• Scenario: Update a step definition processor name.Scenario: Update a step definition processor name
• Scenario: Update a step definition processor name.Scenario: Update a step definition processor name
• Scenario: Update a step definition processor name.Scenario: Update a step definition processor name
• Scenario: Update a step definition processor name.Scenario: Update a step definition processor name
• Scenario: Update a step definition processor name.Scenario: Update a step definition processor name
• Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition
• Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition
• Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition
• Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition
• Scenario: Update a nonexistent step definition.Scenario: Update a nonexistent step definition
• Scenario: Count step definition items.Scenario: Count step definition items
• Scenario: Count step definition items.Scenario: Count step definition items
• Scenario: Count step definition items.Scenario: Count step definition items
• Scenario: Count step definition items.Scenario: Count step definition items
• Scenario: Count step definition items.Scenario: Count step definition items
• Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong
• Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong
• Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong
• Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong
• Scenario: Count step definitions in wrong (empty) scope.Scenario: Count step definitions in wrong
• Scenario: Query for step definitions.Scenario: Query for step definitions
• Scenario: Query for step definitions.Scenario: Query for step definitions
• Scenario: Query for step definitions.Scenario: Query for step definitions
• Scenario: Query for step definitions.Scenario: Query for step definitions
• Scenario: Query for step definitions.Scenario: Query for step definitions
• Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks
• Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks
• Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks
• Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks
• Scenario: Step definition factory sanity checks.Scenario: Step definition factory sanity checks
• Scenario: Regular step creation.Scenario: Regular step creation
• Scenario: Regular step creation.Scenario: Regular step creation
• Scenario: Regular step creation.Scenario: Regular step creation
• Scenario: Regular step creation.Scenario: Regular step creation
• Scenario: Regular step creation.Scenario: Regular step creation
• Scenario: Step with a null scope ID.Scenario: Step with a null scope ID
• Scenario: Step with a null scope ID.Scenario: Step with a null scope ID
• Scenario: Step with a null scope ID.Scenario: Step with a null scope ID
• Scenario: Step with a null scope ID.Scenario: Step with a null scope ID
• Scenario: Step with a null scope ID.Scenario: Step with a null scope ID
• Scenario: Change an existing step name.Scenario: Change an existing step name
• Scenario: Change an existing step name.Scenario: Change an existing step name
• Scenario: Change an existing step name.Scenario: Change an existing step name
• Scenario: Change an existing step name.Scenario: Change an existing step name
• Scenario: Change an existing step name.Scenario: Change an existing step name
• Scenario: Count steps in the database.Scenario: Count steps in the database
• Scenario: Count steps in the database.Scenario: Count steps in the database
• Scenario: Count steps in the database.Scenario: Count steps in the database
• Scenario: Count steps in the database.Scenario: Count steps in the database
• Scenario: Count steps in the database.Scenario: Count steps in the database
• Scenario: Delete an existing step.Scenario: Delete an existing step
• Scenario: Delete an existing step.Scenario: Delete an existing step
• Scenario: Delete an existing step.Scenario: Delete an existing step
• Scenario: Delete an existing step.Scenario: Delete an existing step
• Scenario: Delete an existing step.Scenario: Delete an existing step
• Scenario: Delete a non-existing step.Scenario: Delete a non-existing step
• Scenario: Delete a non-existing step.Scenario: Delete a non-existing step
• Scenario: Delete a non-existing step.Scenario: Delete a non-existing step
• Scenario: Delete a non-existing step.Scenario: Delete a non-existing step
• Scenario: Delete a non-existing step.Scenario: Delete a non-existing step
• Scenario: Step factory sanity checks.Scenario: Step factory sanity checks
• Scenario: Step factory sanity checks.Scenario: Step factory sanity checks
• Scenario: Step factory sanity checks.Scenario: Step factory sanity checks
• Scenario: Step factory sanity checks.Scenario: Step factory sanity checks
• Scenario: Step factory sanity checks.Scenario: Step factory sanity checks
• Scenario: Regular target creation.Scenario: Regular target creation
• Scenario: Regular target creation.Scenario: Regular target creation
• Scenario: Regular target creation.Scenario: Regular target creation
• Scenario: Regular target creation.Scenario: Regular target creation
• Scenario: Regular target creation.Scenario: Regular target creation
• Scenario: Target with a null scope ID.Scenario: Target with a null scope ID
• Scenario: Target with a null scope ID.Scenario: Target with a null scope ID
• Scenario: Target with a null scope ID.Scenario: Target with a null scope ID
• Scenario: Target with a null scope ID.Scenario: Target with a null scope ID
• Scenario: Target with a null scope ID.Scenario: Target with a null scope ID
• Scenario: Delete a job target.Scenario: Delete a job target
• Scenario: Delete a job target.Scenario: Delete a job target
• Scenario: Delete a job target.Scenario: Delete a job target
• Scenario: Delete a job target.Scenario: Delete a job target
• Scenario: Delete a job target.Scenario: Delete a job target
• Scenario: Delete a job target twice.Scenario: Delete a job target twice
• Scenario: Delete a job target twice.Scenario: Delete a job target twice
• Scenario: Delete a job target twice.Scenario: Delete a job target twice
• Scenario: Delete a job target twice.Scenario: Delete a job target twice
• Scenario: Delete a job target twice.Scenario: Delete a job target twice
• Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets
• Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets
• Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets
• Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets
• Scenario: Create and count multiple job targets.Scenario: Create and count multiple job targets
• Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job
• Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job
• Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job
• Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job
• Scenario: Query for the targets of a specific job.Scenario: Query for the targets of a specific job
• Scenario: Update a job target TargetId.Scenario: Update a job target TargetId
• Scenario: Update a job target TargetId.Scenario: Update a job target TargetId
• Scenario: Update a job target TargetId.Scenario: Update a job target TargetId
• Scenario: Update a job target TargetId.Scenario: Update a job target TargetId
• Scenario: Update a job target TargetId.Scenario: Update a job target TargetId
• Scenario: Update a job target step index.Scenario: Update a job target step index
• Scenario: Update a job target step index.Scenario: Update a job target step index
• Scenario: Update a job target step index.Scenario: Update a job target step index
• Scenario: Update a job target step index.Scenario: Update a job target step index
• Scenario: Update a job target step index.Scenario: Update a job target step index
• Scenario: Update a job target status.Scenario: Update a job target status
• Scenario: Update a job target status.Scenario: Update a job target status
• Scenario: Update a job target status.Scenario: Update a job target status
• Scenario: Update a job target status.Scenario: Update a job target status
• Scenario: Update a job target status.Scenario: Update a job target status
• Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks
• Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks
• Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks
• Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks
• Scenario: Job target factory sanity checks.Scenario: Job target factory sanity checks
• org.eclipse.kapua.service.liquibase.KapuaLiquibaseClientTest.shouldCreateAttempToUseCustomSchema
• org.eclipse.kapua.service.liquibase.KapuaLiquibaseClientTest.shouldCreateTableOnlyOnce
• org.eclipse.kapua.service.liquibase.KapuaLiquibaseClientTest.shouldCreateTable
• org.eclipse.kapua.service.authorization.shiro.AccessInfoServiceTest.testFind
• org.eclipse.kapua.service.authorization.shiro.AccessInfoServiceTest.testSimpleCreate
• org.eclipse.kapua.service.authorization.shiro.AccessInfoServiceTest.testPermissionCreate
• org.eclipse.kapua.service.authorization.shiro.AccessInfoServiceTest.testRoleCreate
• org.eclipse.kapua.service.authorization.shiro.AccessInfoServiceTest.testDelete
• org.eclipse.kapua.service.authorization.shiro.DomainRegistryServiceTest.testQueryAndCount
• org.eclipse.kapua.service.authorization.shiro.DomainRegistryServiceTest.testFind
• org.eclipse.kapua.service.authorization.shiro.DomainRegistryServiceTest.testCreate
• org.eclipse.kapua.service.authorization.shiro.DomainRegistryServiceTest.testDelete
• org.eclipse.kapua.service.authorization.shiro.GroupServiceTest.testQueryAndCount
• org.eclipse.kapua.service.authorization.shiro.GroupServiceTest.testFind
• org.eclipse.kapua.service.authorization.shiro.GroupServiceTest.testDelete
• org.eclipse.kapua.service.authorization.shiro.RoleServiceTest.testQueryAndCount
• org.eclipse.kapua.service.authorization.shiro.RoleServiceTest.testFind
• org.eclipse.kapua.service.authorization.shiro.RoleServiceTest.testCreate
• org.eclipse.kapua.service.authorization.shiro.RoleServiceTest.testDelete
• org.eclipse.kapua.service.authorization.shiro.RoleServiceTest.testUpdate
• Scenario: Simple create.Scenario: Simple create
• Scenario: Simple create.Scenario: Simple create
• Scenario: Simple create.Scenario: Simple create
• Scenario: Simple create.Scenario: Simple create
• Scenario: Simple create.Scenario: Simple create
• Scenario: Create with permissions.Scenario: Create with permissions
• Scenario: Delete an access info entity twice.Scenario: Delete an access info entity twice
• Scenario: Count access info entities in a specific scope.Scenario: Count access info entities in a specific scope
• Scenario: Count access info entities in a specific scope.Scenario: Count access info entities in a specific scope
• Scenario: Count access info entities in a specific scope.Scenario: Count access info entities in a specific scope
• Scenario: Count access info entities in a specific scope.Scenario: Count access info entities in a specific scope
• Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user
• Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user
• Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user
• Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user
• Scenario: Query for all the access info entities of a specific user.Scenario: Query for all the access info entities of a specific user
• Scenario: Query for all the access info entities of an invalid user.Scenario: Query for all the access info entities of an invalid user
• Scenario: Query for all the access info entities of an invalid user.Scenario: Query for all the access info entities of an invalid user
• Scenario: Query for all the access info entities of an invalid user.Scenario: Query for all the access info entities of an invalid user
• Scenario: Query for all the access info entities of an invalid user.Scenario: Query for all the access info entities of an invalid user
• Scenario: Create regular access permissions.Scenario: Create regular access permissions
• Scenario: Create regular access permissions.Scenario: Create regular access permissions
• Scenario: Create regular access permissions.Scenario: Create regular access permissions
• Scenario: Create regular access permissions.Scenario: Create regular access permissions
• Scenario: Find last created permision.Scenario: Find last created permision
• Scenario: Find last created permision.Scenario: Find last created permision
• Scenario: Find last created permision.Scenario: Find last created permision
• Scenario: Find last created permision.Scenario: Find last created permision
• Scenario: Find last created permision.Scenario: Find last created permision
• Scenario: Delete an existing access permission entity.Scenario: Delete an existing access permission entity
• Scenario: Delete an existing access permission entity.Scenario: Delete an existing access permission entity
• Scenario: Delete an existing access permission entity.Scenario: Delete an existing access permission entity
• Scenario: Delete an existing access permission entity.Scenario: Delete an existing access permission entity
• Scenario: Delete a non existing permission entity.Scenario: Delete a non existing permission entity
• Scenario: Delete a non existing permission entity.Scenario: Delete a non existing permission entity
• Scenario: Delete a non existing permission entity.Scenario: Delete a non existing permission entity
• Scenario: Delete a non existing permission entity.Scenario: Delete a non existing permission entity
• Scenario: Regular creation of Access Role entity.Scenario: Regular creation of Access Role entity
• Scenario: Regular creation of Access Role entity.Scenario: Regular creation of Access Role entity
• Scenario: Regular creation of Access Role entity.Scenario: Regular creation of Access Role entity
• Scenario: Regular creation of Access Role entity.Scenario: Regular creation of Access Role entity
• Scenario: Creation of access role without an acess info entity.Scenario: Creation of access role without an acess info entity
• Scenario: Creation of access role without an acess info entity.Scenario: Creation of access role without an acess info entity
• Scenario: Creation of access role without an acess info entity.Scenario: Creation of access role without an acess info entity
• Scenario: Creation of access role without an acess info entity.Scenario: Creation of access role without an acess info entity
• Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities
• Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities
• Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities
• Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities
• Scenario: Creation of access role with neither acess info and role entities.Scenario: Creation of access role with neither acess info and role entities
• Scenario: Find an existing access role entity.Scenario: Find an existing access role entity
• Scenario: Find an existing access role entity.Scenario: Find an existing access role entity
• Scenario: Find an existing access role entity.Scenario: Find an existing access role entity
• Scenario: Find an existing access role entity.Scenario: Find an existing access role entity
• Scenario: Find an existing access role entity.Scenario: Find an existing access role entity
• Scenario: Count access role entities by scope.Scenario: Count access role entities by scope
• Scenario: Count access role entities by scope.Scenario: Count access role entities by scope
• Scenario: Count access role entities by scope.Scenario: Count access role entities by scope
• Scenario: Count access role entities by scope.Scenario: Count access role entities by scope
• Scenario: Delete an existing access role entry.Scenario: Delete an existing access role entry
• Scenario: Delete an existing access role entry.Scenario: Delete an existing access role entry
• Scenario: Delete an existing access role entry.Scenario: Delete an existing access role entry
• Scenario: Delete an existing role twice.Scenario: Delete an existing role twice
• Scenario: Delete an existing role twice.Scenario: Delete an existing role twice
• Scenario: Delete an existing role twice.Scenario: Delete an existing role twice
• Scenario: Delete an existing role twice.Scenario: Delete an existing role twice
• Scenario: Access info service sanity checks.Scenario: Access info service sanity checks
• Scenario: Access info service sanity checks.Scenario: Access info service sanity checks
• Scenario: Access info service sanity checks.Scenario: Access info service sanity checks
• Scenario: Access info service sanity checks.Scenario: Access info service sanity checks
• Scenario: Access service comparison sanity checks.Scenario: Access service comparison sanity checks
• Scenario: Access service comparison sanity checks.Scenario: Access service comparison sanity checks
• Scenario: Access service comparison sanity checks.Scenario: Access service comparison sanity checks
• Scenario: Access service comparison sanity checks.Scenario: Access service comparison sanity checks
• Scenario: Create with permissions and a role in the wrong scope.Scenario: Create with permissions and a role in the wrong scope
• Scenario: Create with permissions and a role in the wrong scope.Scenario: Create with permissions and a role in the wrong scope
• Scenario: Create with permissions and a role in the wrong scope.Scenario: Create with permissions and a role in the wrong scope
• Scenario: Create with permissions and a role in the wrong scope.Scenario: Create with permissions and a role in the wrong scope
• Scenario: Count domains in a blank database.Scenario: Count domains in a blank database
• Scenario: Count domains in a blank database.Scenario: Count domains in a blank database
• Scenario: Count domains in a blank database.Scenario: Count domains in a blank database
• Scenario: Count domains in a blank database.Scenario: Count domains in a blank database
• Scenario: Regular domain.Scenario: Regular domain
• Scenario: Regular domain.Scenario: Regular domain
• Scenario: Regular domain.Scenario: Regular domain
• Scenario: Regular domain.Scenario: Regular domain
• Scenario: Domain with null name.Scenario: Domain with null name
• Scenario: Domain with null name.Scenario: Domain with null name
• Scenario: Domain with null name.Scenario: Domain with null name
• Scenario: Domain with null name.Scenario: Domain with null name
• Scenario: Domain with null name.Scenario: Domain with null name
• Scenario: Domain with null actions.Scenario: Domain with null actions
• Scenario: Domain with null actions.Scenario: Domain with null actions
• Scenario: Domain with null actions.Scenario: Domain with null actions
• Scenario: Domain with null actions.Scenario: Domain with null actions
• Scenario: Domains with duplicate names.Scenario: Domains with duplicate names
• Scenario: Domains with duplicate names.Scenario: Domains with duplicate names
• Scenario: Domains with duplicate names.Scenario: Domains with duplicate names
• Scenario: Domains with duplicate names.Scenario: Domains with duplicate names
• Scenario: Find the last created domain entry.Scenario: Find the last created domain entry
• Scenario: Find the last created domain entry.Scenario: Find the last created domain entry
• Scenario: Find the last created domain entry.Scenario: Find the last created domain entry
• Scenario: Find the last created domain entry.Scenario: Find the last created domain entry
• Scenario: Compare domain entries.Scenario: Compare domain entries
• Scenario: Compare domain entries.Scenario: Compare domain entries
• Scenario: Compare domain entries.Scenario: Compare domain entries
• Scenario: Compare domain entries.Scenario: Compare domain entries
• Scenario: Compare domain entries.Scenario: Compare domain entries
• Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry
• Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry
• Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry
• Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry
• Scenario: Delete the last created domain entry.Scenario: Delete the last created domain entry
• Scenario: Delete a nonexistent domain.Scenario: Delete a nonexistent domain
• Scenario: Delete a nonexistent domain.Scenario: Delete a nonexistent domain
• Scenario: Delete a nonexistent domain.Scenario: Delete a nonexistent domain
• Scenario: Count domains in the database.Scenario: Count domains in the database
• Scenario: Count domains in the database.Scenario: Count domains in the database
• Scenario: Count domains in the database.Scenario: Count domains in the database
• Scenario: Count domains in the database.Scenario: Count domains in the database
• Scenario: Domain entry query.Scenario: Domain entry query
• Scenario: Domain entry query.Scenario: Domain entry query
• Scenario: Domain entry query.Scenario: Domain entry query
• Scenario: Count groups in a blank database.Scenario: Count groups in a blank database
• Scenario: Count groups in a blank database.Scenario: Count groups in a blank database
• Scenario: Count groups in a blank database.Scenario: Count groups in a blank database
• Scenario: Count groups in a blank database.Scenario: Count groups in a blank database
• Scenario: Regular group in root scope.Scenario: Regular group in root scope
• Scenario: Regular group in root scope.Scenario: Regular group in root scope
• Scenario: Regular group in root scope.Scenario: Regular group in root scope
• Scenario: Regular group in root scope.Scenario: Regular group in root scope
• Scenario: Regular group in random scope.Scenario: Regular group in random scope
• Scenario: Regular group in random scope.Scenario: Regular group in random scope
• Scenario: Regular group in random scope.Scenario: Regular group in random scope
• Scenario: Regular group in random scope.Scenario: Regular group in random scope
• Scenario: Regular group in random scope.Scenario: Regular group in random scope
• Scenario: Duplicate group name in root scope.Scenario: Duplicate group name in root scope
• Scenario: Duplicate group name in root scope.Scenario: Duplicate group name in root scope
• Scenario: Duplicate group name in root scope.Scenario: Duplicate group name in root scope
• Scenario: Duplicate group name in root scope.Scenario: Duplicate group name in root scope
• Scenario: Group with a null name.Scenario: Group with a null name
• Scenario: Group with a null name.Scenario: Group with a null name
• Scenario: Group with a null name.Scenario: Group with a null name
• Scenario: Group with a null name.Scenario: Group with a null name
• Scenario: Update a group entry in the database.Scenario: Update a group entry in the database
• Scenario: Update a group entry in the database.Scenario: Update a group entry in the database
• Scenario: Update a group entry in the database.Scenario: Update a group entry in the database
• Scenario: Update a group entry in the database.Scenario: Update a group entry in the database
• Scenario: Update a group entry with a false ID.Scenario: Update a group entry with a false ID
• Scenario: Update a group entry with a false ID.Scenario: Update a group entry with a false ID
• Scenario: Update a group entry with a false ID.Scenario: Update a group entry with a false ID
• Scenario: Update a group entry with a false ID.Scenario: Update a group entry with a false ID
• Scenario: Find a group entry in the database.Scenario: Find a group entry in the database
• Scenario: Find a group entry in the database.Scenario: Find a group entry in the database
• Scenario: Find a group entry in the database.Scenario: Find a group entry in the database
• Scenario: Find a group entry in the database.Scenario: Find a group entry in the database
• Scenario: Delete a group from the database.Scenario: Delete a group from the database
• Scenario: Delete a group from the database.Scenario: Delete a group from the database
• Scenario: Delete a group from the database.Scenario: Delete a group from the database
• Scenario: Delete a group from the database - Unknown group ID.Scenario: Delete a group from the database - Unknown group ID
• Scenario: Delete a group from the database - Unknown group ID.Scenario: Delete a group from the database - Unknown group ID
• Scenario: Delete a group from the database - Unknown group ID.Scenario: Delete a group from the database - Unknown group ID
• Scenario: Count groups.Scenario: Count groups
• Scenario: Count groups.Scenario: Count groups
• Scenario: Count groups.Scenario: Count groups
• Scenario: Count groups.Scenario: Count groups
• Scenario: Query for a specific group by name.Scenario: Query for a specific group by name
• Scenario: Query for a specific group by name.Scenario: Query for a specific group by name
• Scenario: Query for a specific group by name.Scenario: Query for a specific group by name
• Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks
• Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks
• Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks
• Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks
• Scenario: Permission factory sanity checks.Scenario: Permission factory sanity checks
• Scenario: Regular role creation.Scenario: Regular role creation
• Scenario: Regular role creation.Scenario: Regular role creation
• Scenario: Regular role creation.Scenario: Regular role creation
• Scenario: Regular role creation.Scenario: Regular role creation
• Scenario: Nameless role entry.Scenario: Nameless role entry
• Scenario: Nameless role entry.Scenario: Nameless role entry
• Scenario: Nameless role entry.Scenario: Nameless role entry
• Scenario: Nameless role entry.Scenario: Nameless role entry
• Scenario: Nameless role entry.Scenario: Nameless role entry
• Scenario: Duplicate role names.Scenario: Duplicate role names
• Scenario: Duplicate role names.Scenario: Duplicate role names
• Scenario: Duplicate role names.Scenario: Duplicate role names
• Scenario: Duplicate role names.Scenario: Duplicate role names
• Scenario: Role entry with no actions.Scenario: Role entry with no actions
• Scenario: Role entry with no actions.Scenario: Role entry with no actions
• Scenario: Role entry with no actions.Scenario: Role entry with no actions
• Scenario: Find role by ID.Scenario: Find role by ID
• Scenario: Find role by ID.Scenario: Find role by ID
• Scenario: Find role by ID.Scenario: Find role by ID
• Scenario: Find role by ID.Scenario: Find role by ID
• Scenario: Search the role database for a random ID.Scenario: Search the role database for a random ID
• Scenario: Search the role database for a random ID.Scenario: Search the role database for a random ID
• Scenario: Search the role database for a random ID.Scenario: Search the role database for a random ID
• Scenario: Search the role database for a random ID.Scenario: Search the role database for a random ID
• Scenario: Delete an existing role.Scenario: Delete an existing role
• Scenario: Delete an existing role.Scenario: Delete an existing role
• Scenario: Delete an existing role.Scenario: Delete an existing role
• Scenario: Delete an existing role.Scenario: Delete an existing role
• Scenario: Delete an existing role.Scenario: Delete an existing role
• Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry
• Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry
• Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry
• Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry
• Scenario: Delete a non existing role entry.Scenario: Delete a non existing role entry
• Scenario: Update existing role name.Scenario: Update existing role name
• Scenario: Update existing role name.Scenario: Update existing role name
• Scenario: Update existing role name.Scenario: Update existing role name
• Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted
• Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted
• Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted
• Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted
• Scenario: Modify a role that was deleted.Scenario: Modify a role that was deleted
• Scenario: Count roles in specific scopes.Scenario: Count roles in specific scopes
• Scenario: Count roles in specific scopes.Scenario: Count roles in specific scopes
• Scenario: Count roles in specific scopes.Scenario: Count roles in specific scopes
• Scenario: Count roles in specific scopes.Scenario: Count roles in specific scopes
• Scenario: A fresh database must contain 1 default role in the root scope.Scenario: A fresh database must contain 1 default role in the root scope
• Scenario: Delete role permissions.Scenario: Delete role permissions
• Scenario: Count role permissions in specific scopes.Scenario: Count role permissions in specific scopes
• Scenario: Count role permissions in specific scopes.Scenario: Count role permissions in specific scopes
• Scenario: Count role permissions in specific scopes.Scenario: Count role permissions in specific scopes
• Scenario: Creating user.Scenario: Creating user
• Scenario: Create user with short name.Scenario: Create user with short name
• Scenario: Create user that has more than DB allowed length.Scenario: Create user that has more than DB allowed length
• Scenario: Create user with special characters in his name.Scenario: Create user with special characters in his name
• Scenario: Update user.Scenario: Update user
• Scenario: Delete user.Scenario: Delete user
• Scenario: Query user.Scenario: Query user
• Scenario: Count user.Scenario: Count user
• Scenario: Find user by id.Scenario: Find user by id
• Scenario: Find user by name.Scenario: Find user by name
• Scenario: Create user that already exist.Scenario: Create user that already exist
• Scenario: Update user that doesn't exist.Scenario: Update user that doesn't exist
• Scenario: Delete user that doesn't exist.Scenario: Delete user that doesn't exist
• Scenario: Find user with id and scope id that doesn't exist.Scenario: Find user with id and scope id that doesn't exist
• Scenario: Find user by name that doesn't exist.Scenario: Find user by name that doesn't exist
• Scenario: Delete Kapua system user.Scenario: Delete Kapua system user
• Scenario: Create multiple users.Scenario: Create multiple users
• Scenario: Find multiple users.Scenario: Find multiple users
• Scenario: Get metadata.Scenario: Get metadata