WEBVTT 00:00.000 --> 00:15.600 So, hi, I'm Gavor and I will talk about how it looks like in the QA Viki. 00:15.600 --> 00:28.000 So, if someone wants to join as a newcomer, the QA team, fortunately there is a lot of very 00:28.000 --> 00:40.400 useful Viki pages on how to do this, thanks to Foundation employees, mostly Air Marie 00:40.400 --> 00:43.400 Cisco, Stefan and Parapsalot others. 00:43.400 --> 00:53.360 So, this is supposed to be good so far, but actually let us ask ourselves how useful is this 00:53.360 --> 00:57.600 actually in onboarding our newbie. 00:57.600 --> 01:05.960 And I ask this from myself because when there is a monthly QA blog about what the QA team 01:05.960 --> 01:14.480 did, there is this top-hand treasures section and I always see the same names, sometimes 01:14.480 --> 01:20.560 even I am in the script, but this last time I was on it. 01:20.560 --> 01:28.520 But these are old contributors and looks like there are no newcomers, that sounds like 01:28.520 --> 01:30.520 a problem. 01:30.520 --> 01:37.640 So let's get to testing how to do that, let's take a newbie. 01:37.640 --> 01:49.240 So my wife was interested in this, yes, it would have been better if I would have a 01:49.240 --> 01:57.160 university class, but I am not a teacher, so that's what I can do, but still she had 01:57.160 --> 02:04.440 some technical background even in this area, so let's just retrain her. 02:04.440 --> 02:15.240 So give her a few common tasks in QA and I would suppose that someone based on just reading 02:15.240 --> 02:21.560 the Wiki can do that, those simple tasks, okay? 02:21.560 --> 02:27.000 And that's observe and do what are the results. 02:27.000 --> 02:37.240 So first task, find a QA Wiki from hibrofiz.org, find a QA Wiki, it's hidden here in the testing 02:37.280 --> 02:48.440 QA menu item, improve it is like not simple English, so that was a little bit of a turnoff, 02:48.440 --> 03:02.240 but eventually it was successful, so so far we are good, yeah, second and third tasks installed 03:02.240 --> 03:09.760 in the nightly build, why not, that's on the latest and greatest development version, 03:09.760 --> 03:18.560 and from the previous menu, it was successful, good, find the bugs in there and register 03:18.560 --> 03:25.680 in that, okay, this was also straightforward and easy, soon we will get to the problematic 03:25.680 --> 03:33.280 parts, okay, let's look up some unconformed works to confirm that recent reports are indeed 03:33.280 --> 03:44.080 valid or not, and that's also something QA team does, so from the Wiki, I was supposed 03:44.080 --> 03:52.560 supposing this should be easy task, but turns out not and it was on the bugs in the 03:52.720 --> 04:01.600 home page, these links, such as bugs reported in the last 24 hours, around days, and that 04:01.600 --> 04:09.280 was straightforward, but this info was not on the Wiki, so if someone goes to the Wiki and asked, 04:09.280 --> 04:16.640 okay, how do I have, they don't find this information, but it's a, three we are simple task 04:16.720 --> 04:27.280 for a new camera, okay, so maybe this is an improvement opportunity for the Wiki, okay, five, 04:28.320 --> 04:37.760 find bugs that need a buy buy set, which is something a little bit up advanced, but yeah, 04:38.320 --> 04:50.800 I wanted to give some more difficult task as well, so find in the buy buy set pages, of course, 04:50.800 --> 05:03.200 easy, but then it was, it was introducing a video about the topic, which is half an hour, 05:03.280 --> 05:15.120 and yeah, that's not what beginners want to watch, so that's not very useful anymore, 05:17.840 --> 05:23.200 and also finding the Windows specific buy buy set, the Git repository is very easy, 05:23.200 --> 05:39.680 there's a huge table in the Wiki about those, okay, what else, the Windows specific part of the 05:40.560 --> 05:48.960 Wiki is somewhat confusing, there is a big table with order, repositories we have like 20 or 05:49.040 --> 05:58.640 something like that already in the last 10 years, and we make one for every, every main 05:58.640 --> 06:06.480 release, so that's two repositories per year, each of them are being like 8 or 10 gigabytes of 06:07.760 --> 06:18.720 disk space, so it is filling up your disk very quickly, and there was a really easy repository 06:18.720 --> 06:27.840 at the end of the table, and she asked me it's important, but actually it was not, so finding the 06:27.840 --> 06:38.800 last few repositories, which contained the most recent regressions, that was less easy to 06:39.760 --> 06:53.120 find, so that's also improvement opportunity, but as setting up the environment is a very short 06:53.120 --> 07:01.680 section in this page, and it said that you are supposed to download Git for Windows, 07:01.840 --> 07:14.560 but there was no link to that software, so that's a small banana peel, but now I have fixed it, 07:16.240 --> 07:23.760 okay, another thing Cygwin is mentioned, that we used to recommend this, and yeah, 07:24.560 --> 07:31.360 this was somewhat of a red herring or something, but she started to use Cygwin, and 07:33.040 --> 07:41.200 somehow on her very new laptop, it failed to download the release repository, which is like 17 gigabytes, 07:41.760 --> 07:48.720 so rather large, but some very weird Git error came in the middle, so. 07:49.120 --> 08:02.080 Two minutes. Yeah, that's maybe that's something to remove from the page, and overall my impression is 08:02.080 --> 08:12.640 that this Windows specific page is very large, it contains instructions for insha setup and 08:13.440 --> 08:22.160 how to do troubleshooting while doing, by bisecting, and how to do the overall process, so maybe 08:22.160 --> 08:30.640 it could be split up into smaller chunks, so whoever is already done with insha setup is no longer 08:30.640 --> 08:49.040 seeing that part, because why should they see it? Okay, next, yeah, it's a, it's the same for the 08:49.040 --> 08:57.600 general QA search, by bisect page, mixes setups, setups instructions, troubleshooting, how to 08:57.600 --> 09:10.720 process descriptions, and also tasks for beginners, so in this part was the wasom query for the 09:11.760 --> 09:21.760 bugs in bugs yellow, which are needing this sort of examination, but this part was well hidden 09:22.480 --> 09:31.120 from the casual eye, so she did not find this, but otherwise it would be a very good 09:32.320 --> 09:44.640 how do I have type of content for perhaps a separate page, and also it's sort of from all 09:44.720 --> 09:51.840 this ones, which are the 10 year old bugs, which was somehow reported to be hidden, by bisect, 09:51.840 --> 09:59.920 but no one came to do it, so it's the ugliest part of the task, so not something for beginners, 10:00.720 --> 10:09.200 how about sorting it by new-est, it would be so much better, because most fresh bugs are easier to 10:09.280 --> 10:16.800 tackle, and that's good for beginners, so that's another improvement of opportunity, 10:18.720 --> 10:25.760 and that's all for today, thank you for listening.