[PATCH 1/5] enable assertions for autoqa tests

Kamil Páral kparal at redhat.com
Fri Sep 10 13:52:27 UTC 2010


Let's enable assertions for autoqa tests. That allows us to quickly
check for situations we think about as showstoppers and it lets us to
end the test quickly (and it will be automatically reported as CRASHED).

Of course an alternative to assertions is to throw exceptions by hand,
but using assertions is much easier and there is no big drawback (only
our tests are compiled with assertions enabled, therefore the
performance hit is neglectable).
---
 Makefile |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Makefile b/Makefile
index 0931a69..a964e1e 100644
--- a/Makefile
+++ b/Makefile
@@ -31,7 +31,7 @@ install: build
 	for t in tests/*; do cp -a $$t $(PREFIX)$(TEST_DIR); done
 	install -d $(PREFIX)$(AUTOTEST_DIR)/client/bin
 	install -m 0644 lib/autotest/site_utils.py $(PREFIX)$(AUTOTEST_DIR)/client/bin
-	( cd lib/python; $(PYTHON) setup.py install -O1 --skip-build --root $(PREFIX)/ )
+	( cd lib/python; $(PYTHON) setup.py install --skip-build --root $(PREFIX)/ )
 	## front-ends/israwhidebroken
 	install -d $(PREFIX)/usr/sbin
 	install -d $(PREFIX)/usr/share/autoqa-israwhidebroken
-- 
1.7.2.2



More information about the autoqa-devel mailing list