From Fedora Project Wiki
(New page: = Jan Hutař = jhutar@redhat.com [http://www.cz.redhat.com/ Red Hat Czech] - QA engineer) |
No edit summary |
||
Line 1: | Line 1: | ||
= Jan Hutař = | = Jan Hutař = | ||
jhutar@redhat.com | [mailto:jhutar@redhat.com jhutar@redhat.com] | ||
[http://www.cz.redhat.com/ Red Hat Czech] - QA engineer | [http://www.cz.redhat.com/ Red Hat Czech] - QA engineer | ||
== Inasnum - Fedora package sanity checker == | |||
* '''prepare phase''' - failure terminates test | |||
* server prepares a job | |||
* gets new packages list for an pending advisory (e.g. [https://admin.fedoraproject.org/updates/F9/FEDORA-2008-6415 FEDORA-2008-6415] - [http://koji.fedoraproject.org/koji/buildinfo?buildID=55526 drupal-6.3-1.fc9]) using [https://fedorahosted.org/bodhi/ Bodhi] and [https://fedorahosted.org/koji/ Koji] | |||
* creates ''repo_advisory'' with packages from the advisory (from Koji) | |||
* creates ''new_advisory.list'' file with `N E V R A` of the packages from the advisory | |||
* creates ''new_src_advisory.list'' file with `N E V R A` of the source package(s) from the advisory | |||
* updates ''repo_update'' - just mirror of oficial Fedora Updates repo | |||
* server creates a LVM snapshot where the clinet will be stared | |||
* client boots up and updates itself from the ''repo_update'' repo | |||
* '''test phase''' | |||
* client queries a job from server, do the test with packages from the ''repo_advisory'' repo | |||
* all new packages installable/updatable? | |||
* no rpm verification issues or only whitelisted ones? | |||
* are these packages rebuidable? | |||
* no file-conflicts? | |||
* ... | |||
* report results to the server | |||
* '''clean up phase''' | |||
* server destroys test system, delete its snapshot partition | |||
== rpmfluff == | |||
'''rpmfluff''' is a lightweight way of building RPMs, and sabotaging them so they are broken in controlled ways. | |||
It is intended for use when testing RPM-testers e.g. rpmlint and writing test cases for RPM tools e.g. yum | |||
See: https://fedorahosted.org/rpmfluff |
Revision as of 06:31, 8 September 2008
Jan Hutař
Red Hat Czech - QA engineer
Inasnum - Fedora package sanity checker
* prepare phase - failure terminates test * server prepares a job * gets new packages list for an pending advisory (e.g. FEDORA-2008-6415 - drupal-6.3-1.fc9) using Bodhi and Koji * creates repo_advisory with packages from the advisory (from Koji) * creates new_advisory.list file withN E V R A
of the packages from the advisory * creates new_src_advisory.list file withN E V R A
of the source package(s) from the advisory * updates repo_update - just mirror of oficial Fedora Updates repo * server creates a LVM snapshot where the clinet will be stared * client boots up and updates itself from the repo_update repo * test phase * client queries a job from server, do the test with packages from the repo_advisory repo * all new packages installable/updatable? * no rpm verification issues or only whitelisted ones? * are these packages rebuidable? * no file-conflicts? * ... * report results to the server * clean up phase * server destroys test system, delete its snapshot partition
rpmfluff
rpmfluff is a lightweight way of building RPMs, and sabotaging them so they are broken in controlled ways.
It is intended for use when testing RPM-testers e.g. rpmlint and writing test cases for RPM tools e.g. yum