Fedora QA Session @ RHT Bangalore

By -
Hey this post is going to talk about the retrospective of Fedora QA onboarding session at Red Hat Bangalore. 15 students from India participated in this event. The idea was to help them get started with contribution. It was good to see people working their way up the ladder. The students began by creating accounts and then setting up their testing environment. Introducing themselves in the mailing list , going ahead and doing Release validation and Update Testing.

The details can be found here --> https://public.etherpad-mozilla.org/p/fedoraqasession

The agenda covered :
1. What is Fedora QA?-->https://fedoraproject.org/wiki/QA/Join
2. Fedora's Release Cycle-->https://fedoraproject.org/wiki/Releases/27/Schedule
3. Setting up your Fedora for testing-->

3.1 Getting FAS accounts,pagure,bugzilla,qa-group sponsorship,adding ssh keys(etc).
3.2 Setting up VM for Release validation with current compose.
4. Getting the nightlies and RC-->https://www.happyassassin.net/2016/04/12/fedora-nightly-image-finder/

Current compose finder : https://fedoraproject.org/wiki/Test_Results:Current_Summary

5.Manual testing
5.1 Release validation-->https://dzone.com/articles/release-validation-testing-in-fedora-qa
5.2 Update Testings-->https://fedoraproject.org/wiki/QA:Updates_Testing
5.3 ARM testing
5.4 Kernel Performance and Regression --> https://fedoraproject.org/wiki/QA:Testcase_kernel_regression
5.4.1 ARM testing --> http://sumantrom.blogspot.in/2017/06/kernel-performance-testing-on-arm.html
5.5 Fedora Cloud Testing with testcloud --> https://fedoraproject.org/wiki/Changes/Local_Test_Cloud
5.6 Gnome Wayland bug triage
5.7 Non-Blocking release candidate testing

General feedback guideline and best practices
https://fedoraproject.org/wiki/QA:Update_feedback_guidelines

6.Automated testing
6.1 OpenQA-->http://openqa.fedoraproject.org/
6.2 Taskotron-->https://pagure.io/group/taskotron -->https://taskotron.fedoraproject.org/

Wiki : https://fedoraproject.org/wiki/QA
Pagure for day to day task of QA team : https://pagure.io/fedora-qa


7.Release Validation testing walkthough
7.1 Release Criteria
7.2  Test Cases  (I think we should talk about criteria first, since the testcases are meant to verify the criteria are met)
7.3  Writing test cases --> -->https://fedoraproject.org/wiki/QA:SOP_test_case_creation
7.3 Writing test Cases
8. Update testing tools
8.1 Fedora easy karma-->https://fedoraproject.org/wiki/Fedora_Easy_Karma
8.2 Bodhi
9. Bugzilla and filing bugs
9.1 Uploading RCA and logs
9.2 Best practices to be followed

Change Set for f27 https://fedoraproject.org/wiki/Releases/27/ChangeSet

10.Testdays -->https://fedoraproject.org/wiki/QA/SOP_Test_Day_management
How to host your own test day --> https://communityblog.fedoraproject.org/hosting-fedora-test-day/
10.1 How to participate --> 17th LxQT Test Day


It was inspiring to have a contributors coming forward and contributing to the project. This was a very helpful session. Thanks Red Hat for the venue and the facilities.

Comments

Post a Comment

Popular posts from this blog

Rocket on Fedora

By -
Image
This post is a very small example of how you can start creating small web apps with Rocket which extensively uses Rust under the hood. This post will just give an idea about how to get started if you are totally new to rust. Rocket is a web framework for Rust that makes it simple to write fast web applications without sacrificing flexibility or type safety . All with minimal code. - rocket.rs Getting started: Start by installing rust nightly on your system or virtual box: $ curl -sSf https://static.rust-lang.org/rustup.sh | sh -s -- --channel=nightly                  Setting up Project and Dependencies: Setting up the project is easy cas you can go ahead and execute cargo new hello-rocket --bin Once the execution is completes , you will have a binary application created with a Cargo.toml file and src dir with main.rs inside it. For setting up the dependencies you need to update the Cargo.toml file. Now,it's time to update the source main.rs f
Read more

[Test Day Annoucement] Anaconda Blivet GUI

By -
Image
Thursday 2017-04-06 will be Anaconda Blivet-GUI Test Day ! As part of this planned Change for Fedora 26, So this is an important Test Day! We'll be testing the new detailed bottom-up configuration screen has been long requested by users and inclusion of blivet-gui into Anaconda finally makes this a reality. On the other hand, it just adds a new option without changing the existing advanced storage configuration so users that prefer the top-down configuration can still use it. to see whether it's working well enough and catch any remaining issues. It's also pretty easy to join in: all you'll need is alpha 1.7 (which you can grab from the wiki page). Anaconda grew a rather important new option in F26: as well as the two existing partitioning choices (automatic, and the existing anaconda custom part interface) there's now a *third* choice.so now you can do custom partitioning with blivet-gui run within anaconda, as well as using anaconda's own interface
Read more

Mine Shiba Inu ($shib) on Fedora/LINUX

By -
Image
Context Please Well, all of us has heard about the new shiny $shib. When the pump is so high, news and media just happen to cover it. That's the normal. This post is not about what $shib is or what you can do with it. This post is a basic walk through of how YOU can mine $shib at home and earn [or atleast learn what mining is]. One of most hyped thing about mining is, we need Graphics Cards [GPU] and a lot of GPUs worthing lakhs in my country. Amount of money which is very hard to shell out at one go.  So, since sometime, miners have been relying heavily on a pool. A pool is collection of computing power which will together mine of a certain type of currency. We have some coins which will require a certain quantity of vRAM to start with and there are some which will require less. Depending on the power of the GPU, you can join the pool and help with collective mining.  Now, since a lot of us don't end up having such GPUs we end up not mining at all! But what if there was a way
Read more