- 07 7月, 2015 5 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Give to test writers the fail_on_error decorator, which should turn any generic exception into an avocado TestFail. This is important for some tests that can raise any exception during a complex operation, and any of those exceptions can be considered a test failure. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Explain that skip() can only be called from inside setUp(), and tell the expected avocado behavior when writers don't follow that rule. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Make sure avocado complains loudly when people try to call skip() from outside setUp() - this shouldn't be allowed in avocado tests. Let the user know of the problem and ask them to fix their tests. Also, update the docstring for skip(), which will reduce the chances of test writers using it in inappropriate places. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Have the clear definition of each test status in the ReferenceGuide. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
In order to keep things simple and clear, enforce the following test results rules: * `PASS`: the test passed, which means all conditions being tested have passed. * `FAIL`: the test failed, which means at least one condition being tested has failed. Ideally, it should mean a problem in the software being tested has been found. * `ERROR`: an error happened during the test execution. This can happen, for example, if there's a bug in the test runner, in its libraries or if a resource breaks unexpectedly. Uncaught exceptions in the test code will also result in this status. * `SKIP`: the test runner decided a requested test should not be executed. This can happen, for example, due to missing requirements in the test environment or when there's a job timeout. In order to do that, let's not make the behavior on exceptions other than TestFail to be configurable. Therefore, the config value uncaught_exception_result must be removed and the status of the test always be 'ERROR'. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 30 6月, 2015 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Execution of tests remotely copies tests unnecessarily
-
- 26 6月, 2015 6 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
avocado.core.plugins: Rename --env and improve --mux-path desc [v2]
-
由 Lukáš Doktor 提交于
--env injects node/key/values into the multiplexed tree. It's 100% related to mux therefor --mux-inject would better reflect the functionality. The --mux-path description was rather misleading, hopefully this will help users to get better notion (although reading the documentation is still preferred). Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Cleber Rosa 提交于
run_suite() actually happens earlier, and is only called once, so it seems to be a better place for the check of Avocado on the remote system. If this condition holds true, then copy the requested tests to the remote system. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The result.setup() method is now only used to setup the communication channel, and the copy of the tests will be made conditional, based on the presence of Avocado on the remote machine. On the unittest side, I'm quite adverse to heavy mocking, so I favored removing all these painful, and IMHO of little value checks. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Instead of copying the entire test directory, let's only copy the selected test and it's data directory. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This method should really return earlier if wasn't asked to copy file to remote side, that is, there's no need to create that directory in those cases. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 25 6月, 2015 4 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Usability fixes on "$ avocado run --help"
-
由 Cleber Rosa 提交于
This is a collection of little small touches that, IMHO, add a little bit more consistency to the plugins involved in the Avocado `run` command. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The command line options and documentations refer to "process", "applications", etc. It's more natural to think and describe them as "executables" instead. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The command line options and documentations refer to "binaries" a lot, with options descriptions such as BINARY_PATH. It's more natural to think and describe them as "executables" instead. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 24 6月, 2015 8 次提交
-
-
由 Cleber Rosa 提交于
-
由 Lucas Meneghel Rodrigues 提交于
API docs: generate separate sections for the 3 modules boundaries
-
由 Cleber Rosa 提交于
Avocado currently has 3 very distinct namespaces boundaries: test API, utils, and core. Let's create 3 separate sections so that users know which one(s) they could use for a given task. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The introduction was meant to be kept shorter, without the bullet point items, because proper descriptions are in the inner sections. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Documentation Review (4th round, v2)
-
由 Lucas Meneghel Rodrigues 提交于
Whenever we use remoter.Remote(), our wrapper to fabric inside tests, we end up losing information that could be used for debugging purposes. Let's introduce an remote related log to the avocado test results dir (remote.log), that will be populated if remoter.Remote() is used. With this patch, tests that use remoter.Remote() (avocado-virt) will have better debugging information available. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
In order to troubleshoot more effectively problems happening in remote/vm operations, make all output coming from fabric and paramiko to a 'remote.log' file in the top level job directory. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
In order to let multiple loggers to get the same information, let the LoggingFile object to accept a list of loggers, rather than a single one. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 23 6月, 2015 16 次提交
-
-
由 Cleber Rosa 提交于
This is obviously about Avocado, and just having "Configuration" makes it easier on the brain and on the eyes. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
As listing plugins is already mentioned in other sections, and documentation on writing a plugin is probably the last thing a regular user would look for. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This basically brings changes in wording and updates to command line outputs. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This basically brings changes in wording and updates to command line outputs. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Into a new section named "Running Tests Remotely". Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This doesn't seem to be the best place for this piece of information. Let's remove it for now, and it may (or may not) have a place somewhere else. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
At its core, what's really important to get accross is that an Avocado test is compatible with unittest.TestCase, and it can be run with compatible test runners. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
We don't implement all of unittest, but rather inherit from the TestCase class. Let's also fix the references to the assert* methods. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The given example was using the old test module/class. Also, for clarity sake, let's add the "new" import style for the Avocado Test class. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Including groupping together the "human" results and then "machine" result formats in another subsection. Changes from v1: * Wording suggestion: "on how to write a plugin" instead of "on how to write plugin" Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
We don't want users to care if some core feature is implemented as a plugin. The important piece of information here is that Avocado allows for its result to be written in different formats. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Besides updating the command outputs to match the current code, the text was attempted to be made simpler and easier to follow. Also, some sections were made subsections of the "Writing a plugin" section. Changes from v1: * Fix "lien" (instead of "line") typo Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The output of the plugins command has changed. It now includes plugins that may fail to load or even have been disabled (usually by themselves). Let's make the user aware of these new possibilities and update the UI examples. Changes from v1: * Fix wording suggestion of "cleaner" instead of "clean" Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Makefile: New `link_vt` and `link_virt` targets
-
由 Lucas Meneghel Rodrigues 提交于
Add a little more granularity to our Makefile. 'make link' still works the way one would expect it to. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-