Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Release Validation Testing in Fedora QA

DZone's Guide to

Release Validation Testing in Fedora QA

How to set up your system for testing with Fedora to help make great contributions to the OSS community.

· DevOps Zone
Free Resource

The Nexus Suite is uniquely architected for a DevOps native world and creates value early in the development pipeline, provides precise contextual controls at every phase, and accelerates DevOps innovation with automation you can trust. Read how in this ebook.

Release validation testing is a process which takes place before an official Fedora release. (Fedora is the upstream, community project from which RHEL is built.) Before the Final (GA) release, we have Alpha and Beta pre-releases, and at each of these milestones, nightly builds (nightlies) and composes are released and tested to ensure that the release meets quality standards. Release validation testing is one way you can help Fedora get better, and this post will talk about how you can start from scratch.

Setting Up Your System for Testing

You can start off by grabbing the image of the Fedora compose you want to test from here (in my case, I will demo with Fedora-KDE-Live-x86_64-24-20160424.n.0 )

Once downloaded, you need to create a Virtual Machine (VM), or you can test it as the primary operating system of your computer, but, since there may be bugs it is advised to start off with a VM – the perfect place to play with new technology. A default configuration of 20GB hard drive and 1024MB memory should be enough to execute the test cases.

Enabling Update-Testing Repo and Installing

You can choose to report results in two ways: either you can go ahead and edit the wiki directly, or you can execute the following commands:

dnf install python-wikitcms
dnf install relval

Finding the Test Cases and Posting Results

Now that you are all set to run tests, let’s find a test case and let me walk you through the process.

Test cases can be found here (note that I’m writing this for Fedora 24, hence I am using the F24 test cases).

I will take up a basic test case of an “installation” category, run it, and post my results:

To run the test case, we can go ahead with relval size-check --username YOUR_FAS_USERNAME (FAS username).

After execution, your screen will look like the following image, and results will be automatically be posted in the result matrix:

Results of my test can be found in the wiki page matrix:

That’s how we can go ahead and perform release validation tests. Good luck, and we hope to see your test results! Give it a try and help out the Fedora Linux and RHEL communities!

The DevOps Zone is brought to you in partnership with Sonatype Nexus.  See how the Nexus platform infuses precise open source component intelligence into the DevOps pipeline early, everywhere, and at scale. Read how in this ebook

Topics:
fedora ,qa

Published at DZone with permission of Sumantro Mukherjee. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}