1. 23 6月, 2015 2 次提交
  2. 15 6月, 2015 1 次提交
  3. 10 6月, 2015 1 次提交
  4. 09 6月, 2015 5 次提交
    • C
      docs: simplify Writing Avocado Test section text · b3788c8a
      Cleber Rosa 提交于
      After reading the text and shuffling the order a bit, I think this
      has an easier to follow structure. A few highlights:
      
      * An Avocado test is really a method, that is, for many methods we
        have many tests.
      * Suppress the attempt to briefly explain the Multiplexer here,
        giving instead a link to a more complete documentation.
      
      Changes from v1:
      * Mention the function naming conventions for the test methods and
        link to PEP 8 relevant section for functions and classes.
      * Break into finer grained sections.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      
      [fixup] docs: simplify Writing Avocado Test section text
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      b3788c8a
    • C
      docs: simplify basic example on Writing Tests Guide · 3c80903c
      Cleber Rosa 提交于
      The idea is to remove everything that is not critical to the user's
      understanding of the core concepts.
      
      Also, to sync to the new multi-test in a single class capabilities
      of Avocado, let's name the main test method `test`. This paves the
      way for other (multi test) examples that name test methods with
      the exact same prefix (test_foo, test_bar and so on).
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      3c80903c
    • C
      docs: reorganization of the Writing Tests section · e01a0d4e
      Cleber Rosa 提交于
      This includes moving the reference text and diagram on test order
      resolution to the Reference Guide. Since this also included
      information on what are simple and instrumented tests, let's
      merge and reuse that.
      
      Also, let's rename "Simple example" to "Basic example" so that it
      does not confuse users with the concept of a Simple Test, since this
      example is actually an Instrumented Test.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      e01a0d4e
    • C
      docs: replace avocado (lowercase) with Avocado (capitalized) · ce4cd9ef
      Cleber Rosa 提交于
      Since Avocado in our context is a proper name, and not really just
      some fruit, let's refer to it using a capitalized word.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      ce4cd9ef
    • C
      API review: move avocado.test to avocado.core.test and expose avocado.Test · 08810698
      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>
      08810698
  5. 02 6月, 2015 1 次提交
    • L
      avocado.multiplexer: Inject YAML files into /run · 3e5cbc85
      Lukáš Doktor 提交于
      This patch changes the default mux-entry to `/run` as it tends to be
      more convenient.
      
      The biggest change is that this location is used as default location
      for added YAML files. It's also used as the base when using relative
      path YAML file injection. The only way to include file into the exact
      location is to use absolute path (`/your/location`).
      
      The benefit is that single simple YAML file doesn't require any additional
      location and is in the default mux-entry location. Check the documentation
      for details.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      3e5cbc85
  6. 20 5月, 2015 1 次提交
  7. 16 5月, 2015 2 次提交
    • L
      avocado.multiplexer: Switch to the new API · d727bfe0
      Lukáš Doktor 提交于
      This patch adds documentation of the "new params API" and removes the
      compatility layer. From now on only the API with paths is valid:
      
          self.params.get(key, path='*', default=None)
      
      where the default path '*' matches anything from --mux-entry path.
      Default path is `/test`.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      d727bfe0
    • L
      examples.tests: Adjust tests to use new params API · 8e2ddf58
      Lukáš Doktor 提交于
      This patch modifies all example tests to use the new API. It uses the
      default path, which is `*`, which matches the mux-entry paths ONLY.
      In order to get the values it's necessarily to inject the YAML files
      into the mux-entry path, by default `/test`, eg:
      
          avocado run sleeptest -m /test:examples/tests/sleeptest.py.data/
          sleeptest.yaml
      
      It might seen as a bit more complicated to execute, but it's definitely
      easier for maintaining and combining existing YAML files. To execute
      matrix of tests you simply inject them into 2 different `/test` children,
      eg: `-m /test/by_length:lengths.yaml /test/by_method:methods.yaml`.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      8e2ddf58
  8. 24 4月, 2015 2 次提交
  9. 10 4月, 2015 1 次提交
  10. 08 4月, 2015 1 次提交
  11. 25 3月, 2015 1 次提交
    • L
      scripts.avocado-bash-utils: Add Avocado bash utils · fa0e77a7
      Lukáš Doktor 提交于
      This patch is initial support for people using custom bash scripts
      with avocado. Tests should use:
      
          PATH=$(avocado "exec-path"):$PATH
      
      and then they can utilize the helpers.
      
      This version contain functions to write to Test.log the same way it's
      possible from python including failing the test with TestWarn in case
      avocado_warn was used.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      fa0e77a7
  12. 20 3月, 2015 1 次提交
  13. 26 2月, 2015 1 次提交
  14. 03 2月, 2015 1 次提交
    • R
      avocado: Add support for recursively finding tests in a directory · f95dc31b
      Rudá Moura 提交于
      Add support to inspect and find tests inside a directory, recursively,
      by using the method `discover_url`. It takes a url (path) and
      returns the tests parameters it discovers.
      
      The loader object has the .discover() method, that can be used
      to inspect the location, and the .validate() method, that will
      discover any problems on the user's input.
      
      We are also changing the behavior of avocado to error out on
      invalid inputs (missing paths or files that are not avocado
      tests). Therefore, the concept of MISSING or NOT_A_TEST both
      disappear from the UI. Unittests were updated to reflect the
      new status quo.
      Signed-off-by: NRudá Moura <rmoura@redhat.com>
      Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
      f95dc31b
  15. 23 1月, 2015 1 次提交
  16. 22 1月, 2015 1 次提交
  17. 16 12月, 2014 1 次提交
  18. 15 12月, 2014 3 次提交
  19. 11 12月, 2014 1 次提交
  20. 04 12月, 2014 1 次提交
  21. 08 10月, 2014 1 次提交
  22. 02 10月, 2014 1 次提交
  23. 01 10月, 2014 1 次提交
  24. 30 9月, 2014 1 次提交
  25. 26 9月, 2014 1 次提交
  26. 17 9月, 2014 2 次提交
  27. 29 8月, 2014 1 次提交
  28. 13 8月, 2014 1 次提交
  29. 07 8月, 2014 1 次提交
  30. 18 7月, 2014 1 次提交