test execution flow outline

Here is an outline of the flow of control for test execution in fuego:

This example if for the fictional test Functional.foo:

sample paths [edit section]

The overlay generator is called with the following arguments:

Legacy (1.0) test information [edit section]

This section has some historical information that only applies to Fuego 1.0. We no longer ship the Jenkins config.xml files for jobs, but instead require the user to create them at installation time with 'ftc add-jobs'.

jobs definitions [edit section]

As of February 2017, there are 67 job config.xml files under fuego-core/jobs

63 jobs source something besides functions.sh (functions.sh is sourced for the call to post_test)

The job Functional.libpng/config.xml sources 2 items (besides functions.sh) This test is very weird and runs all the phases itself, instead of running a single base script.

The following jobs don't source any shell scripts:

There are 30 Functional job directories, and 30 Benchmark job directories.

The following job directly sources reports.sh, then does gen_report:

The following tests don't start with Functional or Benchmark:

test definitions [edit section]

There are 31 Functional test directories, and 33 Benchmark test directories.

.sh scripts [edit section]

There are 29 Functional tests with .sh files:

There are 31 Benchmark tests with .sh files:

Functional tests not sourcing functional.sh [edit section]

There are 21 Functional .sh files that call functional.sh Here are the ones that don't:

There are 2 Functional tests that source stress.sh

Benchmark tests not sourcing benchmark.sh [edit section]

There are 28 Benchmark tests that source benchmark.sh.

Here are the ones that don't: