Add Fuego Functional.fuegotest
cover Add Fuego Functional.fuegotest
Functional test that tests Fuego itself.
As said in my previous e-mail, the test contains most of the infrastructure that we plan to use, but only a few actual tests.
Currently we're just implementing a few 'mock' tests and also testing ftc add-nodes and ftc add-jobs through Pexpect (shell) and SeleniumHQ (browser)
Thanks
Guilherme Campos Camargo (1):
Add fuego-release Functional test
engine/tests/Functional.fuegotest/fuego_test.sh | 29 ++ engine/tests/Functional.fuegotest/spec.json | 11 + engine/tests/Functional.fuegotest/test_run.py | 427 ++++++++++++++++++++++++ 3 files changed, 467 insertions(+) create mode 100755 engine/tests/Functional.fuegotest/fuego_test.sh create mode 100644 engine/tests/Functional.fuegotest/spec.json create mode 100755 engine/tests/Functional.fuegotest/test_run.py
Signature · 1 line
2.16.2
PATCH 1/1 Add fuego-release Functional test
Allows Fuego to test new Fuego releases
--- engine/tests/Functional.fuegotest/fuego_test.sh | 29 ++ engine/tests/Functional.fuegotest/spec.json | 11 + engine/tests/Functional.fuegotest/test_run.py | 427 ++++++++++++++++++++++++ 3 files changed, 467 insertions(+) create mode 100755 engine/tests/Functional.fuegotest/fuego_test.sh create mode 100644 engine/tests/Functional.fuegotest/spec.json create mode 100755 engine/tests/Functional.fuegotest/test_run.py
engine/tests/Functional.fuegotest/fuego_test.sh new file +29 -0
@@ -0,0 +1,29 @@ +#!/bin/bash + +set -e + +readonly fuego_release_dir=fuego-release + +function test_build { + if [ -d ${fuego_release_dir} ]; then + rm -r ${fuego_release_dir} + fi + git clone --quiet --depth 1 --single-branch \ + --branch "${FUNCTIONAL_FUEGOTEST_FUEGOBRANCH}" \ + "${FUNCTIONAL_FUEGOTEST_FUEGOREPO}" \ + "${fuego_release_dir}/fuego" + git clone --quiet --depth 1 --single-branch \ + --branch "${FUNCTIONAL_FUEGOTEST_FUEGOCOREBRANCH}" \ + "${FUNCTIONAL_FUEGOTEST_FUEGOCOREREPO}" \ + "${fuego_release_dir}/fuego-core" + cd - +} + +function test_run { + sudo -n ${TEST_HOME}/test_run.py "${fuego_release_dir}/fuego" + report "echo ok 1 minimal test on target" +} + +function test_processing { + log_compare "$TESTDIR" "1" "^ok" "p" +}
engine/tests/Functional.fuegotest/spec.json new file +11 -0
@@ -0,0 +1,11 @@ +{ + "testName": "Functional.fuegotest", + "specs": { + "default": { + "FUEGOREPO":"https://bitbucket.org/profusionmobi/fuego", + "FUEGOBRANCH":"next", + "FUEGOCOREREPO":"https://bitbucket.org/profusionmobi/fuego-core", + "FUEGOCOREBRANCH":"next" + } + } +}
engine/tests/Functional.fuegotest/test_run.py new file +427 -0
427 lines not on this page · raw message
Signature · 1 line
2.16.2
Tim, if you haven't touched this patch yet, please disconsider it and use the new ones, ok?
Sorry for the noise.
--
Guilherme
Quoted 27 lines · Guilherme Campos Camargo
Functional test that tests Fuego itself.
As said in my previous e-mail, the test contains most of the infrastructure that we plan to use, but only a few actual tests.
Currently we're just implementing a few 'mock' tests and also testing
ftc add-nodesandftc add-jobsthrough Pexpect (shell) and SeleniumHQ (browser)Thanks
Guilherme Campos Camargo (1):
Add fuego-release Functional testengine/tests/Functional.fuegotest/fuego_test.sh | 29 ++ engine/tests/Functional.fuegotest/spec.json | 11 + engine/tests/Functional.fuegotest/test_run.py | 427 ++++++++++++++++++++++++ 3 files changed, 467 insertions(+) create mode 100755 engine/tests/Functional.fuegotest/fuego_test.sh create mode 100644 engine/tests/Functional.fuegotest/spec.json create mode 100755 engine/tests/Functional.fuegotest/test_run.py--
2.16.2