101010.pl

Adam Williamson :fedora:yesterday in <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> qa: * last day of <a href="https://fosstodon.org/tags/devconf_cz" class="mention hashtag" rel="nofollow noopener" target="_blank">#devconf_cz</a> , had a great time! good to see everybody there and meet some new (to me) folks * apart from that, head down working on my new approach for reverse dependency and installability testing, based on lying to dnf repoclosure. I think it's going to be viable, and maybe allow us to have gating checks! I'm just finishing up the test suite, then I'll publish it and start testing it on <a href="https://fosstodon.org/tags/ELN" class="mention hashtag" rel="nofollow noopener" target="_blank">#ELN</a> updates in <a href="https://fosstodon.org/tags/openqa" class="mention hashtag" rel="nofollow noopener" target="_blank">#openqa</a> for now

openSUSE LinuxContribute through testing! 🧪 Learn how to start building <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a> tests for your favorite <a href="https://fosstodon.org/tags/apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#apps</a> at this year's <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> Conference. <a href="https://events.opensuse.org/" rel="nofollow noopener" translate="no" target="_blank">https://events.opensuse.org/</a> <a href="https://fosstodon.org/tags/workshop" class="mention hashtag" rel="nofollow noopener" target="_blank">#workshop</a>

openSUSE LinuxFrom testing in <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a> to rolling with <a href="https://fosstodon.org/tags/Slowroll" class="mention hashtag" rel="nofollow noopener" target="_blank">#Slowroll</a>, your voice matters! Weekly meetings & updates across <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> projects like Leap, Release Engineering, <a href="https://fosstodon.org/tags/Uyuni" class="mention hashtag" rel="nofollow noopener" target="_blank">#Uyuni</a> & more! 🗓️ Don’t just use <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>; build it! Join us 👉 <a href="https://calendar.opensuse.org" rel="nofollow noopener" translate="no" target="_blank">https://calendar.opensuse.org</a>

jablkoziemneHello <a href="https://101010.pl/tags/gnome" class="mention hashtag" rel="tag">#gnome</a> people, are <a href="https://101010.pl/tags/gui" class="mention hashtag" rel="tag">#gui</a> tests still done through the <a href="https://101010.pl/tags/accessibility" class="mention hashtag" rel="tag">#accessibility</a> <a href="https://101010.pl/tags/api" class="mention hashtag" rel="tag">#api</a>? I found <a href="https://discourse.gnome.org/t/how-do-you-test-a-gui-application/3010/3" target="_blank" rel="nofollow noopener" translate="no">https://discourse.gnome.org/t/how-do-you-test-a-gui-application/3010/3</a> but havent yet a chance to use <a href="https://101010.pl/tags/openQA" class="mention hashtag" rel="tag">#openQA</a> or <a href="https://101010.pl/tags/dogtail" class="mention hashtag" rel="tag">#dogtail</a>. Im asking mostly because Im planning on making some small application, and I would like to add at the end of the CI pipeline some <a href="https://101010.pl/tags/end2end" class="mention hashtag" rel="tag">#end2end</a> <a href="https://101010.pl/tags/test" class="mention hashtag" rel="tag">#test</a> to make sure there are no regressions when attempting on some <a href="https://101010.pl/tags/datadriven" class="mention hashtag" rel="tag">#datadriven</a> <a href="https://101010.pl/tags/dynamic" class="mention hashtag" rel="tag">#dynamic</a> layout generation. Or in GNOME case e2e tests are generally not done for specific applications, and they are mostly for the shell, and applications are tested (mostly) by hand? (not trying to belittle <a href="https://101010.pl/tags/QA" class="mention hashtag" rel="tag">#QA</a> people, just I feel the common use cases should be automated to lessen the burden on them)

openSUSE LinuxWant to help test <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> & contribute to quality assurance? You don’t need hours; just 60 seconds. Learn how by watching this quick guide to contributing to <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a>. <a href="https://youtube.com/shorts/Y5_LeNhGqk0?si=O6PSJSWqv4ArN5dh" rel="nofollow noopener" translate="no" target="_blank">https://youtube.com/shorts/Y5_LeNhGqk0?si=O6PSJSWqv4ArN5dh</a>

Adam Williamson :fedora:today in <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> qa: * attended the workstation wg meeting for a catch-up, think it went well * looked into an update stuck in gating, sent a PR to fix its test suite for the sbin merge: <a href="https://src.fedoraproject.org/tests/httpd/pull-request/23" rel="nofollow noopener" translate="no" target="_blank">https://src.fedoraproject.org/tests/httpd/pull-request/23</a> * tweaked my 'check package signatures' <a href="https://fosstodon.org/tags/openqa" class="mention hashtag" rel="nofollow noopener" target="_blank">#openqa</a> test PR a few times and tested it, eventually merged it: <a href="https://pagure.io/fedora-qa/os-autoinst-distri-fedora/pull-request/370" rel="nofollow noopener" translate="no" target="_blank">https://pagure.io/fedora-qa/os-autoinst-distri-fedora/pull-request/370</a> * told <a href="https://fosstodon.org/@nirik" class="u-url mention" rel="nofollow noopener" target="_blank">@nirik</a> and <a href="https://fosstodon.org/@Conan_Kudo" class="u-url mention" rel="nofollow noopener" target="_blank">@Conan_Kudo</a> it had found unsigned packages in several images, they swore a bit and fixed it * travel planning for <a href="https://fosstodon.org/tags/devconf" class="mention hashtag" rel="nofollow noopener" target="_blank">#devconf</a> in june

Adam Williamson :fedora:today in <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> qa: * freelance flatpak diplomacy! <a href="https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks/-/issues/39" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks/-/issues/39</a> , <a href="https://pagure.io/releng/issue/12586" rel="nofollow noopener" translate="no" target="_blank">https://pagure.io/releng/issue/12586</a> , <a href="https://pagure.io/fedora-workstation/issue/463" rel="nofollow noopener" translate="no" target="_blank">https://pagure.io/fedora-workstation/issue/463</a> * worked with anaconda team to figure out why they couldn't get the 'report our test results to the wiki' thing working * added a <a href="https://fosstodon.org/tags/openqa" class="mention hashtag" rel="nofollow noopener" target="_blank">#openqa</a> needle for the rather nice new fedora 42 background, poked <a href="https://fosstodon.org/@Conan_Kudo" class="u-url mention" rel="nofollow noopener" target="_blank">@Conan_Kudo</a> to update kde-settings and sddm so <a href="https://fosstodon.org/tags/KDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDE</a> picks it up * sent out my draft validation test changes for anaconda webui - <a href="https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/R7Q2CWEHCZ5Q56RHSIHZ2K5SA5CYOG7C/" rel="nofollow noopener" translate="no" target="_blank">https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/R7Q2CWEHCZ5Q56RHSIHZ2K5SA5CYOG7C/</a>

openSUSE LinuxDon't miss distributions at <a href="https://fosstodon.org/tags/FOSDEM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSDEM</a>! <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> topics like dependency bundling, building distributions & more. Talks include: 🕚 11:00: Bridging the Gap Between <a href="https://fosstodon.org/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora</a> & <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> 🕐 13:00: Engineering Stable Rolling Releases with <a href="https://fosstodon.org/tags/OBS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OBS</a> and <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a> <a href="https://fosdem.org/2025/schedule/track/distributions/" rel="nofollow noopener" translate="no" target="_blank">https://fosdem.org/2025/schedule/track/distributions/</a>

Sam ThursfieldStatus update, 13/12/24Its been an interesting and cold month so far. I made a successful trip to the UK, one of the first times I’ve been back in winter and avoided being exposed to COVID19 since the pandemic, so that’s a step forwards. I’ve been thinking a lot about documentation recently in a few different places where I work or contribute as a volunteer. One such place is within openQA and the GNOME QA initiative, so here’s what’s been happening there recently.The <a href="https://gitlab.gnome.org/GNOME/openqa-tests/-/wikis/QA-testing-monthly-call" rel="nofollow noopener" target="_blank">monthly Linux QA call</a> is one of my 2024 success stories. The goal of the call is to foster collaboration between distros and upstreams, so that we share testing effort rather than duplicating it, and we get issue reports upstream as soon as things break. Through this call I’ve met many of the key people who are do automated testing of GNOME downstream, and we are starting to share ideas for the future.What I want for GNOME is to be able to run QA tests for any open merge request, so we can spot regressions before they even land. As part of the STF+GNOME+Codethink collaboration we got a <a href="https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3419" rel="nofollow noopener" target="_blank">working prototype</a> of upstream QA for GNOME Shell, but to move beyond a prototype, we need to build a more solid foundation. The current GNOME Shell prototype has about 100 lines of copy-pasted openQA code to set up the VM, and this would need to be copied into every other GNOME module where we might run QA tests. I very much do not want so many copies of one piece of code.<a href="https://samthursfield.wordpress.com/wp-content/uploads/2024/12/image-1.png" rel="nofollow noopener" target="_blank"></a>I mentioned this in the QA call and Oli Kurz, who is the openQA product owner at openSUSE, proposed that we put the setup logic directly into os-autoinst, which is openQA’s test runner. The os-autoinst code has a bare ‘<a href="https://github.com/os-autoinst/os-autoinst/blob/master/basetest.pm" rel="nofollow noopener" target="_blank">basetest</a>‘ module which must be customed for the OS under test. Each distro maintains their own infrastructure on top of that to wait for the desktop to start, log in as a user, and so on.Since most of us test Linux, we can reasonably add a <a href="https://github.com/os-autoinst/os-autoinst/issues/2583" rel="nofollow noopener" target="_blank">more specific base class specific to Linux</a>, and some further helpers for systemd-based OSes. I love this idea as we could now share improvements between all the different QA teams.So the base test class can be extended, but how do we document its capabilities? I find openQA’s existing documentation pretty overwhelming as a <a href="http://open.qa/docs/" rel="nofollow noopener" target="_blank">single 50,000 word document</a>. It’s not feasible for me to totally rework the documentation, but if we’re going to collaborate upstream then we need to have some way to document the new base classes. Of course I also wrote some <a href="https://gitlab.gnome.org/GNOME/gnome-build-meta/-/wikis/openqa/OpenQA-for-GNOME-developers" rel="nofollow noopener" target="_blank">GNOME specific documentation</a> for QA; but hidden docs like this are doomed to become obsolete. I <a href="https://gitlab.gnome.org/Teams/Websites/developer.gnome.org/-/merge_requests/143" rel="nofollow noopener" target="_blank">began adding a section on testing</a> to the GNOME developer guide, but I’ve had no feedback at all on the merge request, so this effort seems like a dead end.So what should we do to make the QA infrastructure easier to understand? Let me know your ideas below.<a href="https://samthursfield.wordpress.com/wp-content/uploads/2024/12/img_20241203_155310.jpg" rel="nofollow noopener" target="_blank"></a>Looking at the problem from another angle, we still lack a collective understanding of what what openQA is and why you might use it. As a small step towards making this clearer, I wrote a comparison of four testing tools <a href="https://pad.gnome.org/tVzBIusTT2e76tpzP7IbKQ#" rel="nofollow noopener" target="_blank">which you can read here</a>. And at Oli’s suggestion I proposed a new <a href="https://en.wikipedia.org/wiki/Draft:OpenQA" rel="nofollow noopener" target="_blank">Wikipedia page for openQA</a>.<a href="https://en.wikipedia.org/wiki/Draft:OpenQA" rel="nofollow noopener" target="_blank"></a>Please suggest changes here or in the <a href="https://matrix.to/#/#openqa:opensuse.org" rel="nofollow noopener" target="_blank">openQA matrix channel</a>. If you’re reading this and are a Wikipedia reviewer, then I would greatly appreciate a review so we can publish the new page. We could then also add openQA to the Wikipedia <a href="https://en.wikipedia.org/wiki/Comparison_of_GUI_testing_tools" rel="nofollow noopener" target="_blank">“Comparison of GUI testing tools”</a>. Through small efforts like this we can hopefully reduce how much documentation is needed on the GNOME side, as we won’t need to start at “what even is openQA”.I have a lot more to say about documentation but that will have to wait for next month. Enjoy the festive season and I hope your 2025 gets off to a good start!<a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://samthursfield.wordpress.com/tag/gnome/" target="_blank">#gnome</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://samthursfield.wordpress.com/tag/openqa/" target="_blank">#openqa</a>

openSUSE LinuxLearn to master bug reporting with <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a>. Check out this <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> Conference talk to understand the logs, identify product bugs 🐛 & file reports seamlessly. <a href="https://youtu.be/3xsGGvoZEt8?si=nfZKVTEzTY8tTEb0" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/3xsGGvoZEt8?si=nfZKVTEzTY8tTEb0</a>

openSUSE LinuxLearn how to use <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a> to file effective bug reports! 🐞💻 This <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> Conference video looks at identifying product bugs, grabbing logs & submitting clear reports via the openQA <a href="https://fosstodon.org/tags/webUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#webUI</a>. Boost your bug-reporting skills & help us keep things green! 🌱 <a href="https://youtu.be/O6YNJkVu0Dw?si=i8_z0l9N6wCpCmhb" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/O6YNJkVu0Dw?si=i8_z0l9N6wCpCmhb</a>

openSUSE Linux🧑‍💻🔍 <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a> is key to delivering stable systems for <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a>'s distributions and flavors! check out this showcase on it ecosystem, <a href="https://fosstodon.org/tags/features" class="mention hashtag" rel="nofollow noopener" target="_blank">#features</a> and more. <a href="https://youtu.be/cLyEpkJSD88?si=QkaEHuXJwLuRqqtY" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/cLyEpkJSD88?si=QkaEHuXJwLuRqqtY</a>

Adam Williamson :fedora:yesterday (sorry, had enough of computers): * lots of discussion/planning around some potential infra hardware moves * caught up with <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> 41 blocker herding * worked through most <a href="https://fosstodon.org/tags/rawhide" class="mention hashtag" rel="nofollow noopener" target="_blank">#rawhide</a> <a href="https://fosstodon.org/tags/openqa" class="mention hashtag" rel="nofollow noopener" target="_blank">#openqa</a> compose test failures - <a href="https://bugzilla.redhat.com/show_bug.cgi?id=2319565" rel="nofollow noopener" translate="no" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=2319565</a> , <a href="https://bugzilla.redhat.com/show_bug.cgi?id=2319354" rel="nofollow noopener" translate="no" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=2319354</a> , some needles I didn't commit yet * revived <a href="https://pagure.io/fedora-iot/pungi-iot/pull-request/102" rel="nofollow noopener" translate="no" target="_blank">https://pagure.io/fedora-iot/pungi-iot/pull-request/102</a> now pungi should be fixed * poked at a test kiwi build for <a href="https://pagure.io/releng/issue/12398" rel="nofollow noopener" translate="no" target="_blank">https://pagure.io/releng/issue/12398</a> with <a href="https://fosstodon.org/@nirik" class="u-url mention" rel="nofollow noopener" target="_blank">@nirik</a> and <a href="https://fosstodon.org/@Conan_Kudo" class="u-url mention" rel="nofollow noopener" target="_blank">@Conan_Kudo</a>

Adam Williamson :fedora:today 2/2: * surveyed the state of current <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> <a href="https://fosstodon.org/tags/openqa" class="mention hashtag" rel="nofollow noopener" target="_blank">#openqa</a> worker deployments ahead of the planned outage next week to redeploy them all - <a href="https://pagure.io/fedora-infrastructure/issue/12206#comment-936883" rel="nofollow noopener" translate="no" target="_blank">https://pagure.io/fedora-infrastructure/issue/12206#comment-936883</a> * reviewed an mwclient PR - <a href="https://github.com/mwclient/mwclient/pull/365" rel="nofollow noopener" translate="no" target="_blank">https://github.com/mwclient/mwclient/pull/365</a> * updated several <a href="https://fosstodon.org/tags/openqa" class="mention hashtag" rel="nofollow noopener" target="_blank">#openqa</a> test needles for Rawhide changes (in progress)

Adam Williamson :fedora:today: * ran <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> 41 blocker review meeting * investigated a kernel 6.11 bug with my laptop and dock - <a href="https://bugzilla.kernel.org/show_bug.cgi?id=219198#c5" rel="nofollow noopener" translate="no" target="_blank">https://bugzilla.kernel.org/show_bug.cgi?id=219198#c5</a> * tried to deal with periodic failures in the <a href="https://fosstodon.org/tags/openqa" class="mention hashtag" rel="nofollow noopener" target="_blank">#openqa</a> <a href="https://fosstodon.org/tags/freeipa" class="mention hashtag" rel="nofollow noopener" target="_blank">#freeipa</a> replica test - <a href="https://pagure.io/fedora-qa/os-autoinst-distri-fedora/c/3c3ed87" rel="nofollow noopener" translate="no" target="_blank">https://pagure.io/fedora-qa/os-autoinst-distri-fedora/c/3c3ed87</a> * tried to backport a GTK fix, it blew up - <a href="https://bugzilla.redhat.com/show_bug.cgi?id=2307728#c11" rel="nofollow noopener" translate="no" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=2307728#c11</a> * backported some Koji / Kiwi fixes - <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2024-bc8e38e03c" rel="nofollow noopener" translate="no" target="_blank">https://bodhi.fedoraproject.org/updates/FEDORA-2024-bc8e38e03c</a> * openQA tests broke because kernel.org was down on IPv4, reported (they fixed it), worked around it * did a bit of <a href="https://fosstodon.org/tags/mwclient" class="mention hashtag" rel="nofollow noopener" target="_blank">#mwclient</a> work

Adam Williamson :fedora:today: * fixed <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> <a href="https://fosstodon.org/tags/openqa" class="mention hashtag" rel="nofollow noopener" target="_blank">#openqa</a> container compose test for a required syntax change in the kiwi call * saw it broke *again* later in the day which sent me and <a href="https://fosstodon.org/@Conan_Kudo" class="u-url mention" rel="nofollow noopener" target="_blank">@Conan_Kudo</a> down a fun ISO spec rabbit hole, bodged it for now with <a href="https://pagure.io/fedora-kiwi-descriptions/pull-request/75" rel="nofollow noopener" translate="no" target="_blank">https://pagure.io/fedora-kiwi-descriptions/pull-request/75</a> * fixed a bug in my compose metadata keep changes and got them merged to all release branches - <a href="https://pagure.io/pungi-fedora/pull-request/1321" rel="nofollow noopener" translate="no" target="_blank">https://pagure.io/pungi-fedora/pull-request/1321</a> etc. * finished mwclient integration test PR, fixed another bug on the way - <a href="https://github.com/mwclient/mwclient/pull/352" rel="nofollow noopener" translate="no" target="_blank">https://github.com/mwclient/mwclient/pull/352</a> , <a href="https://github.com/mwclient/mwclient/pull/353" rel="nofollow noopener" translate="no" target="_blank">https://github.com/mwclient/mwclient/pull/353</a>

openSUSE Linux🚀 Check out our latest video on <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a> during this year's <a href="https://fosstodon.org/@opensuse" class="u-url mention" rel="nofollow noopener" target="_blank">@opensuse</a>! Conference! Learn how to identify <a href="https://fosstodon.org/tags/bugs" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugs</a>, gather logs, file reports & use the <a href="https://fosstodon.org/tags/webUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#webUI</a>. 📺 <a href="https://fosstodon.org/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#software</a> <a href="https://fosstodon.org/tags/QA" class="mention hashtag" rel="nofollow noopener" target="_blank">#QA</a> <a href="https://fosstodon.org/tags/Automation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Automation</a> <a href="https://youtu.be/3xsGGvoZEt8?si=tRJ2PvAmMnTVCRUL" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/3xsGGvoZEt8?si=tRJ2PvAmMnTVCRUL</a>

openSUSE LinuxLet us know what types of questions you have regarding <a href="https://fosstodon.org/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> software with <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a>. Please share any specific scenarios or challenges so that we can address it in a <a href="https://fosstodon.org/tags/tutorial" class="mention hashtag" rel="nofollow noopener" target="_blank">#tutorial</a> video.

Fedora ProjectHow does Fedora test our images? Not without automation that's for sure! Here's a look at our openQA deployment which we use for automated testing, including a recent upgrade to the cloud.➡️ <a href="https://fedoramagazine.org/fedoras-openqa-cloud-deployment/" rel="nofollow noopener" translate="no" target="_blank">https://fedoramagazine.org/fedoras-openqa-cloud-deployment/</a>If you want to learn more about the Fedora Quality Team, <a href="https://fosstodon.org/@adamw" class="u-url mention" rel="nofollow noopener" target="_blank">@adamw</a> is a great person to follow!<a href="https://fosstodon.org/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora</a> <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

openSUSE LinuxQuality Engineering tackles elusive bugs using <a href="https://fosstodon.org/tags/openQA" class="mention hashtag" rel="nofollow noopener" target="_blank">#openQA</a>! Dive into our fast workflows and tools for debugging and squashing bugs with this <a href="https://fosstodon.org/tags/livestream" class="mention hashtag" rel="nofollow noopener" target="_blank">#livestream</a> <a href="https://www.youtube.com/live/RIy0f7HZgo0?si=qeDgHcJbNMWSldwI" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/live/RIy0f7HZgo0?si=qeDgHcJbNMWSldwI</a>

Recent searches

Search options

Administered by:

Server stats:

#openqa