- 14 12月, 2018 3 次提交
-
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
- 13 12月, 2018 8 次提交
-
-
由 Cleber Rosa 提交于
Up to this point, the matching and thus filtering of tags was flat. Now, the individual value of the required keys are checked. For instance, if you have a test such as: class My(Test): def test(self): """
🥑 tags=classification:tier1 """ ... Both of these filter conditions will match: $ avocado run -t classification test.py $ avocado run -t classification:tier1 test.py But this won't match: $ avocado run -t classification:tier2 test.py Also, similarly to the how there's support for including tests that have no tags at all, there's support for including tests that are not tagged with a specific keys. Signed-off-by: NCleber Rosa <crosa@redhat.com> -
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
Let's make the parsing of those tags a utility function so that its behavior can be tested in detail. Also, instead of parsing it for every test in a test suite, let's parse those only once, and using during the filter process. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
The "include_empty" parameter to test the filtering utility function is meant to act when a test with no tags is part of a test suite that also includes tests with tags. There's a current corner case when filtering with tags that must not be present and tests with no tags, when "include_empty" is active. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
In the previous addition to the AVOCADO_TEST_TAGS content, a new Avocado test to be used on unittests was added, but it was not added to assertions on some of the unittests. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
- 12 12月, 2018 13 次提交
-
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
This change introduces two new utility functions related with filesystems. One function returns all filesystem types supported by the running kernel and the other returns the filesystem type of a given mount point. Signed-off-by: NPraveen K Pandey <praveen@linux.vnet.ibm.com> Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
This basically allows us to use the same set interface for checking if a tag is in a set (the dict keys), and at the same time, allows us to have room for the values given to key:val tags. For "flat" tags, that is, ones that do not contain any value, the dictionary will just contain None, and for the key:val tags, the dictionary will contain a set of the values. The set is useful because duplicate values add no value, and a common use case is to have a base value at the class level, and have it extended in the Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
So that a failure will be easier to spot. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Let's loop over the tags once, and create the "must" and "must not" set of tags. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Praveen K Pandey 提交于
added utility which takes as argument a file and pattern and return true or false respectively when pattern matches in file or not >>> from avocado.utils import genio >>> genio.find_pattern("/home/praveen/file1", "praveen") True >>> genio.find_pattern("/home/praveen/file1", "Praveen") False >>> genio.find_pattern("/home/praveen/file12", "Praveen") Traceback (most recent call last): File "<stdin>", line 1, in <module> File "avocado/utils/genio.py", line 219, in find_pattern % (filename, pattern)) avocado.utils.genio.GenIOError: invalid file /home/praveen/file12 to match pattern Praveen >>> Signed-off-by: NPraveen K Pandey <praveen@linux.vnet.ibm.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Lukáš Doktor 提交于
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
由 Lukáš Doktor 提交于
Previous recursive implementation of waiting for children is not really possible, because parent has to treat the children exit, otherwise we get temporary zombie status until the parent process is resumed. This implementation also uses recursive way of killing the children, but instead of waiting for them to die it reports the killed processes and only in the main function it resumes all of them and watches them to die. As a benefit people might now get list of killed processes as return. Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
-
- 11 12月, 2018 3 次提交
-
-
由 Cleber Rosa 提交于
We now need to use jinja2 packages, instead of pystache. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
We only render HTML, that is, we never render anything that must not have any content escaped. So, let's always enable the autoescape feature. This fixes the issue with jinja2 version 2.7.2, available on EL 7, that has the autoescape parameter to environments, but doesn't have the select_autoescape() utility function for selecting what to escape automatically. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 10 12月, 2018 1 次提交
-
-
由 Caio Carrara 提交于
Since the pystache project seems to be dead, without recent updates and has not support planned for Python 3.7+, this change replace it by jinja template engine. Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
- 08 12月, 2018 11 次提交
-
-
由 Cleber Rosa 提交于
To a class that doesn't share the same setup requirements as the other tag filtering tests, but it's still tag filtering related. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
To the previously created TagFilter test class, as it shares the same setUp requirements. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
Into smaller tests that are hopefully easier to read and, if it occurs, much easier to understand the failure. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This lint exception is no longer necessary, let's remove it. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This seems to be a leftover, and is not used anywhere. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Cleber Rosa 提交于
This is causing a lot of ResourceWarnings, specially when running the selftests. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
The new template structure is based on Jinja template engine. Besides the template statements itself it was also split the js and css code in proper separated files. This way the results template keeps simpler. Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-
由 Cleber Rosa 提交于
It's a common use case to want to make sure a file can be read, or if not fail as early as possible with a relevant error message. The avocado.utils.iso9600 is doing that itself, but for the sake of being useful to a wider audience, let's make that a utility itself. As always, the benefits are also increased test coverage and documentation. Signed-off-by: NCleber Rosa <crosa@redhat.com>
-
- 07 12月, 2018 1 次提交
-
-
由 Caio Carrara 提交于
Signed-off-by: NCaio Carrara <ccarrara@redhat.com>
-