From: Jelte Jansen Date: Fri, 22 Mar 2013 15:19:41 +0000 (+0100) Subject: [2583] add LETTUCE_KEEP_OUTPUT options/env var X-Git-Tag: bind10-1.1.0beta1-release~29^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4660c86fe6aeb2c77427ca8cacd1b7f840d4e554;p=thirdparty%2Fkea.git [2583] add LETTUCE_KEEP_OUTPUT options/env var --- diff --git a/tests/lettuce/README b/tests/lettuce/README index 94bf82bb09..a53c6e7208 100644 --- a/tests/lettuce/README +++ b/tests/lettuce/README @@ -70,6 +70,11 @@ These files *will* be overwritten or deleted if the same scenarios are run again, so if you want to inspect them after a failed test, either do so immediately or move the files. +If you want to keep these output files even for successful runs, you can +specify the environment variable LETTUCE_KEEP_OUTPUT=1. The files will +still be overwritten by subsequent runs, but they will not automatically be +deleted. + Adding and extending tests -------------------------- diff --git a/tests/lettuce/features/terrain/terrain.py b/tests/lettuce/features/terrain/terrain.py index bb9759440a..89bdbad743 100644 --- a/tests/lettuce/features/terrain/terrain.py +++ b/tests/lettuce/features/terrain/terrain.py @@ -26,12 +26,16 @@ from lettuce import * import subprocess -import os.path +import os import shutil import re import sys import time +# lettuce cannot directly pass commands to the terrain, so we need to +# use environment variables to influence behaviour +KEEP_OUTPUT = 'LETTUCE_KEEP_OUTPUT' + # In order to make sure we start all tests with a 'clean' environment, # We perform a number of initialization steps, like restoring configuration # files, and removing generated data files. @@ -107,7 +111,7 @@ class RunningProcess: self.process = None self.step = step self.process_name = process_name - self.remove_files_on_exit = True + self.remove_files_on_exit = (os.environ.get(KEEP_OUTPUT) != '1') self._check_output_dir() self._create_filenames() self._start_process(args)