1. 10 5月, 2016 2 次提交
  2. 05 5月, 2016 1 次提交
  3. 02 5月, 2016 2 次提交
  4. 27 4月, 2016 4 次提交
  5. 26 4月, 2016 2 次提交
    • C
      Job Script Plugin: allow user scripts to be run pre/post job · b9cc7abe
      Cleber Rosa 提交于
      This script introduces a pair of directories that will be searched
      for executable files, to be run before and after the actual execution
      of a job.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      b9cc7abe
    • C
      Plugins: Introduce Pre and Post Job Execution Plugins · 6ea85516
      Cleber Rosa 提交于
      These new plugin interfaces, to be registered under the
      'avocado.plugins.job.prepost' namespace, allow for any custom action
      to be executed before and/or after the job execution.
      
      The JobPre plugin interface requires the `pre` method to be
      implemented, while the JobPost plugin interface requires the `post`
      method to be implemented.  The separation of the interfaces allows for
      mandatory implementation of the given interfaces, which was the whole
      point of using Abstract base classes, instead of having empty default
      implementations.
      
      One single class may implement either one, or both of those
      interfaces.  Both `pre` and `post` methods receive the current Job
      instance as an argument, which allows the plugin to fetch any job
      information or even to tweak as it may seem fit.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      6ea85516
  6. 25 4月, 2016 1 次提交
  7. 20 4月, 2016 1 次提交
  8. 19 4月, 2016 1 次提交
  9. 14 4月, 2016 1 次提交
  10. 13 4月, 2016 1 次提交
  11. 18 3月, 2016 1 次提交
  12. 17 3月, 2016 1 次提交
  13. 16 3月, 2016 1 次提交
  14. 09 3月, 2016 1 次提交
  15. 03 3月, 2016 1 次提交
  16. 02 3月, 2016 1 次提交
  17. 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
  18. 12 2月, 2016 1 次提交
  19. 20 1月, 2016 1 次提交
  20. 16 1月, 2016 1 次提交
  21. 08 1月, 2016 4 次提交
  22. 05 1月, 2016 1 次提交
  23. 23 12月, 2015 3 次提交
  24. 19 12月, 2015 1 次提交
  25. 18 12月, 2015 1 次提交
  26. 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
  27. 19 11月, 2015 1 次提交
  28. 05 11月, 2015 1 次提交