QA/Tools

From FedoraProject

< QA(Difference between revisions)
Jump to: navigation, search
(Test case reporting)
(add Phabricator and restructure)
 
Line 1: Line 1:
 
{{header|qa}}
 
{{header|qa}}
 
{{autolang|base=yes}}
 
{{autolang|base=yes}}
 
__NOTOC__
 
  
 
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 [[User:tflink|Tim Flink]] if you're up to the challenge of building new tools for Fedora QA.
 
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 [[User:tflink|Tim Flink]] if you're up to the challenge of building new tools for Fedora QA.
  
= General =
+
= QA tools =
  
; [http://git.fedorahosted.org/git/?p=fedora-qa.git Fedora QA scripts] : This is a Fedora QA Git repository containing various small scripts that are related to our tasks.
+
== Test Automation ==
 
+
; [https://bitbucket.org/fedoraqa Bitbucket team repository] : A list of repositories that are related to our tools and needs.
+
 
+
= 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]].
 
; [[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]].
Line 22: Line 16:
 
; [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].
  
= Installation =
+
== Installation ==
  
 
; [https://fedorahosted.org/snake SNAKE] : Smart Network Automated Kickstart Environment.  A small tool to assist with installing and pykickstart-based library for modeling sustainable kickstarts.
 
; [https://fedorahosted.org/snake SNAKE] : Smart Network Automated Kickstart Environment.  A small tool to assist with installing and pykickstart-based library for modeling sustainable kickstarts.
  
= Test case reporting =
+
== Test case reporting ==
  
 
; [http://testdays.qa.fedoraproject.org/testdays/all_events Test Days Frontend] : A web application for providing results from [[QA/Test Days|Test Days]] events. It uses ResultsDB (legacy) as a backend.
 
; [http://testdays.qa.fedoraproject.org/testdays/all_events Test Days Frontend] : A web application for providing results from [[QA/Test Days|Test Days]] events. It uses ResultsDB (legacy) as a backend.
  
= Bug reporting =
+
== Bug reporting ==
  
 
; [https://qa.fedoraproject.org/blockerbugs/ Blocker Bugs App] : A web application to display current [[QA:SOP blocker bug process|blocker bugs]] during our pre-release cycle.
 
; [https://qa.fedoraproject.org/blockerbugs/ Blocker Bugs App] : A web application to display current [[QA:SOP blocker bug process|blocker bugs]] during our pre-release cycle.
Line 36: Line 30:
 
; [https://fedorahosted.org/python-bugzilla/ python-bugzilla] : Command-line interaction with [https://bugzilla.redhat.com/ Bugzilla]. Supports searching, creating and modifying bugs.
 
; [https://fedorahosted.org/python-bugzilla/ python-bugzilla] : Command-line interaction with [https://bugzilla.redhat.com/ Bugzilla]. Supports searching, creating and modifying bugs.
  
= Test update feedback =
+
== Test update feedback ==
  
 
; [[Fedora Gooey Karma]] : A graphical tool that makes it easy to report feedback for any updates-testing packages currently installed.
 
; [[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 Easy Karma]] : A command line tool that makes it easy to report feedback for any updates-testing packages currently installed.
 +
 +
== Mixed bag ==
 +
 +
; [http://git.fedorahosted.org/git/?p=fedora-qa.git Fedora QA scripts] : A git repository containing various small scripts.
 +
 +
 +
= Infrastructure tools =
 +
 +
These tools we use as our support infrastructure during QA tools development.
 +
 +
; [https://bitbucket.org/fedoraqa Bitbucket team repository] : A list of repositories that are related to our tools and needs.
 +
 +
; [[QA/Phabricator|Phabricator]] : Our main issue and code review tracker for most of our projects.
 +
  
 
[[Category:QA]]
 
[[Category:QA]]

Latest revision as of 08:57, 28 January 2014

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.

Contents

[edit] QA tools

[edit] 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).
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 is going to be 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.

[edit] Installation

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

[edit] Test case reporting

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

[edit] 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.

[edit] 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.

[edit] Mixed bag

Fedora QA scripts 
A git repository containing various small scripts.


[edit] 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.