From Fedora Project Wiki

mNo edit summary
(add ExecDB and OpenQA)
Line 12: Line 12:
; [[ResultsDB]] : A generic storage of (automated) test results. Designed to be lightweight, simple, scalable and fast. It's used by our automation frameworks (AutoQA and Taskotron).
; [[ResultsDB]] : A generic storage of (automated) test results. Designed to be lightweight, simple, scalable and fast. It's used by our automation frameworks (AutoQA and Taskotron).


; [[AutoQA]] : AutoQA is an framework that provides tests, methods for automated execution, and displays for test results.  AutoQA relies on the [[Autotest]] test harness for job scheduling and execution.  Visit the [https://fedorahosted.org/autoqa AutoQA] trac instance for development milestones and source code.  AutoQA is an outgrowth of FudCon F11 [[Automated QA Testing Project|collaboration]]. ''This project is going to be replaced by Taskotron.''
; [https://bitbucket.org/rajcze/execdb ExecDB] : 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 [https://phab.qadevel.cloud.fedoraproject.org/w/taskotron/planning/execdb_features/ concepts].
 
; [https://openqa.opensuse.org/ OpenQA] : We use this tool developed by OpenSUSE to automate certain release test cases, especially installation with [[Anaconda]]. We develop [https://bitbucket.org/rajcze/openqa_fedora Fedora tests] for OpenQA, along with some [https://bitbucket.org/rajcze/openqa_fedora_tools helper tools].
 
; [[AutoQA]] : AutoQA is an framework that provides tests, methods for automated execution, and displays for test results.  AutoQA relies on the [[Autotest]] test harness for job scheduling and execution.  Visit the [https://fedorahosted.org/autoqa AutoQA] trac instance for development milestones and source code.  AutoQA is an outgrowth of FudCon F11 [[Automated QA Testing Project|collaboration]]. '''This project has been replaced by Taskotron.'''


; [http://beaker.fedoraproject.org Beaker] : Beaker is an up and coming fully automated test framework that provides bare metal hardware provisioning including console and power management, and job scheduling and execution. Learn more at [http://beaker-project.org/ Beaker homepage].
; [http://beaker.fedoraproject.org Beaker] : Beaker is an up and coming fully automated test framework that provides bare metal hardware provisioning including console and power management, and job scheduling and execution. Learn more at [http://beaker-project.org/ Beaker homepage].

Revision as of 11:48, 26 March 2015

QA.png

The QA team develops tools to make testing easier and more repeatable. Developing open source quality assurance tools is complex and challenging stuff at the cutting edge of the field. Contact Tim Flink if you're up to the challenge of building new tools for Fedora QA.

QA tools

Test Automation

Taskotron
Taskotron is our current in-development 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 is intended to obsolete AutoQA.
ResultsDB
A generic storage of (automated) test results. Designed to be lightweight, simple, scalable and fast. It's used by our automation frameworks (AutoQA and Taskotron).
ExecDB
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.
OpenQA
We use this tool developed by OpenSUSE to automate certain release test cases, especially installation with Anaconda. We develop Fedora tests for OpenQA, along with some helper tools.
AutoQA
AutoQA is an framework that provides tests, methods for automated execution, and displays for test results. AutoQA relies on the Autotest test harness for job scheduling and execution. Visit the AutoQA trac instance for development milestones and source code. AutoQA is an outgrowth of FudCon F11 collaboration. This project has been replaced by Taskotron.
Beaker
Beaker is an up and coming 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.

Installation

SNAKE
Smart Network Automated Kickstart Environment. A small tool to assist with installing and pykickstart-based library for modeling sustainable kickstarts.

Release validation testing

python-wikitcms and relval
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).

Test case reporting

Test Days Frontend
A web application for providing results from Test Days events. It uses ResultsDB (legacy) as a backend.

Bug reporting

Blocker Bugs App
A web application to display current blocker bugs during our pre-release cycle.
python-bugzilla
Command-line interaction with Bugzilla. Supports searching, creating and modifying bugs.

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.

Mixed bag

Fedora QA scripts
A git repository containing various small scripts.


Infrastructure tools

These tools we use as our support infrastructure during QA tools development.

Bitbucket team repository
A list of repositories that are related to our tools and needs.
Phabricator
Our main issue and code review tracker for most of our projects.