#293: proventester request
-----------------------------------------+------------------
Reporter: trafalger888 | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: | Blocked By:
Blocking: |
-----------------------------------------+------------------
Hello,
I am seeking a mentor for the proventesters group. I would like to
contribute to Fedora and its QA process by testing. I also have recently
started triaging bugs and think this would be another great way to assist
in Fedora's development.
Thank you,
Colby M. McKethen
cmckethen888(a)gmail.com
IRC nick: trafalger888
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/293>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#281: Requesting a proven tester mentor
-----------------------------------------+------------------
Reporter: kunkelc | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: | Blocked By:
Blocking: |
-----------------------------------------+------------------
= phenomenon =
= reason =
I was a proven tester under the usernam OldFart, but had to change ISPs
and now cannot modify the e-mail address used under that username.
Anyway, I think that is why I can't logon anymore. You can find numerous
BZs I have filed as ckunkel - at - been.there.com and currently as
clydekunkel7734 -at- verizon.net and many karma points for previous
versions of Fedora. I have read all of the documentation and am very much
aware that proven testers may be heavily modified or will just plain go
away at some point. Thanks. (Sorry -- don't know wiki formatting.)
= recommendation =
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/281>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#268: asking to join the proven testers and requesting a mentor
-----------------------------------------+------------------
Reporter: arifiauo | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: | Blocked By:
Blocking: |
-----------------------------------------+------------------
= phenomenon =
Hi my name is Arif,
I want to join to be part of proven tester, and I ask the mentor so that I
can be proven tester that can be served well.
= reason =
I am interested in joining proven tester because I love the community of
Fedora and I want to make the Fedora Project better and better.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/268>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#135: Proposed Test Day - TOPIC How about a consideration of the dual boot
issues from Fedora 13?
-----------------------+----------------------------------------------------
Reporter: dramsey | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 14
Component: Test Day | Version:
Keywords: dual boot |
-----------------------+----------------------------------------------------
How about a consideration of the dual boot issues from Fedora 13?
I remember from the Fedora 13 timeframe, there were dual boot issues.
Would it be advantageous to reconsider a subset of this as well as other
lessons learned from the Fedora 13 which may be a good peruse for
historical impact and reflection.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/135>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#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
#289: Howto: debug kernel
--------------------+------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: | Blocked By:
Blocking: |
--------------------+------------------------
I have seen a lot of discussions about kernel with debugging options
enabled in this cycle. The questions repeat itself and I have them
sometimes as well (I tend to forget these information). I think we should
create a wiki page describing:
1. That our current policy is to use debug kernels in all composes prior
to Branched Beta (is that true? maybe just Beta RC1?).
2. The problems that debug kernels may cause (mainly performance
problems).
3. The exceptions in this process (regularly there is a non-debug kernel
built).
4. How to know whether you are currently running a debug kernel (I never
remember this one).
5. How to find latest debug/non-debug kernel in Koji.
6. How to install this kernel from Koji.
Then we can link this page e.g. in our Alpha announcements, so that we
save a lot of question for many people (and maybe a lot of troubles as
well, if they have some troubles and they just don't know about debug
kernels at all).
Good idea? Volunteer?
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/289>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#284: Create advisory installation validation test cases for VirtualBox
----------------------+------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: minor | Milestone:
Component: Wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
Although kernel team (and the rest of the development team) specifically
don't want to commit to supporting VirtualBox, the practical fact is that
a lot of people like to run Fedora in VirtualBox, and we don't at present
have formal testing in place to find out if it's actually working during
release validation.
In practice, we usually find out about any bugs via people trying it and
then posting their results to test@ or the forums, but this is pretty
rough and ready and it's easy to lose the information. If we add formal
VBox testing to the release validation process we'll probably find out
about VBox fails sooner and do a better job of tracking them for possible
fixes or at least documentation at release time.
So, ideally, we should write test cases for deploying Fedora as a VBox
guest (and possibly using it as a VBox host), and add these to the
installation validation matrix as 'advisory' tests (tests not associated
with Alpha, Beta or Final release phases, and without a corresponding
release criterion).
Dan Mashal, who I hope I've added to CC, is interested in this topic and
may choose to be an awesome rock star and contribute the test cases :)
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/284>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance