 Hello everybody To those you know who don't know my name is Jeff. I'm core module on IRC been with Fedora QA for about three years now and I Thought that this talk would be good To kind of jumpstart anybody who hasn't messed with testing anything I Know you're at flocks, so you probably have a good idea about what Fedora is what composes so a lot of this we will gloss over and if we get to the end I Think we could just have a question and answer maybe So yeah, hello all So my name is Suprit and I'm not a full-time QB for Fedora. I work for Red Hat since last five years and Fedora, I just participate. I'm just working on it since last I think 27 and So my contribution to this was to I mean contribution as in my association with Fedora is like I Participate in test days. I mean upload the results file bugs Talk to people Get the base to test update the wikis and follow the process So so before we start How many in the room are QE? Who work with testing fantastic and who are not I mean I there are two to three people anyone who Wants to do the QA and has not done anything yet in Fedora We are not done Okay, okay, good. I mean So so to get started. Yeah Got a general outline of what we're going to talk about There'll be fairly high-level There will be some ticks and tips and tricks That that I found valuable and that Suprit has found valuable The technical side human side and then like I said if we get through it quick, we'll just jump to some questions So as far as actually testing goes you need two things a Fedora account and a bugzilla account Does anybody here not have a bugzilla account? Or a Fedora account for that matter, but you're at flock so Okay So this this is why we test ultimately to make a better end product This this is from the Fedora 29 release these blurbs I found on reddit Good great job Fedora you guys amazing keep up good work Okay, great things have really come around a bug that was affecting like damn was fixed last week And so the laptop I upgraded isn't having issues anymore. So Helps somebody there through testing Upgraded today, and it seems very solid. This is my favorite I want to switch from Ubuntu 18.04 to Fedora 29 Go in places So what is a compose I imagine we all have an idea but it's the compilation of packages that are Pushed together into a bootable image Ideally happens each day its raw hide until it is branched into the next numbered Fedora release and with each compose Comes an opportunity for testing testing that compose testing those packages that have been rolled together And That that's where validation testing comes in So four key things Validation testing the testing each compose Reporting bugs using bugzilla updates testing testing individual updates and Test days so validation testing Like I said is testing a certain compose whether it be raw hide an individual compose that happens each day or a numbered compose on a milestone like beta or final And we test each compose to meet the release criteria, which are a set of guidelines that are preset up That's a for the beta release There must not be these kind of bugs or these kind of errors and for the final release there shouldn't be these kinds and so That is how we determine if something is Bug worth blocking the release on is whether or not it violates the release criteria, which makes it a lot easier when you get towards the end or towards The the hard dates to pick whether or not we can continue with this release because you have the criteria to go on and You can so the test matrices is where we store all the data. It's a wiki page For now and When you test you You can't you go to the test matrix matrix and you can Fill out what you tested. I kind of want to Would like to show you that has anybody not seen it the fedora test matrix Yeah, okay, let's see Let me see if I can do this. Does anyone else had trouble with the network or is it just me? Okay Yeah, we will put this on to I think we could do that. Oh, here we go. Okay So for example, this is the the latest test matrix page the last Compose was the August second. Yeah, so it's a little old but Here you can find what needs to be tested and On which release the base the server the cloud the desktop and so Here's links to all of those images You can find the x86 64-bit image here for all of these on the left as well as armed 64 32 Power PC and s390 x But it this is a good example of What a past test looks like What a failed test looks like what a warning looks like The robot means it's an automated test and then each of these links will link you to a bug or a comment So you can see here that Coconut the bot Had a failure here the size of the workstation live image, which that's what this test is here was Larger than Yes, yes, and it's generated with each release Each compose yeah, yeah, yeah from from the the template that's probably I don't know where it's hosted But so say you want to test something you'd come here and Oh, yeah, let's let's pick this one. So This these are test cases under the storage devices category The milestone that this test must pass Is final so in order for us to ship final somebody has to test this and say that it passed ideally on Final but for some things specifically this fcoe case If it has been tested fairly recently that's good enough So that that does lead me to something else if anybody here has fiber channel over ethernet hardware And you'd like to donate some time testing that would be great because I Think that gets tested once or twice each release so but anyway, so you'd pick what you'd want to do and You can load it it gives you a description of what the test is How to set up for the test how to actually test it and the expected results that you should see and Assuming that that all Passes then you can Mark the test as Passed or failed or or whatever Anyone with a fedora account actually yeah Actually, I think anybody can try. I'm not logged in I'm gonna try it here without being logged in. Yeah, so I guess anybody can Which might be something to think about in the future, I don't know Right you would Just keep I So then another way of testing is by reporting bugs that you find has anyone not seen bugzilla get out So you've all seen bugzilla you all know that that's where we track bugs I won't go into it Want to see it Does anyone want to see it Another way to help contribute it's not testing but Is by attending the blocker bugs meeting so come maybe a month before The branch point we will start to have Blocker bug meetings where we discuss bugs that have been Marked as blockers or violating the release criteria from the first slide and we will all vote on whether we think that it violates the criteria or not and That is where we determine if it actually is a blocker Or if it's a freeze exception and That's a good way to contribute and a good way to Initially get started because all it takes is a knowledge of of the individual bug which you can find on bugzilla and you just read through it and you read the release criteria and You make a judgment call whether or not you think that it violates the criteria or not and be prepared to back it up because sometimes it gets passionate and if you can do that then That's a good way to contribute another way to contribute is to act as the secretary in those meetings where afterwards there could be anywhere from one to Tim how long was that meeting that you had that set the precedent for? If you if you have How many bugs what were did you guys go over but a lot a lot or yeah So you can have a lot of bugs or a few bugs but the secretary will go through all the bugs afterwards and mark whether they were accepted or denied and And a brief blurb and that's another good way to just Contribute if you want to get involved and get your name out there. That'd be a good way to go The third way to really contribute is through updates testing Which is testing individual packages that are in the updates testing repository you Can permanently enable the updates testing repo and when you're full-time QE That's that's what I do personally is I permanently enable it DNF update and then I run through Fedora easy karma. Whoops Here's how you can enable it, but fedora easy karma is a tool that we have that can tell which packages you have installed versus What is in the? updates testing repo and So you update you test it and then you can report using this fedora easy karma and Yeah, that's just a config Is anybody not seen fedora easy karma, let me show you that just so you have an idea Yes Okay Looks like it might work. It's a lot easier than going to Bodhi and Yeah, okay, well don't look at that cuz Okay, yeah, it's an old version is it did Python did we update It's got a little you want the last seven minutes, I think We'll come back to this we'll let it do its thing of course it disconnects So regarding test days, I think we have the official pages We usually get the announcements for upcoming test days you test for the kernel you test for updates upgrades and So if it won't open, I don't know I think it is it's just Originally Supra Wanted to do talk like this that was 50 minutes long and I had said I will do this talk And it's 25 minutes long and then when it came around to it Supra's talk was not selected, but mine was so we decided to collaborate and each take half of you know The 25 minutes, so we had a lot more than we had to cram What So yeah, so we have Fedora 31 upcoming and so the kernel test day was announced recently We just go to the wiki page follow the steps and do the testing. I've already started and So we have Sumantro here who does the announcement usually so Apart from test days, I think So do you want to speak? Do we go to the end? Thank you. And this is the checklist for you to be getting started with your Fedora QV make sure you have all these things and We have this IRC list channels for Fedora Q wave Fedora you just join and search for people you can Search core module or super it over the channels. We are there to help. We have Sumantro here and For the mailing list you can join test at the red peddler project rg For any questions you can put over there We know we're on time Any questions we can take we have we could show you that Here if you're interested if it's just a question vote is the selection of Platforms for testing because for example several times in past half a year I Launched an EC2 machine from the latest Fedora Compose and it simply didn't include so I was let's say I Concerned how this is working that There are a my images for easy to instances like provided by federally and this images like not so Rarely are even not EC2 is a blocking It's not So that's why It's a scene for example, it's there you can test it. It's good. It would be nice if someone would But it's not there is blocking so it's not as important for Because It takes a lot of time to test all the stuff which is blocking So there is a lot of things I think that I'm not sure If that one you mentioned is blocking I don't think so Yeah, that's what I thought Was it a rawhide Compose It's it's testing So For us Most important one Say that again Yeah These these these are You understand This is right where you reported If you weren't able to It seems like everybody should we should we Yeah tomorrow and Saturday That's Saturday Oh Karaoke right Why don't you talk about it Okay Any other questions or do we want to see the bugzilla page? Yeah All right, well then let's call it call it a day