osmo-gsm-tester/.gitignore

__pycache__
pid
.*.sw?
version
_version.py
tags
set_pythonpath
test_work
state
*.pyc
selftest/trial_test/
example/resources.conf
add .gitignore 6 years ago			`__pycache__`
			`pid`
			`.*.sw?`
			`version`
			`_version.py`
			`tags`
core implementation code bomb implementing the bulk of the osmo-gsm-tester Change-Id: I53610becbf643ed51b90cfd9debc6992fe211ec9 6 years ago			`set_pythonpath`
			`test_work`
			`state`
gitignore: Add *.pyc Change-Id: I987df905c5d64294488b5a6cdcf4306307616fc6 6 years ago			`*.pyc`
Add JUnit XML reports; refactor test reporting * Add Junit output file support * Differentiate between an expected failure test and an error in the test, as described in JUnit. * In case of an error/exception during test, record and attach it to the Test object and continue running the tests, and show it at the end during the trial report. Change-Id: Iedf6d912b3cce3333a187a4ac6d5c6b70fe9d5c5 6 years ago			`selftest/trial_test/`
example: Maintain different resources.conf for RnD and prod We still want to maintain this file in the same osmo-gsm-tester repo because we frequently neef to update the config when adding new features. Until now only 1 file was maintained (which was used for RnD setup), and then when runnin in prod the jenkins script used sed to change the file to accomodate slightly changes. This way is too hacky, so let's just maintain too separate files, keeping the original resources.conf key name used by osmo-gsm-tester free, so that jenkins job can symlink one of the 2 files to it. Take the chance to remove OctoBTS and Sysmocell5k from the RnD resources file, as we don't have those them. Change-Id: Ifec851c7ac6fca6b294e57dfe86b92f214ae8f42 5 years ago			`example/resources.conf`