[AutoQA] #355: Determine Use Cases for Functional Self Tests
by fedora-badges
#355: Determine Use Cases for Functional Self Tests
---------------------------+------------------------------------------------
Reporter: tflink | Owner:
Type: task | Status: new
Priority: minor | Milestone: 0.6.0
Component: documentation | Keywords:
---------------------------+------------------------------------------------
== Description ==
In order to [ticket:352 create functional test cases] and [ticket:353
create mockups for fedora services], we need to have some idea of the use
cases that we would want to test for.
Once this information is gathered, we can start creating the tools that we
need for better self testing in AutoQA.
== Questions to answer ==
NOTE: please add to this list if anything is missing.
* What are we looking to test
* Tests (depcheck, upgradepath etc.)
* Situations (broken deps, not breaking upgrade path etc.)
* What do we need in order to test it
* RPM details
* Repo contents
* Expected Results
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/355>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
11 years, 9 months
[AutoQA] #345: Implement file locks for all watchers
by fedora-badges
#345: Implement file locks for all watchers
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Finger Food
Component: watchers | Keywords:
-------------------------+--------------------------------------------------
In ticket #342 we implemented file lock for koji-bodhi watcher so that it
is not run concurrently in multiple instances. Implement the same for all
the remaining watchers.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/345>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
11 years, 10 months
AutoQA 0.8.0 Planning
by Tim Flink
Now that 0.7.0 has pretty much been released, it's time to start
thinking about 0.8.0. Kamil and I talked about this earlier today and
would like to get started on that sooner than later.
We'd like to do a phone conference again and the currently proposed
time is Thursday, December 1 at 13:30 UTC (05:30 PST, 08:30 EST, 14:30
CET). It's a little early for those of us who are in the US but it
seems like a fair compromise with the folks who are in or near Brno
time.
If you're interested and that time doesn't work for you, let us know
and we'll try to come up with a time that works for everyone. It would
pretty much need to be this week, though.
Tim
11 years, 10 months
Anaconda UI rewrite + AutoQA
by Kamil Paral
On our last QA meeting Adam Williamson notified us that there would be an Anaconda hackfest at the next FUDCon and we should raise our concerns (if we had some) regarding AutoQA and the UI re-write. Well, I don't know much about anaconda testing inside AutoQA, I just know we execute some anaconda tests, that's all. But I decided to kick off the discussion and CC relevant people.
>From what I know, we have two kind of anaconda tests inside AutoQA:
1. older rats_install test written by Will Woods and executed James Laska in the past
2. newer anaconda_storage, anaconda_checkbot and compose_tree written by Chris Lumens and James Laska
I am not sure which of those tests provide important feedback to the anaconda team and whether they are being used at all. Can relevant people provide more details about it?
Anaconda team, do you have some specific questions about AutoQA integration and the UI re-write? Will you want to change your tests inside AutoQA in response the new UI and need to have some information from us? I'll happy to answer them if I can.
Also, if the test authors have some comments or recommendation about the new UI architecture in order to allow simple automated testing, please post them here.
Thanks,
Kamil
11 years, 10 months
[AutoQA] #368: reconstructe Fedora install test automation framework
by fedora-badges
#368: reconstructe Fedora install test automation framework
----------------------+-----------------------------------------------------
Reporter: hongqing | Owner: hongqing
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: autotest | Keywords:
----------------------+-----------------------------------------------------
A new framework should be constructed to mapping the test cases and
kickstart files, and it also should be easy for the users to contribute.
A big idea is that one text file will be used to map the test case names
and kickstart files, and the kickstart files will be keeped in a
directory, during test, the test will iterate all the kickstart in the
directory. Users can create new kickstart files in the directory and write
the relationship between test case and kickstart in the text file, of
course, they can also pass it by arguments instead of doing this.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/368>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
11 years, 10 months
Re: #4920: name rules at dl.fp.o/alt/stage
by Hongqing Yang
The directories will always be named as below:
16-Alpha.TC1 16-Beta.RC1 16.RC1
The difference is for Live. There are only Desktop, KDE, LXDE and XFCE for Alpha and Beta.
Live will be separated and other spins will be added for Final, since Alpha and Beta are removed from dl.fp.o/alt/stage,
we cannot compare them now. and robatino is doing the deltaisos, if necessary we can contact with him directly.
I think currently we just need all the ISOs in directory 16.RC5/Fedora/
Hongqing
----- Original Message -----
> From: "Fedora Release Engineering" <rel-eng(a)fedoraproject.org>
> Sent: Thursday, December 1, 2011 11:05:57 AM
> Subject: Re: #4920: name rules at dl.fp.o/alt/stage
>
> #4920: name rules at dl.fp.o/alt/stage
> ------------------------------+---------------------------------------------
> Reporter: hongqing | Owner:
> rel-eng(a)lists.fedoraproject.org
> Type: task | Status: closed
> Milestone: Fedora 16 Final | Component: other
> Resolution: fixed | Keywords:
> ------------------------------+---------------------------------------------
> Changes (by ausil):
>
> * status: new => closed
> * resolution: => fixed
>
> Comment:
>
> after talking on IRC things are ok as is
>
> --
> Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4920#comment:7>
> Fedora Release Engineering <http://fedorahosted.org/rel-eng>
> Release Engineering for the Fedora Project
11 years, 10 months
