Commit 638a844c authored by Kirill Smelkov's avatar Kirill Smelkov

X Discovered more issues with buildout code injection

parent e41706c1
...@@ -120,6 +120,12 @@ def XN_PEER(xn_addr): ...@@ -120,6 +120,12 @@ def XN_PEER(xn_addr):
class ENBTestCase(AmariTestCase): class ENBTestCase(AmariTestCase):
maxDiff = None # want to see full diff in test run log on an error maxDiff = None # want to see full diff in test run log on an error
# stress correctness of ru_ref/cell_ref/... usage throughout all places in
# buildout code - special characters should not lead to wrong templates or
# code injection.
default_partition_reference = AmariTestCase.default_partition_reference + \
'${aaa:bbb}\n[ccc];'
# XXX temp # XXX temp
instance_max_retry = 1 instance_max_retry = 1
report_max_retry = 1 report_max_retry = 1
......
...@@ -5,7 +5,7 @@ ...@@ -5,7 +5,7 @@
export SLAPOS_TEST_DEBUG=1 export SLAPOS_TEST_DEBUG=1
export SLAPOS_TEST_VERBOSE=1 export SLAPOS_TEST_VERBOSE=1
export SLAPOS_TEST_SKIP_SOFTWARE_CHECK=1 export SLAPOS_TEST_SKIP_SOFTWARE_CHECK=1
export SLAPOS_TEST_SKIP_SOFTWARE_REBUILD=0 export SLAPOS_TEST_SKIP_SOFTWARE_REBUILD=1
rm -rf snapshot rm -rf snapshot
mkdir snapshot mkdir snapshot
...@@ -18,5 +18,5 @@ export SLAPOS_TEST_LOG_DIRECTORY=`pwd`/snapshot ...@@ -18,5 +18,5 @@ export SLAPOS_TEST_LOG_DIRECTORY=`pwd`/snapshot
#time ../k/kpython_for_test -m unittest discover -vf -k SimCard #time ../k/kpython_for_test -m unittest discover -vf -k SimCard
#time ../k/kpython_for_test -m unittest discover -vf #time ../k/kpython_for_test -m unittest discover -vf
#time ../k/kpython_for_test -m unittest discover -vf -k TestENB_CPRI #time ../k/kpython_for_test -m unittest discover -vf -k TestENB_CPRI
#time ../k/kpython_for_test -m unittest discover -vf -k TestENB_SDR time ../k/kpython_for_test -m unittest discover -vf -k TestENB_SDR
time ../k/kpython_for_test -m unittest discover -vf -k TestENB_Lopcomm #time ../k/kpython_for_test -m unittest discover -vf -k TestENB_Lopcomm
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment