System Test Report - GoranErdeljan/TINF19C-Team-4-Service-Registry GitHub Wiki

Created by Serdar Ilhan

1. Scope

The TCS / TRP (Test Case Specification / Test Report) describes the environment, the preconditions and the actions of a test performed or to be performed. If the test was performed, the results are given. Test Case Specification / Test Reports are referenced by System Integration Plans/Reports (SIP/SIR), by System Test Plans/Reports (STP/STR) and by System Validation Plans/Reports (SVP/SVR).

2. Product names and attributes

The following test objects must be verified:

Ref.ID Produktnummer Produktname Produktbeschreibung
1 Build v1.0 DNS-SD (Domain Name service - Service Discovery) to OI4-Service-Registry (Open Industry 4.0) Interface Listens to DNS SD records on the network and registers them with the OI4 service registry using an MQTT-Broker.
2 Build v1.0 Test Application The test application registers all open entries in the network via the DNS SD server

3. Test Equipment

The following equipment must be available for testing:

  • Linux Linux operating system
  • Docker application
  • The installed interfaces and the installed main application as described in the user manual (User-Manual-3.Installation).

4 Results of Testsiute

4.1 Results of Testsuit Testsuit-Adding services found using DNS-SD to the OI4-Registry

Testcase ID: Adding services found using DNS-SD to the OI4-Registry
Req.-ID: LF30 / Registering Services at the OI4-Registry , LF40 / Listening to Services registered at the OI4-Service-Registry

Test steps:

Step Action result
1 Build and run the docker containers as specified in the User Manual When using sudo docker ps all 4 containers are listed as running
2 Use avahi-publish to announce a service using DNS-SD Output established under name 'Test'
3 Go to the web interface of the OI4-Registry and check the list of applications The test application shows up in the list

Test data:

Dataset Command
1 avahi-publish -s Test _http._tcp 2201 "oi4=true" "ProductInstanceUri="urn:undefined.com/Test/bla/undefined"" "Manufacturer={"Locale":"de-de","Text":"TINF19C-Team4"}" "ManufacturerUri="urn:undefined.com"" "Model={"Locale":"de-de","Text":"DNS_SD_Test_Application"}" "ProductCode="DNS_SD_TEST"" "HardwareRevision=""" "SoftwareRevision="0.0"" "DeviceRevision=""" "DeviceManual="Not available"" "DeviceClass="Registry"" "RevisionCounter=1" "SerialNumber="undefined"" "Description={"Locale":"de-de","Text":"DNS_SD_Test_Application"}"

4.2 Results of Testsuit Testsuit-Ignoring services found using DNS-SD without 'oi4=true'-TXTRecords

Testcase ID: Ignoring services found using DNS-SD without 'oi4=true'-TXTRecords
Req.-ID: LF20 / Listening to DNS-SD Entries

Test steps:

Step Action result
1 Build and run the docker containers as specified in the User Manual When using sudo docker ps all 4 containers are listed as running
2 Use avahi-publish to announce a service using DNS-SD Output established under name 'Test'
3 Go to the web interface of the OI4-Registry and check the list of applications The test application does NOT show up in the list

Test data:

Dataset Command
1 avahi-publish -s Test _http._tcp 2201 "ProductInstanceUri="urn:undefined.com/Test/bla/undefined"" "Manufacturer={"Locale":"de-de","Text":"TINF19C-Team4"}" "ManufacturerUri="urn:undefined.com"" "Model={"Locale":"de-de","Text":"DNS_SD_Test_Application"}" "ProductCode="DNS_SD_TEST"" "HardwareRevision=""" "SoftwareRevision="0.0"" "DeviceRevision=""" "DeviceManual="Not available"" "DeviceClass="Registry"" "RevisionCounter=1" "SerialNumber="undefined"" "Description={"Locale":"de-de","Text":"DNS_SD_Test_Application"}"

4.3 Results of Testsuit Testsuit-Announce services found on the OI4-Message-Bus using DNS-SD

Testcase ID: Announce services found on the OI4-Message-Bus using DNS-SD
Req.-ID: LF30 / Registering Services at the OI4-Registry , LF40 / Listening to Services registered at the OI4-Service-Registry

Test steps:

Step Action result
1 Build and run the docker containers as specified in the User Manual When using sudo docker ps all 4 containers are listed as running
2 Go to the web interface of the test application The web interface is viewable
3 Check whether the OI4-Registry is shown in the list of DNS-SD entries List contains OI4-Registry

Test data: No Test data

4.4 Results of Testsuit Testsuit-Configure interface application using environment variables

Testcase ID: Configure interface application using environment variables
Req.-ID: LF30 / Registering Services at the OI4-Registry , LF40 / Listening to Services registered at the OI4-Service-Registry

Test steps:

Step Action result
1 Build the docker containers as specified in the User Manual When using sudo docker images both images show up
2 Run the OI4-Registry container and the eclipse-mosquitto container as specified in the User Manual When using 'sudo docker ps' both containers show up as "running"
3 Run the test application container as specified in the User Manual When using 'sudo docker ps' the container shows up as running
4 Run the interface application container with the environment variable MDNS_HOSTIP set to "192.168.0.100" When using 'sudo docker ps' the container shows up as running
5 Go to the web interface of the test application The DNS-SD entry of the OI4-Registry shows the IP-adress "192.168.0.100"

Test data: No Test data

4.5 Results of Testsuit Testsuit-Configure test application using environment variables

Testcase ID: Configure test application using environment variables
Req.-ID: LF30 / Registering Services at the OI4-Registry , LF40 / Listening to Services registered at the OI4-Service-Registry

Test steps:

Step Action result
1 Build the docker containers as specified in the User Manual When using sudo docker images both images show up
2 Run the OI4-Registry container and the eclipse-mosquitto container as specified in the User Manual When using 'sudo docker ps' both containers show up as "running"
3 Run the interface application container as specified in the User Manual When using 'sudo docker ps' the container shows up as running
4 Run the test application container with the environment variable MDNS_HOSTIP set to "192.168.0.100" When using 'sudo docker ps' the container shows up as running
5 Go to the web interface of the test application The DNS-SD entry of the DNS-SD test application shows the IP-adress "192.168.0.100"

Test data: No Test data