[Jenkins]Jenkins

Test Result : (root)

0 failures , 15 skipped
4,824 tests
Took 4.5 sec.

All Tests

ClassDurationFail(diff)Skip(diff)Pass(diff)Total(diff)
Scenario: A fresh database must contain 1 default role in the root scope0 ms003+33+3
Scenario: A mock test scenario0.49 sec003+33+3
Scenario: A newly created account must have some metadata3 ms003+33+3
Scenario: A1 User with admin rights publishes arbitrary message to arbitrary topic10 ms008+88+8
Scenario: Access info service sanity checks0 ms004+44+4
Scenario: Access service comparison sanity checks0 ms003+33+3
Scenario: Account based ClientInfo data check7 ms0012+1212+12
Scenario: Account exactly on its expiration date5 ms0014+1414+14
Scenario: Account expiration date test - Parent and child expiration set, then parent expiration date changed to before child expiration date2 ms006+66+6
Scenario: Account expiration date test - Parent expiration set, child expiration after father expiration3 ms006+66+6
Scenario: Account expiration date test - Parent expiration set, child expiration before father expiration2 ms005+55+5
Scenario: Account expiration date test - Parent expiration set, child expiration null3 ms006+66+6
Scenario: Account name must not be mutable2 ms006+66+6
Scenario: Account past its expiration date4 ms0014+1414+14
Scenario: Account wide metrics check8 ms0014+1414+14
Scenario: Account with future expiration date4 ms0013+1313+13
Scenario: Account with no expiration date3 ms0013+1313+13
Scenario: All device parameters must match the device creator15 ms003+33+3
Scenario: B1 Broker publish to CTRL_ACC_REPLY9 ms009+99+9
Scenario: B10 Broker create sub-topic on ACL_DATA_ACC is not allowed9 ms009+99+9
Scenario: B11 Broker subscribe on ACL_DATA_ACC is not allowed7 ms008+88+8
Scenario: B12 Broker subscribe - publish - admin on ACL_DATA_ACC_CLI6 ms009+99+9
Scenario: B13 Broker publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms009+99+9
Scenario: B15 Broker subscribe on ACL_CTRL_ACC_NOTIFY is not allowed5 ms008+88+8
Scenario: B2 Broker create sub-topic on CTRL_ACC_REPLY10 ms009+99+9
Scenario: B3 Broker subscribe on personal CTRL_ACC_REPLY5 ms009+99+9
Scenario: B4 Broker subscribe on CTRL_ACC_REPLY of another account7 ms009+99+9
Scenario: B5 Broker publish to CTRL_ACC is not allowed11 ms009+99+9
Scenario: B6 Broker create sub-topic on CTRL_ACC is not allowed12 ms009+99+9
Scenario: B7 Broker subscribe on CTRL_ACC is not allowed3 ms008+88+8
Scenario: B8 Broker subscribe - publish - admin on CTRL_ACC_CLI10 ms009+99+9
Scenario: B9 Broker publish to ACL_DATA_ACC is not allowed11 ms009+99+9
Scenario: Basic Device Event queries9 ms0014+1414+14
Scenario: Birth and applications event handling5 ms0012+1212+12
Scenario: Birth and death message handling5 ms0012+1212+12
Scenario: Birth and missing event handling3 ms0012+1212+12
Scenario: Birth message handling from a new device5 ms0013+1313+13
Scenario: Birth message handling from an existing device10 ms0012+1212+12
Scenario: Both the parent and child accounts do not expire4 ms0011+1111+11
Scenario: Both the parent and child accounts have the same expiration date2 ms0011+1111+11
Scenario: Captured date based ClientInfo data check11 ms0015+1515+15
Scenario: Case sensitivness of named device searches10 ms003+33+3
Scenario: Change an existing step name13 ms008+88+8
Scenario: Change the account parent Id2 ms005+55+5
Scenario: Change the account parent path4 ms005+55+5
Scenario: Channel info queries based on datastore channel filters19 ms0025+2525+25
Scenario: ChannelInfo client ID and topic data based on the client id20 ms0014+1414+14
Scenario: ChannelInfo client ID based on the account id8 ms0013+1313+13
Scenario: ChannelInfo last published date11 ms0015+1515+15
Scenario: ChannelInfo topic data based on the account id7 ms0013+1313+13
Scenario: Check account properties4 ms004+44+4
Scenario: Check the Device Connection Domain data seetting5 ms002+22+2
Scenario: Check the database cache coherency6 ms0015+1515+15
Scenario: Check the mapping for message semantic topics10 ms0015+1515+15
Scenario: Check the message store7 ms0010+1010+10
Scenario: Check the sanity of the Device Connection Domain data initialization7 ms002+22+2
Scenario: Child account expires after parent5 ms009+99+9
Scenario: Child account expires before parent7 ms0011+1111+11
Scenario: Child account has null expiration date8 ms009+99+9
Scenario: Client Id based ClientInfo data check17 ms0014+1414+14
Scenario: Compare domain entries0 ms002+22+2
Scenario: Connect to the system and publish some data7 ms0022+2222+22
Scenario: Connection Service factory sanity checks6 ms002+22+2
Scenario: Count access info entities in a specific scope1 ms0019+1919+19
Scenario: Count access role entities by scope3 ms0033+3333+33
Scenario: Count connections in empty scope7 ms004+44+4
Scenario: Count connections in scope6 ms005+55+5
Scenario: Count devices in a specific scope7 ms0011+1111+11
Scenario: Count devices with a specific BIOS version5 ms006+66+6
Scenario: Count domains in a blank database1 ms003+33+3
Scenario: Count domains in the database0 ms006+66+6
Scenario: Count events in empty scope7 ms0010+1010+10
Scenario: Count events in scope11 ms0014+1414+14
Scenario: Count groups0 ms0012+1212+12
Scenario: Count groups in a blank database0 ms003+33+3
Scenario: Count job items10 ms004+44+4
Scenario: Count job items in wrong (empty) scope14 ms001+11+1
Scenario: Count role permissions in specific scopes1 ms0015+1515+15
Scenario: Count roles in specific scopes1 ms0013+1313+13
Scenario: Count step definition items13 ms004+44+4
Scenario: Count step definitions in wrong (empty) scope8 ms001+11+1
Scenario: Count steps in the database9 ms0011+1111+11
Scenario: Count user5 ms006+66+6
Scenario: Create a regular event14 ms0010+1010+10
Scenario: Create a single device11 ms004+44+4
Scenario: Create an event with a null action12 ms0011+1111+11
Scenario: Create an event with a null scope ID11 ms0010+1010+10
Scenario: Create and count multiple job targets10 ms008+88+8
Scenario: Create and count several execution items for a job13 ms009+99+9
Scenario: Create index with specific prefix11 ms0013+1313+13
Scenario: Create multiple users3 ms005+55+5
Scenario: Create regular access permissions1 ms0015+1515+15
Scenario: Create some regular role permissions0 ms006+66+6
Scenario: Create user that already exist5 ms007+77+7
Scenario: Create user that has more than DB allowed length5 ms005+55+5
Scenario: Create user with short name6 ms005+55+5
Scenario: Create user with special characters in his name5 ms005+55+5
Scenario: Create with permissions1 ms0010+1010+10
Scenario: Create with permissions and a role1 ms0013+1313+13
Scenario: Create with permissions and a role in the wrong scope0 ms0010+1010+10
Scenario: Creating index with regular user15 ms0025+2525+25
Scenario: Creating new device and tagging it with specific Tag3 ms0014+1414+14
Scenario: Creating new device, tagging it with specific Tag and then deleting this Tag11 ms0016+1616+16
Scenario: Creating tag3 ms007+77+7
Scenario: Creating two indexes with daily index12 ms0017+1717+17
Scenario: Creating two indexes with hourly index14 ms0017+1717+17
Scenario: Creating two indexes with weekly index10 ms0017+1717+17
Scenario: Creating user87 ms005+55+5
Scenario: Creation of access role with neither acess info and role entities0 ms008+88+8
Scenario: Creation of access role without an acess info entity0 ms008+88+8
Scenario: D1 Device publish to CTRL_ACC_REPLY9 ms009+99+9
Scenario: D10 Device subscribe - publish - admin on ACL_DATA_ACC_CLI8 ms009+99+9
Scenario: D11 Device publish to ACL_CTRL_ACC_NOTIFY is allowed7 ms009+99+9
Scenario: D13 Device subscribe on ACL_CTRL_ACC_NOTIFY is not allowed3 ms007+77+7
Scenario: D2 Device create sub-topic on CTRL_ACC_REPLY11 ms009+99+9
Scenario: D3 Device subscribe on personal CTRL_ACC_REPLY8 ms009+99+9
Scenario: D4 Device subscribe on CTRL_ACC_REPLY of another account6 ms009+99+9
Scenario: D5 Device subscribe - publish - admin on CTRL_ACC4 ms009+99+9
Scenario: D6 Device subscribe - publish - admin on CTRL_ACC_CLI6 ms009+99+9
Scenario: D7 Device publish to ACL_DATA_ACC is not allowed7 ms009+99+9
Scenario: D8 Device create sub-topic on ACL_DATA_ACC is not allowed12 ms009+99+9
Scenario: D9 Device subscribe on ACL_DATA_ACC is not allowed6 ms008+88+8
Scenario: DM1 Data manage publish to CTRL_ACC_REPLY is allowed6 ms009+99+9
Scenario: DM10 Data manage subscribe - publish - admin on ACL_DATA_ACC_CLI2 ms009+99+9
Scenario: DM11 Data manage publish to ACL_CTRL_ACC_NOTIFY is allowed6 ms009+99+9
Scenario: DM13 Data manage subscribe on ACL_CTRL_ACC_NOTIFY is not allowed4 ms008+88+8
Scenario: DM2 Data manage create sub-topic on CTRL_ACC_REPLY7 ms009+99+9
Scenario: DM3 Data manage subscribe on personal CTRL_ACC_REPLY4 ms009+99+9
Scenario: DM4 Data manage subscribe on CTRL_ACC_REPLY of another account3 ms009+99+9
Scenario: DM5 Data manage publish to CTRL_ACC is not allowed8 ms009+99+9
Scenario: DM6 Data manage create sub-topic on CTRL_ACC is not allowed10 ms009+99+9
Scenario: DM7 Data manage subscribe on CTRL_ACC is not allowed3 ms008+88+8
Scenario: DM8 Data manage subscribe - publish - admin on CTRL_ACC_CLI5 ms009+99+9
Scenario: DM9 Data manage subscribe - publish - admin on ACL_DATA_ACC4 ms009+99+9
Scenario: DV1 Data view publish to CTRL_ACC_REPLY7 ms009+99+9
Scenario: DV10 Data view create sub-topic on ACL_DATA_ACC is allowed6 ms009+99+9
Scenario: DV11 Data view subscribe on ACL_DATA_ACC is allowed2 ms0010+1010+10
Scenario: DV12 Data view publish to ACL_CTRL_ACC_CLI is allowed14 ms009+99+9
Scenario: DV13 Data view create sub-topic on ACL_CTRL_ACC_CLI is not allowed7 ms009+99+9
Scenario: DV15 Data view publish to ACL_CTRL_ACC_NOTIFY is allowed5 ms009+99+9
Scenario: DV17 Data view subscribe on ACL_CTRL_ACC_NOTIFY is not allowed3 ms008+88+8
Scenario: DV2 Data view create sub-topic on CTRL_ACC_REPLY2 ms009+99+9
Scenario: DV3 Data view subscribe on personal CTRL_ACC_REPLY6 ms009+99+9
Scenario: DV4 Data view subscribe on CTRL_ACC_REPLY of another account3 ms009+99+9
Scenario: DV5 Data view publish to CTRL_ACC is not allowed3 ms009+99+9
Scenario: DV6 Data view create sub-topic on CTRL_ACC is not allowed7 ms009+99+9
Scenario: DV7 Data view subscribe on CTRL_ACC is not allowed3 ms008+88+8
Scenario: DV8 Data view subscribe - publish - admin on CTRL_ACC_CLI3 ms009+99+9
Scenario: DV9 Data view publish to ACL_DATA_ACC is not allowed4 ms009+99+9
Scenario: Delete Kapua system user3 ms005+55+5
Scenario: Delete a access info entity with permissions and roles2 ms009+99+9
Scenario: Delete a connection from the database8 ms007+77+7
Scenario: Delete a group from the database1 ms006+66+6
Scenario: Delete a group from the database - Unknown group ID0 ms004+44+4
Scenario: Delete a job24 ms008+88+8
Scenario: Delete a job execution item15 ms006+66+6
Scenario: Delete a job execution item twice13 ms007+77+7
Scenario: Delete a job target16 ms006+66+6
Scenario: Delete a job target twice10 ms007+77+7
Scenario: Delete a job twice12 ms007+77+7
Scenario: Delete a non existent event9 ms0011+1111+11
Scenario: Delete a non existing connection6 ms006+66+6
Scenario: Delete a non existing permission entity0 ms0012+1212+12
Scenario: Delete a non existing role entry0 ms008+88+8
Scenario: Delete a non-existing step10 ms009+99+9
Scenario: Delete a nonexistent domain0 ms004+44+4
Scenario: Delete a step definition15 ms008+88+8
Scenario: Delete a step definition twice9 ms007+77+7
Scenario: Delete an access info entity twice2 ms008+88+8
Scenario: Delete an access info entity using the wrong scope ID0 ms008+88+8
Scenario: Delete an existing access info entity2 ms009+99+9
Scenario: Delete an existing access permission entity0 ms0011+1111+11
Scenario: Delete an existing access role entry2 ms0018+1818+18
Scenario: Delete an existing account4 ms005+55+5
Scenario: Delete an existing device from the registry7 ms004+44+4
Scenario: Delete an existing event12 ms0013+1313+13
Scenario: Delete an existing role0 ms005+55+5
Scenario: Delete an existing role twice0 ms0011+1111+11
Scenario: Delete an existing step10 ms008+88+8
Scenario: Delete items based on query results13 ms0042+4242+42
Scenario: Delete items by the datastore ID11 ms0033+3333+33
Scenario: Delete middle child expiration3 ms0015+1515+15
Scenario: Delete nonexisting account4 ms004+44+4
Scenario: Delete nonexisting role permission0 ms0010+1010+10
Scenario: Delete parent expiration2 ms0014+1414+14
Scenario: Delete role permissions0 ms007+77+7
Scenario: Delete the Kapua system account4 ms005+55+5
Scenario: Delete the last created domain entry1 ms007+77+7
Scenario: Delete user7 ms006+66+6
Scenario: Delete user that doesn't exist4 ms005+55+5
Scenario: Deleting tag3 ms007+77+7
Scenario: Deleting user in account that is higher in hierarchy5 ms0023+2323+23
Scenario: Deleting user in account that is lower in hierarchy4 ms0024+2424+24
Scenario: Device connection update8 ms006+66+6
Scenario: Device factory sanity checks6 ms002+22+2
Scenario: Device queries8 ms0013+1313+13
Scenario: Device query - find by BIOS version6 ms007+77+7
Scenario: Domain entry query0 ms004+44+4
Scenario: Domain with null actions0 ms004+44+4
Scenario: Domain with null name0 ms004+44+4
Scenario: Domains with duplicate names0 ms007+77+7
Scenario: Duplicate group name in root scope0 ms008+88+8
Scenario: Duplicate role names0 ms004+44+4
Scenario: Empty query results are supported0 ms005+55+5
Scenario: Event factory sanity checks7 ms006+66+6
Scenario: Event service domain check7 ms006+66+6
Scenario: Every account must have the default configuration items2 ms003+33+3
Scenario: Extra long continuous test with multiple subscenarios with LOOSE default connection mode30 ms00418+418418+418
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode33 ms00396+396396+396
Scenario: Extra long continuous test with multiple subscenarios with STRICT default connection mode and no previously defined devices65 ms00304+304304+304
Scenario: Find a connection by its IDs13 ms005+55+5
Scenario: Find a connection by its client ID14 ms005+55+5
Scenario: Find a group entry in the database0 ms007+77+7
Scenario: Find a non existing event10 ms0010+1010+10
Scenario: Find account by Id5 ms004+44+4
Scenario: Find account by Ids8 ms004+44+4
Scenario: Find account by name4 ms004+44+4
Scenario: Find account by random Id4 ms003+33+3
Scenario: Find all child accounts6 ms003+33+3
Scenario: Find an access info entity0 ms008+88+8
Scenario: Find an access info entity by user ID1 ms007+77+7
Scenario: Find an event by its ID7 ms0010+1010+10
Scenario: Find an existing access role entity0 ms009+99+9
Scenario: Find by name nonexisting account3 ms003+33+3
Scenario: Find device by client ID6 ms003+33+3
Scenario: Find device by registry ID9 ms004+44+4
Scenario: Find last created permision1 ms008+88+8
Scenario: Find multiple users3 ms005+55+5
Scenario: Find role by ID0 ms004+44+4
Scenario: Find the last created domain entry0 ms004+44+4
Scenario: Find user by id3 ms005+55+5
Scenario: Find user by name3 ms005+55+5
Scenario: Find user by name that doesn't exist4 ms003+33+3
Scenario: Find user with id and scope id that doesn't exist5 ms003+33+3
Scenario: Generic connection query6 ms007+77+7
Scenario: Get metadata4 ms003+33+3
Scenario: Group with a null name0 ms005+55+5
Scenario: Handle account creation47 ms003+33+3
Scenario: Handle duplicate account names6 ms005+55+5
Scenario: Handle null account name5 ms004+44+4
Scenario: Handling of 2 birth messages5 ms0012+1212+12
Scenario: Handling of a disconnect message from a non existing device5 ms0010+1010+10
Scenario: I try to find a non-existing connection6 ms005+55+5
Scenario: If user credential expiration date is before today, user can not login6 ms0014+1414+14
Scenario: If user credential expiration date is today, user can not login it is day inclusive3 ms0014+1414+14
Scenario: If user credential expiration date is tomorrow, user can login2 ms0013+1313+13
Scenario: If user credential is in state disabled, user can not login3 ms0014+1414+14
Scenario: If user credential is in state enabled, user can login2 ms0013+1313+13
Scenario: If user expiration date is before today, user can not login4 ms0013+1313+13
Scenario: If user expiration date is today, user can not login because expiration date was reached6 ms0013+1313+13
Scenario: If user expiration date is tomorrow, user can login3 ms0012+1212+12
Scenario: Installing a package11 ms0013+1313+13
Scenario: It is possible to change the configuration items4 ms004+44+4
Scenario: It must be possible to query for specific entries in the role database0 ms005+55+5
Scenario: Job execution factory sanity checks14 ms002+22+2
Scenario: Job factory sanity checks20 ms003+33+3
Scenario: Job target factory sanity checks10 ms002+22+2
Scenario: Job with a duplicate name16 ms006+66+6
Scenario: Job with a null name14 ms005+55+5
Scenario: Job with a null scope ID14 ms006+66+6
Scenario: Job with an empty name15 ms006+66+6
Scenario: MetricsInfo client ID and topic data based on the client id9 ms0017+1717+17
Scenario: MetricsInfo last published date8 ms0024+2424+24
Scenario: Modify a role that was deleted0 ms006+66+6
Scenario: Modify an existing account4 ms004+44+4
Scenario: Modify last child expiration so that it still expires before parent2 ms0014+1414+14
Scenario: Modify middle child expiration so that it still expires before parent3 ms0014+1414+14
Scenario: Modify middle child expiration to outlive parent4 ms0015+1515+15
Scenario: Modify nonexisting account3 ms006+66+6
Scenario: Modify parent expiration so that it still expires after child4 ms0014+1414+14
Scenario: Modify parent expiration to before child expiration1 ms0015+1515+15
Scenario: Nameless role entry0 ms004+44+4
Scenario: Negative scenario when client connects twice with same client id8 ms0011+1111+11
Scenario: New connection with reserved ID9 ms0033+3333+33
Scenario: Permission factory sanity checks0 ms003+33+3
Scenario: Positive scenario without stealing link27 ms0012+1212+12
Scenario: Query based on message ordering8 ms0010+1010+10
Scenario: Query based on metrics ordering5 ms0010+1010+10
Scenario: Query before schema search6 ms0041+4141+41
Scenario: Query for a specific group by name0 ms0014+1414+14
Scenario: Query for all the access info entities of a specific user1 ms0015+1515+15
Scenario: Query for all the access info entities of an invalid user2 ms007+77+7
Scenario: Query for executions of a specific job12 ms0016+1616+16
Scenario: Query for jobs with specified name8 ms006+66+6
Scenario: Query for step definitions12 ms007+77+7
Scenario: Query for the targets of a specific job9 ms0019+1919+19
Scenario: Query user5 ms006+66+6
Scenario: Regular connection6 ms006+66+6
Scenario: Regular creation of Access Role entity0 ms0010+1010+10
Scenario: Regular domain0 ms004+44+4
Scenario: Regular group in random scope0 ms005+55+5
Scenario: Regular group in root scope1 ms005+55+5
Scenario: Regular job creation17 ms007+77+7
Scenario: Regular job execution creation36 ms005+55+5
Scenario: Regular role creation0 ms006+66+6
Scenario: Regular step creation14 ms008+88+8
Scenario: Regular step definition creation11 ms007+77+7
Scenario: Regular step definition with a property list12 ms004+44+4
Scenario: Regular target creation11 ms005+55+5
Scenario: Role creator sanity checks0 ms002+22+2
Scenario: Role entry with no actions0 ms004+44+4
Scenario: Role object equality check0 ms002+22+2
Scenario: Role service related objects sanity checks0 ms004+44+4
Scenario: Search for a non existent client ID10 ms005+55+5
Scenario: Search for an access info entity by an incorrect user ID0 ms008+88+8
Scenario: Search the role database for a random ID0 ms004+44+4
Scenario: Send BIRTH message and then DC message11 ms0015+1515+15
Scenario: Send BIRTH message and then DC message while broker ip is NOT set17 ms006+66+6
Scenario: Send BIRTH message and then DC message while broker ip is set by System75 ms008+88+8
Scenario: Send BIRTH message and then DC message while broker ip is set by config file23 ms008+88+8
Scenario: Set environment variables0.12 sec0043+4343+43
Scenario: Setting configuration without mandatory items must raise an error3 ms005+55+5
Scenario: Simple create0 ms007+77+7
Scenario: Simple positive scenario for creating daily index13 ms0014+1414+14
Scenario: Simple positive scenario for creating default - weekly index18 ms0012+1212+12
Scenario: Simple positive scenario for creating hourly index15 ms0014+1414+14
Scenario: Start broker for all scenarios0.16 sec0032+3232+32
Scenario: Start datastore for all scenarios0.33 sec0030+3030+30
Scenario: Start event broker for all scenarios0.15 sec0036+3636+36
Scenario: Starting and stopping the simulator should create a device entry and properly set its status11 ms0020+2020+20
Scenario: Stealing link scenario15 ms0028+2828+28
Scenario: Step definition factory sanity checks12 ms002+22+2
Scenario: Step definition with a duplicate name6 ms006+66+6
Scenario: Step definition with a null name13 ms006+66+6
Scenario: Step definition with a null scope ID10 ms006+66+6
Scenario: Step definition with an empty name7 ms005+55+5
Scenario: Step factory sanity checks8 ms002+22+2
Scenario: Step with a null scope ID18 ms008+88+8
Scenario: Stop broker after all scenarios0.1 sec0032+3232+32
Scenario: Stop datastore after all scenarios99 ms0030+3030+30
Scenario: Stop event broker for all scenarios0.15 sec0036+3636+36
Scenario: Target with a null scope ID8 ms005+55+5
Scenario: Test LOOSE user coupling on single connection10 ms0027+2727+27
Scenario: Test LOOSE user coupling with 3 connections18 ms0037+3737+37
Scenario: Test STRICT user coupling on single connection18 ms0024+2424+24
Scenario: Test STRICT user coupling with 3 connections and a reserved user17 ms0062+6262+62
Scenario: Test STRICT user coupling with user change allowed on single connection13 ms0035+3535+35
Scenario: Test account query3 ms004+44+4
Scenario: Test the message store with server timestamp indexing8 ms0013+1313+13
Scenario: Test the message store with timestamp indexing7 ms0013+1313+13
Scenario: The Client ID is case sensitive10 ms007+77+7
Scenario: To be defined16 ms015+151+116+16
Scenario: Try to change an existing connection ID7 ms006+66+6
Scenario: Try to create an access into entity with an invalid role id0 ms008+88+8
Scenario: Try to delete a non existing device from the registry6 ms004+44+4
Scenario: Try to find a device with an invalid client ID6 ms003+33+3
Scenario: Try to find a device with an invalid registry ID7 ms003+33+3
Scenario: Try to modify the connection client ID6 ms006+66+6
Scenario: Try to update the device client ID9 ms004+44+4
Scenario: Unknown configuiration items are silently ignored4 ms004+44+4
Scenario: Update a group entry in the database2 ms007+77+7
Scenario: Update a group entry with a false ID0 ms008+88+8
Scenario: Update a job XML definition10 ms007+77+7
Scenario: Update a job description11 ms007+77+7
Scenario: Update a job name10 ms007+77+7
Scenario: Update a job target TargetId13 ms006+66+6
Scenario: Update a job target status14 ms007+77+7
Scenario: Update a job target step index11 ms005+55+5
Scenario: Update a non existing device5 ms005+55+5
Scenario: Update a nonexistent job16 ms007+77+7
Scenario: Update a nonexistent step definition17 ms007+77+7
Scenario: Update a step definition name17 ms007+77+7
Scenario: Update a step definition processor name19 ms008+88+8
Scenario: Update a step definition target type12 ms008+88+8
Scenario: Update an existing device9 ms004+44+4
Scenario: Update existing role name0 ms005+55+5
Scenario: Update job id of an existing execution item23 ms006+66+6
Scenario: Update the end time of an existing execution item19 ms007+77+7
Scenario: Update user24 ms007+77+7
Scenario: Update user that doesn't exist4 ms005+55+5
Scenario: User locking itself out by using out login attempts3 ms0016+1616+16
Scenario: User locking itself out with failed attempts and not waiting to unlock6 ms0017+1717+17
Scenario: User locking itself out with failed attempts and waiting to unlock3 ms0017+1717+17
Scenario: User login with wrong pass, but with enough time between login failures5 ms0019+1919+19
Scenario: User not locking itself out by using less than max failed login attempts3 ms0017+1717+17
Scenario: Validate a device client based search with a null client ID6 ms004+44+4
Scenario: Validate a device client based search with an empty client ID6 ms004+44+4
Scenario: Validate a device client search with null scope12 ms004+44+4
Scenario: Validate a device count with a null Scope ID7 ms005+55+5
Scenario: Validate a device creator with a null client ID9 ms006+66+6
Scenario: Validate a device creator with a null scope ID6 ms006+66+6
Scenario: Validate a device query with a null Scope ID6 ms005+55+5
Scenario: Validate a device search with a null device ID10 ms004+44+4
Scenario: Validate a device search with a null scope ID12 ms004+44+4
Scenario: Validate a null creator8 ms005+55+5
Scenario: Validate a null device6 ms005+55+5
Scenario: Validate a null device count7 ms005+55+5
Scenario: Validate a null device query9 ms005+55+5
Scenario: Validate a regular creator6 ms004+44+4
Scenario: Validate a regular device5 ms004+44+4
Scenario: Validate a regular device client search6 ms003+33+3
Scenario: Validate a regular device count6 ms004+44+4
Scenario: Validate a regular device deletion9 ms003+33+3
Scenario: Validate a regular device query6 ms004+44+4
Scenario: Validate a regular device search7 ms003+33+3
Scenario: Validate deleting a device with a null device ID5 ms004+44+4
Scenario: Validate deleting a device with a null scope ID6 ms004+44+4
empty) scope0 ms008+88+8