Summary

eliminate code in all tests that manages last_used_testplan;; Owner: Tim; Reporter: Tim; Status: closed; Priority: high

; Summary: eliminate code in all tests that manages last_used_testplan;; Owner: Tim; Reporter: Tim; Status: closed; Priority: high

Description [edit section]

= Description =Currently, there is code in every single test's config.xml file (Jenkinstest configuration file), like the following:

{{{#!YellowBoxif [ ! -d "$FUEGO_LOGS_PATH/$JOB_NAME" ]; then mkdir -p "$FUEGO_LOGS_PATH/$JOB_NAME"; fi        echo $TESTPLAN >$FUEGO_LOGS_PATH/$JOB_NAME/last_used_testplan;        TESTPLAN=testplans/$TESTPLAN.json}}}

This is followed by the actual invocation of the test base script usinga 'source' line.

It would be nice to eliminate this duplication and put these mkdir and filecreation operations into the functional.sh or benchmark.sh files, so theydon't clutter up each individual test.

Do some research to see why these are expressed this way, and if neededrefactor the handling of testplans to avoid this problem.  This lookslike it was done as a quick hack to save the last_used_testplan.

Also, why is the indentation in these files so weird?

Notes [edit section]

= Notes =Also, why can't the 'source' line be calculated, and the entire config.xmlfile generated at test package install time.  It probably could be ifthe base script name were required to follow a convention (either have thesame name as the test, or have the name base_script.sh)

backlink

Fuego Issues List

; backlink: [[Fuego Issues List]]