The QA team develops tools to make testing easier and more repeatable. We have several projects ranging from some that are pretty simple and new developer friendly to complex and challenging stuff at the cutting edge of the field. Contact Tim Flink or the qa-devel mailing list if you're interesting in helping to build new tools for Fedora QA.
- Taskotron is our current framework for automatically executing a number of Fedora related tests. Both Fedora infrastructure generic and Fedora packages specific tests should be supported. Package maintainers should have an easy way of providing tests for their packages. This framework obsoleted AutoQA. You can see Taskotron in action.
- A generic storage of (automated) test results. Designed to be lightweight, simple, scalable and fast. Taskotron, openQA and Autocloud (using autocloudreporter) results are reported to ResultsDB.
- A Python library that represents certain conventions for storing results in ResultsDB as code, and makes it easy to report results that comply with the conventions.
- This database with a front-end allows us to track tasks which are scheduled, running and finished in Taskotron. It provides a simple way to navigate people (mostly admin and developer-type folks) into different corners of the Taskotron infrastructure - BuildBot job details, ResultsDB results, logs and artifacts directories. Read some design concepts.
- We use this tool (developed by our friends at SUSE, now with contributions from us too) to automate certain release test cases, especially installation with Anaconda. We develop Fedora tests for openQA, along with a scheduler / result forwarder and a hard disk image creator. The production Fedora instance is here.
- Beaker is a fully automated test framework that provides bare metal hardware provisioning including console and power management, and job scheduling and execution. Learn more at Beaker homepage.
Release validation testing
- python-wikitcms, relval and testdays
- A Python library and CLI based upon it for performing various release validation testing tasks in the Wikitcms 'test management system' (the set of wiki pages in which release validation test results are stored). testdays can perform a few basic operations on Test Day pages. relvalconsumer is a Fedmsg consumer which creates validation test events.
- A script for running informational checks on a Fedora compose and printing or mailing out the results.
- A project comprising a static page generator and some fedmsg consumers that together produce a page linking to the most successful recent compose of each Fedora image for Rawhide and Branched. Also lists most recent successfully-tested image, for images tested by openQA or Autocloud.
Test case reporting
- Test Days App
- A web application for providing results from Test Days events. It uses ResultsDB as a backend.
Test update feedback
- Fedora Gooey Karma
- A graphical tool that makes it easy to report feedback for any updates-testing packages currently installed.
- Fedora Easy Karma
- A command line tool that makes it easy to report feedback for any updates-testing packages currently installed.
- Fedora QA tools
- A git repository containing various small tools.
- Fedora QA statistics tools
- Tools for generating statistics on user contributions. relval also has some functions for doing this. See Recognition for more details.
These tools we use as our support infrastructure during QA tools development.
- Bitbucket team repository
- Bitbucket repositories related to our tools and needs.
- Pagure team namespace
- Pagure repositories related to our tools and needs.
- Pagure Taskotron namespace
- Pagure repositories related to Taskotron.
We are working to ultimately host all repositories in Pagure, but some remain in Bitbucket for now.
- Our main issue and code review tracker for most of our projects.