Hi folks, thanks for your feedback in the last few days. I've created two wiki pages about packages which don't execute their tests in %check: https://fedoraproject.org/wiki/QA/Testing_in_check
and another one for packages which don't seem to have test suites at all: https://fedoraproject.org/wiki/QA/Missing_upstream_test_suites
My intent is for these pages to serve as a source of working material for Fedora volunteers.
Note: there are some false negatives which I still haven't filtered out - work in progress.
Please forward this to anyone who may be interested to work on these items as we need lots of hands to make any significant improvements! (In particular I will soon teach to students and will point them here).
Any comments and proposals are welcome!
Thanks, Alex
On Thu, Feb 27, 2014 at 03:55:02PM +0200, Alexander Todorov wrote:
Hi folks, thanks for your feedback in the last few days. I've created two wiki pages about packages which don't execute their tests in %check: https://fedoraproject.org/wiki/QA/Testing_in_check
Of the two packages that have 'virt' in their title, it looks like virt-manager genuinely contains tests upstream but they are not enabled in Fedora. Actually some tests fail in Fedora 20.
Attached is a proposed patch to the spec file. I ran this under auto-buildrequires to see if it would need any extra BRs, but auto-br didn't find any.
I didn't want to push it because I have approximately no idea what I'm doing with python / virt-manager & tests.
and another one for packages which don't seem to have test suites at all: https://fedoraproject.org/wiki/QA/Missing_upstream_test_suites
virt-viewer is mentioned in this list. Not sure how that could be meaningfully tested since it requires an X11 display and a network connection to a VM.
Keep up the good work,
Rich.
На 27.02.2014 16:18, Richard W.M. Jones написа:
Attached is a proposed patch to the spec file. I ran this under auto-buildrequires to see if it would need any extra BRs, but auto-br didn't find any.
Richard, can you point me to what auto-buildrequires is, where it lives and how do I use it? I don't seem to have it on my system or I'm blind and don't know where to look for it.
and another one for packages which don't seem to have test suites at all: https://fedoraproject.org/wiki/QA/Missing_upstream_test_suites
virt-viewer is mentioned in this list. Not sure how that could be meaningfully tested since it requires an X11 display and a network connection to a VM.
Mock this :). Of course it depends on the nature of bugs which are usually filed against virt-viewer and mocking could be just an overkill (or not at all possible).
PS: I will update these wiki pages with links to bugzilla.
-- Alex
On Thu, Feb 27, 2014 at 05:49:05PM +0200, Alexander Todorov wrote:
На 27.02.2014 16:18, Richard W.M. Jones написа:
Attached is a proposed patch to the spec file. I ran this under auto-buildrequires to see if it would need any extra BRs, but auto-br didn't find any.
Richard, can you point me to what auto-buildrequires is, where it lives and how do I use it? I don't seem to have it on my system or I'm blind and don't know where to look for it.
http://people.redhat.com/~rjones/auto-buildrequires/
It's also packaged in Fedora (auto-buildrequires).
Run it like this:
fedpkg srpm # to build an srpm auto-br-rpmbuild --rebuild --define "_sourcedir $(pwd)" *.src.rpm
and it will build the package and suggest a list of BuildRequires at the end.
Rich.
On 02/27/2014 09:18 AM, Richard W.M. Jones wrote:
On Thu, Feb 27, 2014 at 03:55:02PM +0200, Alexander Todorov wrote:
Hi folks, thanks for your feedback in the last few days. I've created two wiki pages about packages which don't execute their tests in %check: https://fedoraproject.org/wiki/QA/Testing_in_check
Of the two packages that have 'virt' in their title, it looks like virt-manager genuinely contains tests upstream but they are not enabled in Fedora. Actually some tests fail in Fedora 20.
Unfortunately our 'unit test' suite depends on host libvirt version in some capacity. I try to weed out the version dependencies as they pop up, but it means sometimes the test suite is broken depending on the libvirt version.
For that reason enabling the test suite in the spec is a pain since a libvirt update in rawhide followed by a virt-manager rebuild might fail since the test suite has diverged. We can ignore failure, like your patch does, but that doesn't seem to valuable besides slowing down the build.
Attached is a proposed patch to the spec file. I ran this under auto-buildrequires to see if it would need any extra BRs, but auto-br didn't find any.
It will need to duplicate BuildRequires for all the virt-manager-common deps at least.
- Cole
Interesting :
fedora-release-notes
***-fonts
Can someone point me how to test them?
На 27.02.2014 18:14, Christopher Meng написа:
Interesting :
fedora-release-notes
***-fonts
Can someone point me how to test them?
See amiri-fonts, gnu-free-fonts and thai-scalable-fonts. These appear to have some sort of testing available in the source and all three seem to be different. Maybe that will give you a place to start.
Otherwise look at the bugs for a particular package (wiki updated with links to Bugzilla) and figure out what kind of bugs are the most common ones. If there's a pattern it is likely possible it can be automated.
-- Alex
packaging@lists.fedoraproject.org
-
Alexander Todorov -
Christopher Meng -
Cole Robinson -
Richard W.M. Jones