/
DatastoreNewIndexCustomPrefix.feature
49 lines (41 loc) · 1.75 KB
/
DatastoreNewIndexCustomPrefix.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
###############################################################################
# Copyright (c) 2018 Eurotech and/or its affiliates and others
#
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Eclipse Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/epl-v10.html
#
# Contributors:
# Eurotech - initial API and implementation
#
###############################################################################
@datastore
Feature: Datastore tests
@StartDatastore
Scenario: Start datastore for all scenarios
@StartEventBroker
Scenario: Start event broker for all scenarios
@StartBroker
Scenario: Start broker for all scenarios
Scenario: Create index with specific prefix
Create elasticsearch index with specific prefix set by system property.
Index gets created when user publishes data.
Given Server with host "127.0.0.1" on port "9200"
When All indices are deleted
And I login as user with name "kapua-sys" and password "kapua-password"
And Account for "kapua-sys"
Given The device "test-device-1"
When I prepare a random message with capture date "2018-01-01T10:21:32.123Z" and save it as "RandomDataMessage"
And I store the message "RandomDataMessage" and remember its ID as "RandomDataMessageId"
And I refresh all database indices
When REST call at "/_cat/indices/"
Then REST response containing text "green open"
And REST response containing text "custom-prefix-1-2018-01"
And All indices are deleted
@StopBroker
Scenario: Stop broker after all scenarios
@StopEventBroker
Scenario: Stop event broker for all scenarios
@StopDatastore
Scenario: Stop datastore after all scenarios