...
Test Bed
The test bed consists of a VM 4 VMs running on x86 hardware, performing jump host/deploy deploy and ci/cd and build and master node roles, two edge nodes on ARM64 (Jetson Nano) hardware, and two sensor nodes on ARM32 (Raspberry Pi) hardware.
| Node Type | Count | Hardware | OS | ||
|---|---|---|---|---|---|
Deploy Master CI/CD Build | 4 | Jump Host, Deploy/Master | 1 | Intel i5, 2 cores VM | Ubuntu 20.04 |
| Edge | 2 | Jetson Nano, ARM Cortex-A57, 4 cores | Ubuntu 20.04 | ||
| SensorCamera | 2 | Raspberry Pi 3, ARM Cortex-A53, 4 cores | Rasbian 11.1 | H.View HV-500E6A | N/A (pre-installed) |
The Build A second VM is used to run the BluVal test framework components outside the system under test.
...
Traffic Generator
N/A
Test API description
CI/CD Regression Tests:
...
Node Setup
This set of test cases confirms the Docker private registry setup, population, and tear-down proceduresscripting to change the default runtime of edge nodes.
The Test inputs
The test scripts and data are stored in the source repository's cicd/tests/sdt_step2/install/docker directory.
Test Procedure
The test bed is placed place in a state with the deploy and master node setup complete, but with Kubernetes, EdgeX, and the private registry not running.where all nodes are prepared with required software. No EdgeX or Kubernetes services are running.
Execute the test scripts:
robot cicd/tests/docker/sdt_step2/install/
Expected output
The test script scripts will start the registry, pull upstream images and populate the registry, clean images left over from the pull process, stop the registry, and remove the registry. The change the default runtime of edge nodes from runc to nvidia. The robot command should report success for all test cases.
Test Results
Nexus URL: https://nexus.akraino.org/content/sites/logs/fujitsu/job/lfedge-docker/1/
Pass (51/5 1 test casescase)
CI/CD Regression Tests:
...
Images Build & Push
These
...
This set of test cases confirms the scripting to initialize master and edge nodesverify that the images for EdgeX microservices can be constructed, and pushed to private registry.
The Test inputs
The test scripts and data are stored in the source repository's cicd/tests/install directorysdt_step2/build/ directory.
Test Procedure
The test bed is place placed in a state where only the deploy node is initialized. No EdgeX or Kubernetes services are running. For a complete test, the master and edge nodes should not have any software installed that was not installed as part of the OS installationall nodes are prepared with required software and the Docker registry is running. The registry must be populated with the Kubernetes and Flannel images from upstream.
Execute the test scripts:
robot cicd/tests/sdt_step2/build/install
Expected output
The test scripts will initialize the master and edge nodes and verify the required software is installedbuild images of changed services(sync-app/image-app/device-camera), add push the images to private registry. The robot command should report success for all test cases.
Test Results
Nexus URL: https://nexus.akraino.org/content/sites/logs/fujitsu/job/lfedge-install/1/
Pass (21/2 1 test casescase)
CI/CD Regression Tests: Cluster Setup & Teardown
...