barbican/.testr.conf

[DEFAULT]
test_command=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
             OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
             OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} \
             ${PYTHON:-python} -m subunit.run discover -s ${OS_TEST_PATH:-./barbican} -t . $LISTOPT $IDOPTION

test_id_option=--load-list $IDFILE
test_list_option=--list
group_regex=([^\.]+\.)+
Switch to testr Change-Id: I6ca365e0b0d2ec86e0b61ce4c58b967260d480a7 2014-01-27 18:19:53 -06:00			`[DEFAULT]`
Modifying testr conf to suppress output Testr pumps out a lot of output to the screen even with successful tests. Other OpenStack projects solve this by modifying their testr config to force stdout and stderr capture similar to other testing frameworks. For this change, I have copied how Nova handles this. Change-Id: Ie6fb60585a632e09fef068f768c6b6fde10017f0 2014-09-13 15:12:58 -05:00			`test_command=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \`
			`OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \`
Use testr for running functional tests and documentation Alters tox.ini to use testr rather than nosetests. Also, adds documentation on how to use tox to run a single functional test class. Change-Id: I1333ead397f338ee3da3d81b0e1de8e93283a2b5 Closes-Bug: #1490747 2015-08-28 01:38:39 -05:00			`OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} \`
			`${PYTHON:-python} -m subunit.run discover -s ${OS_TEST_PATH:-./barbican} -t . $LISTOPT $IDOPTION`
Switch to testr Change-Id: I6ca365e0b0d2ec86e0b61ce4c58b967260d480a7 2014-01-27 18:19:53 -06:00
			`test_id_option=--load-list $IDFILE`
			`test_list_option=--list`
Use testr for running functional tests and documentation Alters tox.ini to use testr rather than nosetests. Also, adds documentation on how to use tox to run a single functional test class. Change-Id: I1333ead397f338ee3da3d81b0e1de8e93283a2b5 Closes-Bug: #1490747 2015-08-28 01:38:39 -05:00			`group_regex=([^\.]+\.)+`