#302: freeIPA test day request for 9.13.12
----------------------+------------------
Reporter: dpal | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
IPA team wants to allocate a test day slot on 9.13.12.
We will be providing details about the features to test and all the
instructions. This is not the first time we do it so we know the drill.
The only help we need is announcement of the IPA test day thought the
Fedora mailing lists.
We might need some other help but we not sure what it would be for now.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/302>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#305: Abrt test day request for 2012-09-27
----------------------+------------------
Reporter: dkutalek | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
I would like to allocate a test day slot for 2012-09-27.
This will be my first Test day as organizer, so I am just finding out how
things works and how it should look like. Seems like I have folks happy to
help around me in Brno, so hope everything will go fine.
I should bring in details in next weeks and expect having everything ready
by the end of August.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/305>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#312: OpenStack test day request for Aug 30th
----------------------+------------------
Reporter: pbrady | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
Following on from the previous 2 successful test days,
the openstack team would like to have a test day for the
openstack Folsom (milestone 3) release.
Probably included also in the test cases will be
tests for the new Heat component listed as a Fedora 18 feature:
https://fedoraproject.org/wiki/Features/Heat
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/312>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#308: Request for Fedora Networking Test Week
----------------------+------------------
Reporter: martix | Owner:
Type: task | Status: new
Priority: major | Milestone:
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
We want to do Networking Test Week on 24.-26. October 2012.
We will focus our testing on Network Manager, dnssec-trigger, firewalld
new functionality, interactions between them and their integration in
Gnome and KDE desktops.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/308>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#304: Request for F18 Power Management test day
-----------------------------------------+------------------
Reporter: jskarvad | Owner:
Type: task | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: | Blocked By:
Blocking: |
-----------------------------------------+------------------
We would like to run F18 Power Management test day. We expect it to be
similar to our previous F17 Power Management test day. We will try to
prepare Live CDs for this event (as for F17). We suggest 2012-10-11 but
probably any date would fit to us. We would probably also try to hold this
on-site in Red Hat Brno office (as for f17).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/304>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
Hey, folks. It's that time again - time to start thinking about Test
Days for Fedora 18.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization, or any combination of the
two. To propose a Test Day, just file a ticket in QA trac - full details
are at https://fedoraproject.org/wiki/QA/Test_Days/Create . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at
https://fedoraproject.org/wiki/QA/Fedora_18_test_days . There are many
slots open right now, with the earliest on 2012-08-09 and the latest
2012-11-01. Consider the development schedule, though, in deciding when
you want to run your Test Day - for some topics you may want to avoid
the time before the Alpha release or the time after the feature freeze
or the Final freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific timeframe due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or timeframe you'd
like, and we'll figure it out from there.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any other member of the QA team on test@ or in
#fedora-qa on IRC. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
#151: Tests consistent with Criterion
---------------------------+------------------------------------------------
Reporter: rhe | Owner: rhe
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 15
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
Criteria was kept changing during F-14 test cycle, but some installation
tests didn't update accordingly. On the other hand, the criterion should
be modified to include preupgrade_from_older_release test and new tests
created for F-15.
= enhancement recommendation =
Installation tests need be reviewed and updated to fit for the criterion.
Criterion for preupgrade_from_older_release test is required.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/151>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
is there a way to enable ssh on f18? i tried enable/disable, start/stop
firewalld/iptables.service, and even lokkit --enabled (which responded
with: ERROR: FirewallD is active, please use firewall-cmd.)
At the moment, there is a Final Criterion that states "If there is an embedded
checksum on any release medium, it must be correct", which means that in this
case you can run checkisomd5 externally and have it work. There is nothing that
ensures that the built-in mediacheck should work, even if it appears on the boot
menu (which it now does in F18). In fact, at the moment it doesn't - see
https://bugzilla.redhat.com/show_bug.cgi?id=848764 .
So I'd suggest adding something like requiring that if there is an embedded
checksum, then the built-in mediacheck (corresponding to the rd.live.check boot
option) should work. Perhaps the embedded checksum should also be required,
since all the Install and Live images currently have them. Thoughts?
#306: Blockers that move to 'CLOSED' are not removed from the tracker page
--------------------------------------+------------------------
Reporter: tflink | Owner: tflink
Type: defect | Status: new
Priority: major | Milestone: Fedora 18
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+------------------------
= bug description =
Blockers that move to 'CLOSED' are not moved from the tracker page
= bug analysis =
The bugzilla sync algorithm isn't updating the 'active' field to false
when a bug is closed
= fix recommendation =
Write a new test case to capture the behavior and update the
syncronization algorithm accordingly
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/306>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance