- 08 4月, 2015 5 次提交
-
-
由 Rudá Moura 提交于
It's now possible to select test methods to execute, in the multiple tests context, by using a special form. When you select `filename.py:test_method_pattern` it will filter out every test methods and use just the test_method_pattern passed. The pattern is a shell like feature, so `test_connection*` will select every test method that starts with `test_connection` to execute. Example: $ avocado run examples/tests/gdbtest.py:\*connect*\ will run: (1/3) gdbtest.py:GdbTest.test_connect_multiple_clients: PASS (2.41 s) (2/3) gdbtest.py:GdbTest.test_disconnect: PASS (2.52 s) (3/3) gdbtest.py:GdbTest.test_disconnect_raw: PASS (4.52 s) and $ avocado run examples/tests/gdbtest.py:test_connect_multiple_clients will test just: (1/1) gdbtest.py:GdbTest.test_connect_multiple_clients: PASS (2.34 s) Note that we've scape the test method pattern to avoid shell expansion! Signed-off-by: NRudá Moura <rmoura@redhat.com>
-
由 Rudá Moura 提交于
Remove words for setup, cleanup and action and update to the new slang: setUp, tearDown and runTest. Signed-off-by: NRudá Moura <rmoura@redhat.com>
-
由 Rudá Moura 提交于
When a class has multiple tests, display each test. Example: INSTRUMENTED examples/tests/gdbtest.py:GdbTest.test_connect_multiple_clients Signed-off-by: NRudá Moura <rmoura@redhat.com>
-
由 Rudá Moura 提交于
Set the datadir for test based upon the filename of the class, so that multiple test methods in a same test class will share the same datadir directory. Signed-off-by: NRudá Moura <rmoura@redhat.com>
-
由 Rudá Moura 提交于
Introduce multiple test methods defined in Avocado Test class. The tests looks like the one of unittest module. The test methods are defined when you create test<something> methods, inside the test class. Each test methods becomes a test case unit to execute. Example: class MyTest(avocado.test.Test): def test_eone(self)... def test_two(self)... def testAnotherone(self)... Signed-off-by: NRudá Moura <rmoura@redhat.com>
-
- 07 4月, 2015 2 次提交
-
-
由 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>
-
由 Rudá Moura 提交于
avocado.runner: Fortify early_state.get(timeout)
-
- 03 4月, 2015 1 次提交
-
-
由 Lukáš Doktor 提交于
We shouldn't heavily rely on early_state. This patch tries to get value from early_state and when it's 0/None uses DEFAULT_TIMEOUT. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 01 4月, 2015 2 次提交
-
-
由 Cleber Rosa 提交于
-
由 Rudá Moura 提交于
When running 'run --help' piped through a non existing command, exit gracefully with a shell error and don't print the whole trace back message. Reference: https://trello.com/c/Nm4elZrb/363-bug-avocado-should-fail-gracefully-when-redirected-to-a-broken-pipeSigned-off-by: NRudá Moura <rmoura@redhat.com>
-
- 31 3月, 2015 4 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
examples.tests.simplewarning: Use -e to exit on failure
-
由 Lukáš Doktor 提交于
In tree execution worked fine in virtual environment, but not without it. This commit tries to iterate through PATH and detect the in-tree libexec path. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Lukáš Doktor 提交于
We need to execute avocado in simpletests, thus we need both, libexec and scripts directories inside PATH. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Lukáš Doktor 提交于
Use -e to exit on first failure. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 30 3月, 2015 6 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Run unittests during the build of RPM packages [v2]
-
由 Cleber Rosa 提交于
It seems a good idea, and another safety net, to run the selftests during the build of packages. For now, it's not trivial to run the functional tests, so let's at least run the unittests. Another current limitation is that unittests are only run on Fedora and not on EL6 or EL7, and the reason for that are missing dependencies on both EPEL6 and EPEL7. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The basic idea here is to put all common requirements on a common line and deal with the differences in conditional blocks. Also, python-flexmock is not available on EPEL 7, but available on all other supported platforms. Finally, python-yaml and PyYAML are in their own lines because it makes it easier to see that they're the same package with different names. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This means that we include the Makefile in the source tarball and just use the `man` target. With regards to portability among Python version, this should not be an issue as rst2man on the system itself will the correct version. In a sense, it's just another utility, it doesn't really matter it's written in Python. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
There are two reasons for introducing this new target: 1) It adds symmetry to the Debian targets, which have both source only and complete versions. 2) It is useful when you only want to make the source package and build the "binary" elsewhere. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
avocado.remote: Add support for host-timeout [v2]
-
- 29 3月, 2015 1 次提交
-
-
由 Lukáš Doktor 提交于
Sometimes avocado on guest hangs. This patch adds host timeout to interrupt the execution. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 28 3月, 2015 6 次提交
-
-
由 Cleber Rosa 提交于
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
To help users to understand what each config option does. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Cleber Rosa 提交于
-
由 Lucas Meneghel Rodrigues 提交于
Those are not necessary in the avocado options and can safely stay as a config file only option. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
The option --relative links instructed the htmlresult plugin whether to use absolute log paths in anchor tags, or to use relative paths, something that dates back to the old autotest html job report. After thinking about it I realized that this option doesn't need to be here, as using relative links is basically better for all intents and purposes (the job results can be safely redistributed and the report would still work). So get rid of that option and always use relative links for the job results dir links and logs. Tested with local execution as well as remote/vm execution. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 27 3月, 2015 13 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Include virt API on readthedocs.org
-
由 Cleber Rosa 提交于
This patch will checkout the avocado-virt repo during the documentation build, so that all of avocado's API (including -virt) is presented at a single and comprehensive location. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The following things were changed and for the following reasons: 1) Remove the current hack to force the program name at the module entry point, for obvious reasons. 2) Return the exit status code, for obvious reasons. 3) Add some safety with a `__main__` check, because Sphinx will load the avocado module in such a way that the avocado app is run and the build fails. This is true on my system, and may be the case on others. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
avocado.aexpect: Fix bugs that broke avocado-virt
-
由 Lucas Meneghel Rodrigues 提交于
Let's try to avoid mistakes by explaining that we should not use avocado imports in the stand alone part of the aexpect module. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
We can't require avocado imports in the server part of the aexpect process because that will be executed stand alone, and will not have access to the rest of the avocado libraries. The bugs were introduced in commits: 6f380e0d 3fa9077f This patch fixes the problem by moving the imports to the client side of the module. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Remove another seldomly used option, --job-log-level, and move the opportunity to set the value to the config file. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
It is not a widely used option, so it's better to keep it in runner.behavior.keep_tmp_files config. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Bugfixes 26/03/2015
-
由 Lucas Meneghel Rodrigues 提交于
In the local runner, we use the multiplexer, but not so in remote runner mode. Let's add the compatibility option here to resolve the bug that broke the remote plugin. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
-
由 Lucas Meneghel Rodrigues 提交于
-
由 Lucas Meneghel Rodrigues 提交于
Review command line options. [V5]
-