The ioFog Test Runner provides a convenient way to run multiple smoke test suites on a deployed Edge Compute Network (ECN).

The suite by default does not run any non-smoke tests, i.e. tests that would invalidate or potentially break the ECN, therefore it can be used on staging a productions ECNs to verify correct deployment.

The following test suites are available:

• Controller REST API smoke tests
• Agent CLI smoke tests
• Basic microservice deployment integration tests

Note that some of additional test suites are automatically skipped as of this release of Test Runner.

You must have iofogctl configured with its default namespace pointing to the ECN you want to test

Example usage of the test runner with iofogctl configuration:

docker run --name test-runner \
        -v ~/.iofog/:/root/.iofog/ \
        iofog/test-runner:latest

Example usage of the test runner with endpoint configurations configuration:

docker run --name test-runner \
        -v ~/.ssh/my_iofog_agent_ssh_key:/root/.ssh/id_rsa \
        -e CONTROLLER="1.2.3.4:51121" \
        -e CONTROLLER_EMAIL="[email protected]" \
        -e CONTROLLER_PASSWORD="#Bugs4Fun" \
        -e AGENT_USER="root" \
        -e AGENT_KEY="/root/.ssh/id_rsa" \
        iofog/test-runner:latest

Note that whenever AGENTS is specified, you need to mount appropriate ssh keys to /root/.ssh of the test-runner containers. The keys can be in any default SSH position: ~/.ssh/id_dsa, ~/.ssh/id_ecdsa, ~/.ssh/id_ed25519 and ~/.ssh/id_rsa.

The output of this test-suite currently is a single XML File that is Junit-XML compliant. This can be used in development pipelines on most DevOps infrastructure to display test results in easy to consume factor.

This is used in Azure Pipelines to display each builds pass/fail for both entire test suites as well as for specific tests we may see multiple failures in, to help identify issues that may not be consistent.

The test output is file is TEST-RESULTS.xml and is stored in /root/test-results of the test-runner container.