Build #711 (Jan 19, 2021 3:57:07 AM)

	Changes Added Junit tests for broker module (details / githubweb)
	Started by an SCM change
	Revision: bd6470a1f7aa637bbade958855cd6cc3de1f7c8e origin/develop
	Test Result (18 failures / +16) Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT" Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 2222 Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 2222 Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 2222 Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account Scenario: Executing Job When Device Connected After The Specified Start Date And Time.And I confirm the executed job is finished Scenario: Executing Job When Device Connected After The Specified Start Date And Time.Scenario: Executing Job When Device Connected After The Specified Start Date And Time Scenario: Executing Job When Device Connected Before End Date And Time.And I confirm the executed job is finished Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time Scenario: Executing Job And Then Restarting Device.Then I find 4 device events Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53" Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description Show all failed tests >>>