Fedora 29-20180926.n.0 compose check report
No missing expected images. Failed openQA tests: 5/132 (x86_64), 1/24 (i386), 1/2 (arm) ID: 285923 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/285923 ID: 285959 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/285959 ID: 285975 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/285975 ID: 285981 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/285981 ID: 285987 Test: x86_64 universal install_no_swap URL: https://openqa.fedoraproject.org/tests/285987 ID: 286030 Test: x86_64 universal install_blivet_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/286030 ID: 286069 Test: i386 universal install_scsi_updates_img URL: https://openqa.fedoraproject.org/tests/286069 Soft failed openQA tests: 4/132 (x86_64), 2/24 (i386) (Tests completed, but using a workaround for a known bug) ID: 285917 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/285917 ID: 285918 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/285918 ID: 285943 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/285943 ID: 285944 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/285944 ID: 285949 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/285949 ID: 286022 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/286022 Passed openQA tests: 123/132 (x86_64), 21/24 (i386) Skipped openQA tests: 1 of 158 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora 29 compose report: 20180926.n.0 changes
OLD: Fedora-29-20180923.n.0 NEW: Fedora-29-20180926.n.0 = SUMMARY = Added images:0 Dropped images: 2 Added packages: 2 Dropped packages:1 Upgraded packages: 26 Downgraded packages: 0 Size of added packages: 468.96 KiB Size of dropped packages:304.24 KiB Size of upgraded packages: 3.12 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 2.63 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Container_Minimal_Base docker s390x Path: Container/s390x/images/Fedora-Container-Minimal-Base-29-20180923.n.0.s390x.tar.xz Image: LXQt live x86_64 Path: Spins/x86_64/iso/Fedora-LXQt-Live-x86_64-29-20180923.n.0.iso = ADDED PACKAGES = Package: python-j1m.sphinxautozconfig-0.1.0-3.fc29 Summary: Sphinx support for ZConfig RPMs:python2-j1m.sphinxautozconfig python3-j1m.sphinxautozconfig Size:26.94 KiB Package: thttpd-2.29-2.fc29 Summary: A tiny, turbo, throttleable lightweight HTTP server RPMs:thttpd Size:442.02 KiB = DROPPED PACKAGES = Package: reinteract-0.5.9-19.fc29 Summary: Interactive Python shell RPMs:reinteract Size:304.24 KiB = UPGRADED PACKAGES = Package: NetworkManager-1:1.12.4-1.fc29 Old package: NetworkManager-1:1.12.2-2.fc29 Summary: Network connection manager and user applications RPMs: NetworkManager NetworkManager-adsl NetworkManager-bluetooth NetworkManager-config-connectivity-fedora NetworkManager-config-server NetworkManager-dispatcher-routing-rules NetworkManager-libnm NetworkManager-libnm-devel NetworkManager-ovs NetworkManager-ppp NetworkManager-team NetworkManager-tui NetworkManager-wifi NetworkManager-wwan Size: 24.84 MiB Size change: 27.95 KiB Changelog: * Tue Sep 18 2018 Thomas Haller - 1:1.12.4-1 - Update to 1.12.4 release Package: SuperLU-5.2.1-5.fc29 Old package: SuperLU-5.2.1-4.fc29 Summary: Subroutines to solve sparse linear systems RPMs: SuperLU SuperLU-devel SuperLU-doc Size: 7.15 MiB Size change: -29.72 KiB Changelog: * Fri Sep 14 2018 Antonio Trande - 5.2.1-5 - Remove gcc-gfortran as required package Package: brial-1.2.4-1.fc29 Old package: brial-1.2.3-3.fc29 Summary: Framework for Boolean Rings RPMs: brial brial-devel python2-brial python3-brial Size: 6.48 MiB Size change: -53.20 KiB Changelog: * Thu Sep 13 2018 Jerry James - 1.2.4-1 - New upstream version Package: container-selinux-2:2.73-1.gitd7a3f33.fc29 Old package: container-selinux-2:2.71-2.git5721d74.fc29 Summary: SELinux policies for container runtimes RPMs: container-selinux Size: 44.41 KiB Size change: 424 B Changelog: * Mon Aug 27 2018 Dan Walsh - 2.71-2 - Fix restorecon to not error on missing directory * Wed Sep 12 2018 Dan Walsh - 2.72-1 - Allow container_runtimes to setattr on callers fifo_files * Wed Sep 12 2018 Dan Walsh - 2.73-1 - Define spc_t as a container_domain, so that container_runtime will transition to spc_t even when setup with nosuid. Package: cpprest-2.10.6-1.fc29 Old package: cpprest-2.10.5-1.fc29 Summary: C++ REST library RPMs: cpprest cpprest-devel Size: 4.94 MiB Size change: 3.02 KiB Changelog: * Thu Sep 13 2018 Wolfgang St??ggl - 2.10.6-1 - New upstream version - Since v2.10.0 the minimum required version of cmake is 3.1 Package: erlang-cowboy-2.4.0-1.fc29 Old package: erlang-cowboy-2.0.0-3.fc29 Summary: Small, fast, modular HTTP server written in Erlang RPMs: erlang-cowboy Size: 244.25 KiB Size change: -963.20 KiB Changelog: * Fri Sep 14 2018 Peter Lemenkov - 2.4.0-1 - Ver. 2.4.0 Package: erlang-folsom-0.8.7-1.fc29 Old package: erlang-folsom-0.8.5-5.fc29 Summary: Erlang-based metrics system RPMs: erlang-folsom Size: 106.35 KiB Size change: -527.47 KiB Changelog: * Fri Sep 14 2018 Peter Lemenkov - 0.8.7-1 - Ver. 0.8.7 Package: erlang-gproc-0.8.0-1.fc29 Old package: erlang-gproc-0.7.0-4.fc29 Summary: Extended process registry for Erlang RPMs: erlang-gproc Size: 417.37 KiB Size change: -2.04 MiB Changelog: * Fri Sep 14 2018 Peter Lemenkov - 0.8.0-1 - Ver. 0.8.0 Package: erlang-mochiweb-2.18.0-1.fc29 Old package: erlang-mochiweb-2.17.0-3.fc29 Summary: An Erlang library for building lightweight HTTP servers RPMs: erlang-mochiweb Size: 1.81 MiB Size change: 1.56 KiB Changelog: * Tue Sep 04 2018 Peter Lemenkov - 2.18.0 - Ver. 2.18.0 Package: erlang-protobuffs-0.9.1-1.fc29 Old package: erlang-protobuffs-0.9.0-6.fc29 Summary: A set of Protocol Buffers tools and modules for Erlang applications RPMs: erlang-protobuffs Size: 115.37 KiB Size change: -573.24 KiB Changelog: * Fri Sep 14 2018 Peter Lemenkov - 0.9.1-1 - Ver. 0.9.1 Package: erlang-ranch-1.6.1-1.fc29 Old package
[Test Day] Fedora 29 Atomic and Cloud 2018-10-01
Hey All, Fedora 29 Atomic and Cloud provides latest version of packages from Fedora 29. Both Fedora Cloud Base and Atomic Host provide the latest available versions of packages in Fedora 29 containing all features and bug fixes done in individual packages like the kernel, cockpit and more. Additionally, Fedora Atomic Host includes the latest version of podman, which provides the ability to use OCI containers[0] and runc. This Test Day is to make sure that all artifacts from Fedora 29 Atomic Host and Cloud Base are working as expected and to catch and fix bugs early. For Atomic Host, there are ISO and QCOW2 images available to test on the aarch64, ppc64le and x86_64 architectures. Additionally, there are libvirt and virtualbox vagrant images for both Atomic Host and Cloud Base. If you use AWS to launch instances in cloud, you can help by testing the AMIs both Atomic Host and Cloud Base. All the details on how and what to test and more information about the available media download details are available at Test Day wiki page[1]. [0]https://www.opencontainers.org/ [1]https://fedoraproject.org/wiki/Test_Day:2018-10-01_Cloud-Atomic_Testday Thanks //sumantro ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
[Test-Announce] [Test Day] Fedora 29 Atomic and Cloud 2018-10-01
Hey All, Fedora 29 Atomic and Cloud provides latest version of packages from Fedora 29. Both Fedora Cloud Base and Atomic Host provide the latest available versions of packages in Fedora 29 containing all features and bug fixes done in individual packages like the kernel, cockpit and more. Additionally, Fedora Atomic Host includes the latest version of podman, which provides the ability to use OCI containers[0] and runc. This Test Day is to make sure that all artifacts from Fedora 29 Atomic Host and Cloud Base are working as expected and to catch and fix bugs early. For Atomic Host, there are ISO and QCOW2 images available to test on the aarch64, ppc64le and x86_64 architectures. Additionally, there are libvirt and virtualbox vagrant images for both Atomic Host and Cloud Base. If you use AWS to launch instances in cloud, you can help by testing the AMIs both Atomic Host and Cloud Base. All the details on how and what to test and more information about the available media download details are available at Test Day wiki page[1]. [0]https://www.opencontainers.org/ [1]https://fedoraproject.org/wiki/Test_Day:2018-10-01_Cloud-Atomic_Testday Thanks //sumantro ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org
Re: Proposal: Add release announcement post to Go/No-Go criteria
On Wed, Sep 26, 2018 at 12:38 AM Matthew Miller wrote: > On Tue, Sep 25, 2018 at 04:35:09PM -0400, Ben Cotton wrote: > > With today's Beta release, the release announcement post for Fedora > > Magazine was not ready. As a result, the announcement went out a > > little late and then only due to a drop-everything effort (thanks, > > stickster!). We have a proposal to add a fourth criterion for the > > Go/No-Go decision, beginning with F29 Final: > > Isn't this supposed to be the point of the release-readiness meeting that > follows go/no-go? > Indeed, it is part of the readiness meeting but even that might not be sufficient sometimes. This happened to me once that the Beta release announcement wasn't really ready (and I had to write it then...) even I was told on the readiness meeting it is ready :). And it's a knowledge that somehow transferred from Program Manager to Program Manager to always recheck the status but it gets lost over generations :))) (and you're doing a great job Ben!). Go/No-Go meeting is really a not a good candidate but maybe some changes to how the Readiness meeting is done might help. Instead of status meeting we can change it more to the Readiness Check-list like thing with predefined tasks that are neccessary for the release. Just one note - afaik Readiness meeting does not block the release automatically if something is not ready but I believe it's kind of common sense to block when something like announcement is not ready (but you always have like 5 days between first possible GA date and Readiness meeting). Thanks, Jaroslav > > -- > Matthew Miller > > Fedora Project Leader > ___ > devel mailing list -- de...@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org > -- Jaroslav Řezník Engineering Program Manager Office: +420 532 294 645 Mobile: +420 602 797 774 Red Hat, Inc. http://www.redhat.com/ ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Self-introduction: Péter Tóth
- Original Message -
> From: "Peter Toth"
> To: test@lists.fedoraproject.org
> Sent: Tuesday, June 19, 2018 2:28:44 PM
> Subject: Self-introduction: Péter Tóth
>
> Hello,
>
> I'm a big fan of Fedora and want to contribute somehow to the Fedora QA.
> I currently study electrical engineering at the Brno University of Technogy
> in Brno, Czech republic and I'm also interested in computers generaly. I
> mean just to imagine the "flying" electrons inside the silicon of the ICs or
> just to bring my thoughts to the "other side" and think about anything
> relating to UNIX-like operating systems and it's applications. I also enjoy
> learning new things about how the things work on the Linux, and for this
> reason I thought it would be interesting to see and be part of the team
> which manages the testing in order to find out what is not working properly.
> :-)
>
> Also currently I am an intern at the Red Hat's Brno office. I do have
> experience with using and administrating Fedora and also RHEL, RHEV In
> the field of programming I do have experience with C language, Python,
> markup languages and not so markup language as YAML, also I do shell
> scripting in BASH and sometimes I trying to be POSIX compliant with it. :-)
>
> I am available also on:
> ICQ: 405778592
> IRC ptoth(at) irc.freenode.net
> e-mail: xtothp00(at) stud.feec.vutbr.cz -- alternative
>
> I am looking forward to work with you!
> Kind regards,
>
> --
>
>
Hey Peter!
Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you
have, I have sponsored you by now.
I think you already had a word with Adamw but here's something more you can
look into, if you are looking to contribute to Fedora QA. :)
You can start off by testing updates in [http://bodhi.fedoraproject.org/] for
Fedora 27, Fedora 28, and Fedora 29. Update testing is where a tester tests a
package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases
and tags viz "pending" & "testing". You can read much about update testing here
[1]. You can also, use fedora-easy-karma for giving out feedbacks.
you can start with Release Validation testing. In Release Validation all you
need to do is to check the nightly/TC/RC against certain criteria. For example,
let's take the latest compose (Fedora 29 Branched 20180923), you can run test
cases which are mentioned [2] and submit your results in the test matrix.
Note that each of the test cases[3] will have "How to test" section which will
have the steps (to be executed sequentially) and if the results match with the
expected results you can mark it as pass by editing the wiki page
{{result|PASS|}} . Always make sure to check for "Associated
release criterion" which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.
You can always find the ‘current’ validation pages using these addresses:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
For Automation, you can start looking at
Taskotron[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].
https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n.0_Summary?rd=Test_Results:Current_Summary
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
We have test days coming happening now which is a nice place to start, please
stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
Thanks
//sumantro
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Introduction - Diego Damian
- Original Message -
> From: "Diego Damián"
> To: test@lists.fedoraproject.org
> Sent: Friday, June 29, 2018 4:48:33 PM
> Subject: Introduction - Diego Damian
>
> Hi guys,
>
> My name is Diego Aaron, I'm 26 years old and live at Lima Perú. I have
> started using Linux for a couple of months now, since I am preparing for the
> LPIC I certification.
> I am also learning about Java programming and application testing in a
> personal way. I have more experience in configuring Cisco network equipment.
> I'm very glad to join at Fedora QA Team. I have working with Red Hat Linux in
> my work since six months ago. So, let's time to
> contribute with the project.
>
> So, thanks a lot for some people who accepted me at Fedora Project.
>
> At my signature I'm sending my contacts fell free if anyone want to contact
> me.
>
> Bye
> --
> Att.
>
> Diego Damian
> -
> Contacts
> email: diegoaaro...@gmail.com
> irc nickname: diegoaaron909
Hey Diego,
Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you
have, I have sponsored you by now.
You can start off by testing updates in [http://bodhi.fedoraproject.org/] for
Fedora 27, Fedora 28, and Fedora 29. Update testing is where a tester tests a
package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases
and tags viz "pending" & "testing". You can read much about update testing here
[1]. You can also, use fedora-easy-karma for giving out feedbacks.
you can start with Release Validation testing. In Release Validation all you
need to do is to check the nightly/TC/RC against certain criteria. For example,
let's take the latest compose (Fedora 29 Branched 20180923), you can run test
cases which are mentioned [2] and submit your results in the test matrix.
Note that each of the test cases[3] will have "How to test" section which will
have the steps (to be executed sequentially) and if the results match with the
expected results you can mark it as pass by editing the wiki page
{{result|PASS|}} . Always make sure to check for "Associated
release criterion" which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.
You can always find the ‘current’ validation pages using these addresses:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
For Automation, you can start looking at
Taskotron[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].
https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n.0_Summary?rd=Test_Results:Current_Summary
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
We have test days coming happening now which is a nice place to start, please
stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
Thanks
//sumantro
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Introduction
- Original Message -
> From: "Jaydeep Godara"
> To: test@lists.fedoraproject.org
> Sent: Thursday, August 23, 2018 3:14:03 PM
> Subject: Introduction
>
> Hello,
> I am Jaydeep Godara and pursuing my B.Tech in Computer Science.
> I am using Linux from more than year and fedora for last six months.
> Currently I am working with Python and Machine Learning.
> I want to contribute to fedora and testing is most fitted option for me right
> now.
>
> Links:
> Github:
> https://github.com/JaydeepGo
> Twitter:
> https://twitter.com/JaydeepGo
> IRC:
> JaydeepGo at freenode
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/OOV6UBXBS3K4MZ3LNUU4YRVFDGBVATDU/
>
Hey Jaydeep!
Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you
have, I have sponsored you by now.
I think you already had a word with Adamw but here's something more you can
look into, if you are looking to contribute to Fedora QA. :)
You can start off by testing updates in [http://bodhi.fedoraproject.org/] for
Fedora 27, Fedora 28, and Fedora 29. Update testing is where a tester tests a
package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases
and tags viz "pending" & "testing". You can read much about update testing here
[1]. You can also, use fedora-easy-karma for giving out feedbacks.
you can start with Release Validation testing. In Release Validation all you
need to do is to check the nightly/TC/RC against certain criteria. For example,
let's take the latest compose (Fedora 29 Branched 20180923), you can run test
cases which are mentioned [2] and submit your results in the test matrix.
Note that each of the test cases[3] will have "How to test" section which will
have the steps (to be executed sequentially) and if the results match with the
expected results you can mark it as pass by editing the wiki page
{{result|PASS|}} . Always make sure to check for "Associated
release criterion" which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.
You can always find the ‘current’ validation pages using these addresses:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
For Automation, you can start looking at
Taskotron[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].
https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n.0_Summary?rd=Test_Results:Current_Summary
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
We have test days coming happening now which is a nice place to start, please
stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
Thanks
//sumantro
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: To join Fedora testing and quality assurance
- Original Message -
> From: "Abdul Rehman"
> To: test@lists.fedoraproject.org
> Sent: Wednesday, September 5, 2018 11:28:56 PM
> Subject: To join Fedora testing and quality assurance
>
> Hi,
> I am currently testing on Screen keyboard of Fedora using OpenQA and I found
> a bug which I would like to discuss on the list. So request to join me in
> the list.
>
> --
> Regards,
> Abdul Rehman Quadri
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
Hey Abdul!
Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you
have, I have sponsored you by now.
I think you already had a word with Adamw but here's something more you can
look into, if you are looking to contribute to Fedora QA. :)
You can start off by testing updates in [http://bodhi.fedoraproject.org/] for
Fedora 27, Fedora 28, and Fedora 29. Update testing is where a tester tests a
package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases
and tags viz "pending" & "testing". You can read much about update testing here
[1]. You can also, use fedora-easy-karma for giving out feedbacks.
you can start with Release Validation testing. In Release Validation all you
need to do is to check the nightly/TC/RC against certain criteria. For example,
let's take the latest compose (Fedora 29 Branched 20180923), you can run test
cases which are mentioned [2] and submit your results in the test matrix.
Note that each of the test cases[3] will have "How to test" section which will
have the steps (to be executed sequentially) and if the results match with the
expected results you can mark it as pass by editing the wiki page
{{result|PASS|}} . Always make sure to check for "Associated
release criterion" which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.
You can always find the ‘current’ validation pages using these addresses:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
For Automation, you can start looking at
Taskotron[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].
https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n.0_Summary?rd=Test_Results:Current_Summary
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
We have test days coming happening now which is a nice place to start, please
stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
Thanks
//sumantro
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Introduction
- Original Message -
> From: "Ludovic Hirlimann"
> To: test@lists.fedoraproject.org
> Sent: Friday, September 21, 2018 11:14:06 AM
> Subject: Introduction
>
> Hi,
> My name is Ludovic. Paul-Muadib on freenode. I've been using OSS since
> 2000ish. I'm emplyed by mozilla as root , before that I was the QA lead for
> Thunderbird and for Joost a video startup company. I've used linux on and
> off since 1996 (kernel 1.3.88) with slackware/Debian/RHEL/CentOS - I've also
> played with things like Tru64, HP-UX and friends. I'm joigning the QA list,
> cause I like running the kernel-test and the wiki needs some edits (like
> using pyhton3-fedora). I don't have much free time but I have interest in
> non x86 hardware, 28mm platisc soldier and photography. I usually sign my
> emails (but have not setup this adrees back on a proper email client since
> I've reinstalled my machine.
>
> Ludo
>
> --
> https://www.hirlimann.net/Ludovic/carnet/
Hey!
Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you
have, I are sponsored by now.
You can start off by testing updates in [http://bodhi.fedoraproject.org/] for
Fedora 27, Fedora 28, and Fedora 29. Update testing is where a tester tests a
package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases
and tags viz "pending" & "testing". You can read much about update testing here
[1]. You can also, use fedora-easy-karma for giving out feedbacks.
you can start with Release Validation testing. In Release Validation all you
need to do is to check the nightly/TC/RC against certain criteria. For example,
let's take the latest compose (Fedora 29 Branched 20180923), you can run test
cases which are mentioned [2] and submit your results in the test matrix.
Note that each of the test cases[3] will have "How to test" section which will
have the steps (to be executed sequentially) and if the results match with the
expected results you can mark it as pass by editing the wiki page
{{result|PASS|}} . Always make sure to check for "Associated
release criterion" which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.
You can always find the ‘current’ validation pages using these addresses:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
For Automation, you can start looking at
Taskotron[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].
https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n.0_Summary?rd=Test_Results:Current_Summary
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
We have test days coming happening now which is a nice place to start, please
stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
I will be interested in working with you for creating more test cases for
Firefox and Thunderbird!
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
