From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <daniel.sangorrin@toshiba.co.jp>
From: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Date: Tue,  4 Sep 2018 19:01:29 +0900
Message-Id: <1536055292-34772-1-git-send-email-daniel.sangorrin@toshiba.co.jp>
Subject: [Fuego] Dynamic variables
List-Id: Mailing list for the Fuego test framework
	<fuego.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/fuego>,
	<mailto:fuego-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/fuego/>
List-Post: <mailto:fuego@lists.linuxfoundation.org>
List-Help: <mailto:fuego-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/fuego>,
	<mailto:fuego-request@lists.linuxfoundation.org?subject=subscribe>
To: fuego@lists.linuxfoundation.org

Hello Tim,

These patches add dynamic vars to ftc run-test so that one
can easily test variations of a base spec by overriding its
values. Although prolog.sh contains the values used by the
run, I also store a spec.json file on the log directory
for each run. I think this is cleaner and easier to
read than having to dig in prolog.sh

[PATCH 1/3] of: use logdir argument instead of prolog.sh
[PATCH 2/3] OF: create a spec.json on each run
[PATCH 3/3] ftc: add dynamic-vars to ftc run-test

Thanks,
Daniel