/
DeviceBrokerIpConfigFileI9n.feature
39 lines (33 loc) · 1.48 KB
/
DeviceBrokerIpConfigFileI9n.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
###############################################################################
# Copyright (c) 2017, 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
###############################################################################
@broker
Feature: Device Broker connection ip with config file
Device Service integration scenarios with running broker service.
@StartDatastore
Scenario: Start datastore for all scenarios
@StartBroker
Scenario: Start broker for all scenarios
Scenario: Send BIRTH message and then DC message while broker ip is set by config file
Effectively this is connect and disconnect of Kura device.
Basic birth - death scenario. Scenario includes check that broker server ip
is correctly set with config file.
When I start the Kura Mock
And Device birth message is sent
And I wait 5 seconds for system to receive and process that message
And I login as user with name "kapua-sys" and password "kapua-password"
Then Device is connected with "192.168.33.10" server ip
And I logout
And Device death message is sent
@StopBroker
Scenario: Stop broker after all scenarios
@StopDatastore
Scenario: Stop datastore after all scenarios