- 18 9月, 2015 1 次提交
-
-
由 Lukáš Doktor 提交于
The name was not correct as the test should error-out. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 15 9月, 2015 1 次提交
-
-
由 Lukáš Doktor 提交于
Currently when one passes exception, which is not instance of Exception, avocado proceeds and returns "INTERRUPTED" test instead of "ERROR". This for example happens when old-style-class is used as exception. This patch uses pure "except" without any argument to catch such exceptions and then it wraps them in "exceptions.TestError" instead. The same applies to "setUp" and "tearDown", they only use different class as a wrapper. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 18 6月, 2015 1 次提交
-
-
由 Lukáš Doktor 提交于
The runTest method has been obsoleted and everyone should be using "test*" method(s) instead. This patch removes the support and replaces the default and example entry points to "test". Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 09 6月, 2015 1 次提交
-
-
由 Cleber Rosa 提交于
Only avocado.Test is of general interest to test writers. For that reason the entire test module has been moved to the avocado.core namespace. The recommended way to go about writing instrumented tests is something like: from avocado import Test class MyTest(Test): def test_foo(self): do_stuff() Changes from v2: * Fixed references in docstrings * Fixed refrences of avocado.test in Writing Test Guide docs Changes from v1: * Fixed comment typo on commit message * Fixed old reference of avocado.test (then test.Test) instead of avocado then Test in GDB docs. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 24 4月, 2015 2 次提交
-
-
由 Rudá Moura 提交于
Export avocado.core.job.main as avocado.main, so that make it look like an API for test developers to use. Signed-off-by: NRudá Moura <rmoura@redhat.com>
-
由 Rudá Moura 提交于
Move avocado.job to avocado.core.job, in conformance to our purpose of keeping things not related to test developers, inside avocado.core, isolated from users. Signed-off-by: NRudá Moura <rmoura@redhat.com>
-
- 07 4月, 2015 1 次提交
-
-
由 Rudá Moura 提交于
We're going one step ahead to unittest compatibility. Now we obsolete action() method and use runTest(). Then what is runTest() will be run(). Update the selftests and tests regarding this modification. Signed-off-by: NRudá Moura <rmoura@redhat.com>
-
- 04 3月, 2015 1 次提交
-
-
由 Lukáš Doktor 提交于
The NastyException error is back: class NastyException(Exception): def __init__(self, msg): self.msg = msg def __str__(self): return self.msg crashes Avocado. The problem is we are trying to re-raise the exceptions and then read the traceback again. Even reading of the details of this very nasty written exception causes critical failure. What this patch does instead of handling issues wherever we produce them, it waits till the exception bubbles to the entry-point and it tries to read it. If it fails, we log the original traceback (information about the failure) and then user-friendly message saying we're unable to retrieve the original failure. Additionally I had to modify the xunit output as in case of very nasty inputs it's unable to reproduce the values. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-