autoqa-devel January 2010

autoqa-devel@lists.fedorahosted.org

5 participants
50 discussions

[AutoQA] #102: post-iso-build hook
by fedora-badges 03 Aug '11

03 Aug '11

#102: post-iso-build hook ----------------------+----------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: watchers | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- We need one (or more) standard locations where new iso images get posted for testing, and a watcher that can monitor for new iso images and launch appropriate installation/sanity tests. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/102> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #104: virtguest.py: accept iso image(s) as install location
by fedora-badges 21 Jul '11

21 Jul '11

#104: virtguest.py: accept iso image(s) as install location --------------------+------------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- allow {{{VirtGuest.create()}}} to use an iso image (or images) for its {{{location}}} arg, and automatically choose the appropriate {{{--location URL}}} or {{{--cdrom IMAGE}}} flag. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/104> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #111: depcheck test
by fedora-badges 28 Aug '10

28 Aug '10

#111: depcheck test --------------------+------------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: autoqa depcheck Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- Write an actual depcheck test. This test should take, as inputs: * one or more new package builds, and * the name of a target repository for the new build(s) The test should examine the PRCO (provides/requires/conflicts/obsoletes) data for the new package(s) and the PRCO data for the target repository (and all its parent repos). The test should fail if the new builds would cause missing/broken dependencies or unresolveable conflicts in the target repo(s). -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/111> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 8

[AutoQA] #118: New test proposal: Python debugability
by fedora-badges 06 Aug '10

06 Aug '10

#118: New test proposal: Python debugability --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: minor | Milestone: Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- From Adam Williamson: I've cut some of the context, but basically David wants to write a test case for checking whether Python debugging is possible as intended, and I asked exactly how he wanted it to be used. {{{ On Tue, 2010-01-26 at 15:30 -0500, David Malcolm wrote: > > > Can I request a test case to cover debuggability of the Python > runtime > > > please (both in Fedora and in RHEL). > > > > > > This is in relation to: > > > https://bugzilla.redhat.com/show_bug.cgi?id=556975 > > > https://bugzilla.redhat.com/show_bug.cgi?id=558977 > > > https://bugzilla.redhat.com/show_bug.cgi?id=557772 > > > > > > as there seem to be gcc and gdb issues, which are conspiring to > make > > > python impossible to debug. > > > > > > > > > The requirement is: within "gdb python", I must be able to select > a > > > PyEval_EvalFrameEx frame, and have the following work: > > > (gdb) print co > > > (gdb) print f > > > > > > rather that have <variable optimized out> > > > > > > so that I can do this: > > > (gdb) print (char*)(((PyStringObject*)co->co_name)->ob_sval) > > > to get the function name > > > > > > (gdb) print (char*)(((PyStringObject*)co->co_filename)->ob_sval) > > > to get the source filename > > > > > > and > > > > > > (gdb) print f->f_lineno > > > to get the approximate source line number. > > > > > > If the above isn't working, it becomes extremely hard to > meaningfully > > > debug any issues that arise inside Python. > This is probably scriptable, and a good candidate for AutoQA and foe > RHTS. > }}} -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/118> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #107: writing a python test (modeled similarly to install.py)
by fedora-badges 23 Jul '10

23 Jul '10

#107: writing a python test (modeled similarly to install.py) -------------------+-------------------------------------------------------- Reporter: liam | Owner: Type: task | Status: new Priority: major | Milestone: Component: tests | Version: 1.0 Keywords: | -------------------+-------------------------------------------------------- write a python test (modeled similarly to install.py) that takes as input: * a URL to a kickstart file (URL can be local (e.g. file://) or remote (e.g. http://, ftp://, nfs:// ...) ... but start with easy case first. * a URL for the install media (again, keep this simple for now and assume file:///var/lib/libvirt/images/Fedora-12-x86_64-DVD.iso) * a URL to a configuration file that describes the environment - again, perhaps optional for now. But eventually we'll need something that tells the test to create a guest with 4 NICs vs 1 NIC, 3 SCSI drives etc... Don't worry about being fancy at first ... just take the defaults. This is just where I might see it headed in 6+ months. Copy from the kvm autotest project if you like. At beginning, we focus on the basics and something that gets things far enough along so we can review, adjust and repeat. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/107> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 10

[AutoQA] #115: Update post-tree-compose to recognize new stage2 URL
by fedora-badges 21 Jul '10

21 Jul '10

#115: Update post-tree-compose to recognize new stage2 URL -------------------------+-------------------------------------------------- Reporter: jlaska | Owner: Type: enhancement | Status: new Priority: major | Milestone: Automate installation test plan Component: watchers | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- During Fedora 13, release engineering will provide schedule drops of rawhide for automated testing against rats_install. The provided data will include a compose tree (without packages). For proper automated testing of these images, post-tree-compose will need to monitor a new URL for testing (likely candidate is http://alt.fedoraproject.org/pub/alt/stage/rawhide-testing) In addition, rats_install will need to support installing with stage2 and the package repo in different locations. That will be tracked in another ticket. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/115> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #109: post-bodhi-update watcher
by fedora-badges 26 Jun '10

26 Jun '10

#109: post-bodhi-update watcher ----------------------+----------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: autoqa depcheck Component: watchers | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- the post-bodhi-update hook (see ticket #87) will require a post-bodhi- update watcher. This should use the bodhi API to get info about newly- created/changed updates and fire tests. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/109> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 8

[AutoQA] #106: create disk images for tests requiring pre-existing disk data
by fedora-badges 19 May '10

19 May '10

#106: create disk images for tests requiring pre-existing disk data --------------------+------------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- Some installation tests require existing disks with some data - either an old version of Fedora to upgrade, or certain disk partitions to be reused/replaced. For example: * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_New_Bootloader * https://fedoraproject.org/wiki/QA:Testcase_Preupgrade * https://fedoraproject.org/wiki/QA/TestCases/PartitioningPreExistingLvm2Lvm2 etc. We should either have a library of methods for creating these disks, or keep stock disk images for this purpose. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/106> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #103: virtguest.py: pass in extra boot args
by fedora-badges 29 Apr '10

29 Apr '10

#103: virtguest.py: pass in extra boot args --------------------+------------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- the !VirtGuest class needs a way to pass in extra boot args (for example {{{rescue}}} or {{{updates=XXX}}}) for various test cases. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/103> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #100: virtguest.py: allow some way to override/extend the kickstart passed to the guest
by fedora-badges 01 Apr '10

01 Apr '10

#100: virtguest.py: allow some way to override/extend the kickstart passed to the guest --------------------+------------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- In order to automate most of the test cases in the installation test plan, we need to be able to pass custom kickstart commands to a newly-created virt guest. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/100> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel January 2010