Skip to content

Commit

Permalink
Added integration tests for limitExceed value
Browse files Browse the repository at this point in the history
  • Loading branch information
@MDeLuise @Coduz
MDeLuise authored and Coduz committed Aug 4, 2021
1 parent 2c36ba7 commit 8ed3fff
Show file tree
Hide file tree
Showing 4 changed files with 488 additions and 0 deletions.
21 changes: 21 additions & 0 deletions ...tegration-steps/src/main/java/org/eclipse/kapua/qa/integration/steps/RestClientSteps.java
View file
Expand Up @@ -207,6 +207,27 @@ public void restResponseDoesntContainUser(int expeted) throws Exception {
Assert.assertEquals("Wrong response code.", expeted, restResponseCode);
}

@Then("^REST response contains limitExceed field with value (true|false)$")
public void restResponseContainsLimitExceedValueWithValue(String value) throws Exception {
String restResponse = (String) stepData.get(REST_RESPONSE);
UserListResult userList = XmlUtil.unmarshalJson(restResponse, UserListResult.class, null);
Assert.assertEquals(Boolean.parseBoolean(value), userList.isLimitExceeded());
}

@Given("^An authenticated user$")
public void anAuthenticationToken() throws Exception {
restPostCallWithJson("/v1/authentication/user",
"{\"password\": \"kapua-password\", \"username\": \"kapua-sys\"}");
restResponseContainingAccessToken();
}

@Given("^(\\d+) new users? created$")
public void newUsersCreated(int howManyUser) throws Exception {
for (int i = 0; i < howManyUser; ++i) {
restPostCallWithJson("/_/users", String.format("{\"name\": \"new-user-%d\"}", i));
}
}

/**
* Take input parameter and replace its $var$ with value of var that is stored
* in step data.
Expand Down
324 changes: 324 additions & 0 deletions qa/integration/src/test/resources/features/datastore/Datastore.feature
View file
Expand Up @@ -976,6 +976,330 @@ Feature: Datastore tests
Then An assertion error was thrown
And I logout

Scenario: Create 4 clients, query all clients with offset 0 and limit 1
Check if value of limitExceed is true.

Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | ci_topic_by_account/1/2/3 |
| test-client-1 | ci_topic_by_account/1/2/4 |
| test-client-1 | ci_topic_by_account/1/2/5 |
| test-client-1 | ci_topic_by_account/1/2/6 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account channels with limit 1 and offset 0 and store them as "AccountChannelList"
Then The channel list "AccountChannelList" have limitExceed value true
And I delete all indices
And I logout

Scenario: Create 4 clients, query all clients with offset 0 and limit 4
Check if value of limitExceed is false.

Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | ci_topic_by_account/1/2/3 |
| test-client-1 | ci_topic_by_account/1/2/4 |
| test-client-1 | ci_topic_by_account/1/2/5 |
| test-client-1 | ci_topic_by_account/1/2/6 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account channels with limit 4 and offset 0 and store them as "AccountChannelList"
Then The channel list "AccountChannelList" have limitExceed value false
And I delete all indices
And I logout

Scenario: Create 4 clients, query all clients with offset 2 and limit 1
Check if value of limitExceed is true.

Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | ci_topic_by_account/1/2/3 |
| test-client-1 | ci_topic_by_account/1/2/4 |
| test-client-1 | ci_topic_by_account/1/2/5 |
| test-client-1 | ci_topic_by_account/1/2/6 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account channels with limit 1 and offset 2 and store them as "AccountChannelList"
Then The channel list "AccountChannelList" have limitExceed value true
And I delete all indices
And I logout

Scenario: Create 4 clients, query all clients with offset 1 and limit 3
Check if value of limitExceed is false.

Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | ci_topic_by_account/1/2/3 |
| test-client-1 | ci_topic_by_account/1/2/4 |
| test-client-1 | ci_topic_by_account/1/2/5 |
| test-client-1 | ci_topic_by_account/1/2/6 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account channels with limit 3 and offset 1 and store them as "AccountChannelList"
Then The channel list "AccountChannelList" have limitExceed value false
And I delete all indices
And I logout

Scenario: Create 4 metrics, query all metrics with offset 0 and limit 1
Check if value of limitExceed is true.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
And I set the following metrics to the message 0 from the list "TestMessages"
| metric | type | value |
| tst-metric-1 | double | 123 |
| tst-metric-2 | int | 123 |
And I set the following metrics to the message 1 from the list "TestMessages"
| metric | type | value |
| tst-metric-3 | string | 123 |
| tst-metric-4 | bool | true |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics with limit 1 and offset 0 and store them as "AccountMetrics"
Then The metric list "AccountMetrics" have limitExceed value true
And I delete all indices

Scenario: Create 4 metrics, query all metrics with offset 0 and limit 4
Check if value of limitExceed is false.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
And I set the following metrics to the message 0 from the list "TestMessages"
| metric | type | value |
| tst-metric-1 | double | 123 |
| tst-metric-2 | int | 123 |
And I set the following metrics to the message 1 from the list "TestMessages"
| metric | type | value |
| tst-metric-3 | string | 123 |
| tst-metric-4 | bool | true |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics with limit 4 and offset 0 and store them as "AccountMetrics"
Then The metric list "AccountMetrics" have limitExceed value false
And I delete all indices

Scenario: Create 4 metrics, query all metrics with offset 2 and limit 1
Check if value of limitExceed is true.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
And I set the following metrics to the message 0 from the list "TestMessages"
| metric | type | value |
| tst-metric-1 | double | 123 |
| tst-metric-2 | int | 123 |
And I set the following metrics to the message 1 from the list "TestMessages"
| metric | type | value |
| tst-metric-3 | string | 123 |
| tst-metric-4 | bool | true |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics with limit 1 and offset 2 and store them as "AccountMetrics"
Then The metric list "AccountMetrics" have limitExceed value true
And I delete all indices

Scenario: Create 4 metrics, query all metrics with offset 3 and limit 1
Check if value of limitExceed is false.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
And I set the following metrics to the message 0 from the list "TestMessages"
| metric | type | value |
| tst-metric-1 | double | 123 |
| tst-metric-2 | int | 123 |
And I set the following metrics to the message 1 from the list "TestMessages"
| metric | type | value |
| tst-metric-3 | string | 123 |
| tst-metric-4 | bool | true |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics with limit 1 and offset 3 and store them as "AccountMetrics"
Then The metric list "AccountMetrics" have limitExceed value false
And I delete all indices

Scenario: Create 4 clients, query all clients with offset 0 and limit 1
Check if value of limitExceed is true.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/4 |
| test-client-3 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/4 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account clients with limit 1 and offset 0 and store them as "ClientInfo"
Then The client list "ClientInfo" have limitExceed value true
And I delete all indices

Scenario: Create 4 clients, query all clients with offset 0 and limit 4
Check if value of limitExceed is false.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/4 |
| test-client-3 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/4 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account clients with limit 4 and offset 0 and store them as "ClientInfo"
Then The client list "ClientInfo" have limitExceed value false
And I delete all indices

Scenario: Create 4 clients, query all clients with offset 2 and limit 1
Check if value of limitExceed is true.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/4 |
| test-client-3 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/4 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account clients with limit 1 and offset 2 and store them as "ClientInfo"
Then The client list "ClientInfo" have limitExceed value true
And I delete all indices

Scenario: Create 4 clients, query all clients with offset 3 and limit 1
Check if value of limitExceed is false.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/4 |
| test-client-3 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/4 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account clients with limit 1 and offset 3 and store them as "ClientInfo"
Then The client list "ClientInfo" have limitExceed value false
And I delete all indices

Scenario: Create 4 messages, query all messages with offset 0 and limit 1
Check if value of limitExceed is true.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-client-1"
And I set the database to device timestamp indexing
When I prepare a number of messages in the specified ranges and remember the list as "TestMessages"
| clientId | topic | count | startDate | endDate |
| test-client-1 | delete/by/date/test | 3 | 2018-10-01T12:00:00.000Z | 2018-12-31T12:00:00.000Z |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account messages with limit 1 and offset 0 and store them as "MessageInfo"
Then The message list "MessageInfo" have limitExceed value true
And I delete all indices

Scenario: Create 4 messages, query all messages with offset 0 and limit 4
Check if value of limitExceed is false.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-client-1"
And I set the database to device timestamp indexing
When I prepare a number of messages in the specified ranges and remember the list as "TestMessages"
| clientId | topic | count | startDate | endDate |
| test-client-1 | delete/by/date/test | 3 | 2018-10-01T12:00:00.000Z | 2018-12-31T12:00:00.000Z |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account messages with limit 4 and offset 0 and store them as "MessageInfo"
Then The message list "MessageInfo" have limitExceed value false
And I delete all indices

Scenario: Create 4 messages, query all messages with offset 2 and limit 1
Check if value of limitExceed is true.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-client-1"
And I set the database to device timestamp indexing
When I prepare a number of messages in the specified ranges and remember the list as "TestMessages"
| clientId | topic | count | startDate | endDate |
| test-client-1 | delete/by/date/test | 3 | 2018-10-01T12:00:00.000Z | 2018-12-31T12:00:00.000Z |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account messages with limit 1 and offset 2 and store them as "MessageInfo"
Then The message list "MessageInfo" have limitExceed value true
And I delete all indices

Scenario: Create 4 messages, query all messages with offset 3 and limit 1
Check if value of limitExceed is false.

Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-client-1"
And I set the database to device timestamp indexing
When I prepare a number of messages in the specified ranges and remember the list as "TestMessages"
| clientId | topic | count | startDate | endDate |
| test-client-1 | delete/by/date/test | 3 | 2018-10-01T12:00:00.000Z | 2018-12-31T12:00:00.000Z |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account messages with limit 1 and offset 3 and store them as "MessageInfo"
Then The message list "MessageInfo" have limitExceed value false
And I delete all indices

Scenario: Stop broker after all scenarios

Given Stop Broker
Expand Down

0 comments on commit 8ed3fff

Please sign in to comment.