Skip to content

A
avocado

openeuler / avocado

通知 0
Star 0
Fork 0
A
avocado

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 03 3月, 2016 1 次提交
  3. 02 3月, 2016 1 次提交
  5. 29 2月, 2016 2 次提交
    • C
      Test: remove get_data_path utility API · 58dea874
      由 Cleber Rosa 提交于 
      The get_data_path utility API of the Test class is a convenience,
it simply joins the name of a given file to the datadir location.

IMHO the value is low when compared to the pollution of the namespace
and yet another compatibility/stability promise.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      58dea874
    • C
      Test: remove stdout_log and stderr_log attributes · 09ed812b
      由 Cleber Rosa 提交于 
      These two attributes are simply utility logger instances that test
writers can use to write "directly" to the test process' STDOUT and
STDERR.

I agree that having those ready to use inside a test is a nice to
have, but I don't think it justifies the polution to the test class
namespace.

Let's remove those and document how the user can use Python's standard
logging API to retrieve the logger instances that Avocado provides to
tests. This will continue to exist and be supported.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      09ed812b
  7. 12 2月, 2016 1 次提交
  9. 20 1月, 2016 1 次提交
  11. 16 1月, 2016 1 次提交
  13. 08 1月, 2016 4 次提交
  15. 05 1月, 2016 1 次提交
  17. 23 12月, 2015 3 次提交
  19. 19 12月, 2015 1 次提交
  21. 18 12月, 2015 1 次提交
  23. 07 12月, 2015 1 次提交
    • C
      virtualenv: allow tests to run properly on them · 63aa6df6
      由 Cleber Rosa 提交于 
      While going through the dependency list (requirements*.txt files) and
performing our self tests out of virtual environments, I noticed that
some tests are run outside the virtual environments.

The reason is that, even though the virtual environment is activated
for the test session (and say, `which python` gives `/venv/bin/python`),
we have hard coded `/usr/bin/python` in most places.

According to the some discussions on the virtualenv project itself[1],
a quick solution is to revert to the also common `/usr/bin/env python`
way of pointing to the Python interpreter.

[1] - https://github.com/pypa/virtualenv/issues/124Signed-off-by: NCleber Rosa <crosa@redhat.com>
      63aa6df6
  25. 19 11月, 2015 1 次提交
  27. 05 11月, 2015 2 次提交
  29. 30 10月, 2015 1 次提交
    • L
      avocado: Add support for --dry-run · 069e3784
      由 Lukáš Doktor 提交于 
      It's prone to mistakes maintain two separate ways to query for tests
(running them and displaying available ones).

This patch implements --dry-run, which follows the full "run" process,
only instead of running the test it skips them.

Additionally the --dry-run uses some tweaks to tell them apart from
normal executions, namely:

    1. No sysinfo gathering
    2. Unique id is 0000000000000000000000000000000000000000
    3. Unless user provides custom log location, fresh tmpdir is used
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      069e3784
  31. 28 10月, 2015 1 次提交
    • C
      Plugins: remove external plugin support · 7b969527
      由 Cleber Rosa 提交于 
      In preparation for the large plugin refactor, let's simplify the code ASAP
and drop related (custom) functionality that is going to be replaced.

Standard setuptools entrypoints is going to provide better capability then
our custom code that supports external 'avocado_*.py'module loading.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      7b969527
  33. 27 10月, 2015 1 次提交
  35. 08 10月, 2015 1 次提交
  37. 07 10月, 2015 5 次提交
  39. 05 10月, 2015 2 次提交
  41. 02 10月, 2015 2 次提交
  43. 01 10月, 2015 2 次提交
    • C
      Test Loader: drop support and remove all mentions of BUGGY tests · 153497f7
      由 Cleber Rosa 提交于 
      The BUGGY test concept relies on loading/executing the Python file
containing the tests and failing to do so. Since Avocado won't
load/execute Python test files anymore, it's not possible or desirable
to keep the BUGGY tests around.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
      153497f7
    • L
      avocado.core.loaders: Make it possible to specify test loaders · fddbd88c
      由 Lukáš Doktor 提交于 
      Currently we can only specify the loader plugins order via settings.
This patch adds "--loaders" argument and improves the granularity.
Now it's possible to set either @plugin_name, or TEST_TYPE, where
TEST_TYPE is the mapped name of the plugin (eg. SIMPLE, VT, ...)

There is one special name "DEFAULT", which injects all unspecified
loaders in the position of the "DEFAULT" keyword. When "DEFAULT" is
not specified, not-listed plugins/test_types are not evaluated.
(therefor it's possible to restrict some test loaders or only some
test types).

As the usecase changed slightly, the settings option was renamed
from plugins.loader_plugins_priority to plugins.loaders.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      fddbd88c
  45. 30 9月, 2015 2 次提交
  47. 11 9月, 2015 1 次提交
  49. 08 9月, 2015 1 次提交