- 07 4月, 2015 1 次提交
-
-
由 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>
-
- 22 1月, 2015 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Now that we don't enforce a silly correspondence test module name -> class name, we can call our test classes whatever we want as long as it inherits from avocado.test.Test. Let's then rename our tests to something more CamelCase. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 28 11月, 2014 1 次提交
-
-
由 Rudá Moura 提交于
Remove the license text from files inside docs, examples and selftest, to keep the license text only in relevant parts of the project. References: * https://fedoraproject.org/wiki/Packaging:LicensingGuidelines * https://www.gnu.org/licenses/gpl-howto.htmlSigned-off-by: NRudá Moura <rmoura@redhat.com>
-
- 12 9月, 2014 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
We have tests/ and selftests/ in avocado (the test runner). The former includes examples of tests that make use of the avocado API, and are also used to test avocado via CI. This is confusing, as it doesn't make it clear to users that tests are not part of the avocado framework. Since we have a directory called examples with some other files (multiplexer, plugins), move the tests to there (and keep using them in the CI). Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 29 7月, 2014 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
We want avocado tests to not require specific directories, the user should be able to arrange them in the dir structure they see fit. Also, if a test requires data, we suppose their data dir is located in the same directory as the source file, with the name: [modulename].data Re arrange the test dir to reflect this new structure. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 08 5月, 2014 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
They raise the following exceptions: 1) TestError (failure) 2) TestNAError (skip) 3) TestWarn (failure) The corresponding functional tests for them go in the Travis CI file. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 25 4月, 2014 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 24 4月, 2014 1 次提交
-
-
由 Rudá Moura 提交于
Improvements for using xUnit with Jenkins (Junit). Now the actual XML result is handled in class XmlResult. Also minor fix (cosmetics) in tests.failtest. Signed-off-by: NRuda Moura <rmoura@redhat.com>
-
- 23 4月, 2014 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
I went through all python files in avocado code, and some changes were made: * Files entirely written by the current avocado dev team were changed to be GPL v2+ * Files with a significant portion of code derived from autotest remain GPL v2 strict, and original authorship was re-established Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 10 4月, 2014 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 26 3月, 2014 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Introduce the job.main() entry point in all avocado test modules. This way all of them can be executed. The functionality depends on having avocado installed system wide, though. Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-
- 12 3月, 2014 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
-
- 08 3月, 2014 1 次提交
-
-
由 Lucas Meneghel Rodrigues 提交于
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
-