From Fedora Project Wiki
m (link to Phab wiki page) |
(→Overview: changed verbage of taskotron description) |
||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
'''Taskotron''' is a framework for automated | '''Taskotron''' is a framework for automated task execution. It is in very early stages of development with the initial objective of replacing [[AutoQA]] for automating selected package checks in Fedora. | ||
Some of its major envisioned features: | Some of its major envisioned features: | ||
| Line 11: | Line 11: | ||
* Trivial local execution - no need to replicate the production environment with all its servers and configurations, the check authors can easily run and develop their checks on their local machine with no unnecessary software setup hassle | * Trivial local execution - no need to replicate the production environment with all its servers and configurations, the check authors can easily run and develop their checks on their local machine with no unnecessary software setup hassle | ||
* Useful for other Linux distributions as well, not just Fedora | * Useful for other Linux distributions as well, not just Fedora | ||
== Read more == | == Read more == | ||
Revision as of 16:36, 15 May 2014
Overview
Taskotron is a framework for automated task execution. It is in very early stages of development with the initial objective of replacing AutoQA for automating selected package checks in Fedora.
Some of its major envisioned features:
- Support for distribution-wide checks - e.g. Can this set of packages be pushed to stable updates repository? or Is this new system compose installable?
- Support for package-related checks - e.g. Can this new build of firefox package be safely updated? or Do the functional tests pass for this new build of openssh?
- Simple check management - package maintainers in full control of their package-related checks, no hurdles
- Event-based - where applicable only the simplest interaction between services is used - passing messages through a message bus - for both check triggering and result reporting. No hardcoded tie-ins to specific services.
- Decoupled design - comprised of loosely-coupled standalone units (tools, libraries) so that important logical functions are separated and one unit can be replaced with a different unit with similar functionality
- Trivial local execution - no need to replicate the production environment with all its servers and configurations, the check authors can easily run and develop their checks on their local machine with no unnecessary software setup hassle
- Useful for other Linux distributions as well, not just Fedora
Read more
There's not much documentation yet, but we are working on it. For the moment, you can read:
- User:Tflink/taskotron development plan
- User:Tflink/taskotron development subprojects
- User:Tflink/taskotron contribution guide
- Install a dev instance
- Category:Taskotron
This documents some of the reasons for re-implementing AutoQA as Taskotron:
- Down With Test Automation! Long Live Task Automation!
- An Initial Idea for Taskbot
- How is Taskbot Different from AutoQA?
Get involved
- User:Tflink/taskotron contribution guide - a quick start guide
- Fedora QA on Bitbucket - our code repositories
- Phabricator - ticket tracking and code review system
- qa-devel - a mailing list for development discussion of Taskotron and other QA tools
- #fedora-qa[?] - our IRC channel