From Fedora Project Wiki

m (link to Phab wiki page)
(phabricator is discontinued)
(18 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== Overview ==
== Overview ==


'''Taskotron''' is a framework for automated test execution. It is in very early stages of development with the objective to replace [[AutoQA]] for automating selected QA tasks in Fedora.
'''Taskotron''' is a framework for automated task execution. It currently runs selected package checks in Fedora.


Some of its major envisioned features:
Some of its major envisioned features:
Line 12: Line 12:
* Useful for other Linux distributions as well, not just Fedora
* Useful for other Linux distributions as well, not just Fedora


== Our systems ==


== Read more ==
* [https://taskotron.fedoraproject.org/ Taskotron production instance]
* [https://taskotron.stg.fedoraproject.org/ Taskotron staging instance]
* [http://taskotron-dev.fedoraproject.org/ Taskotron development instance]


There's not much documentation yet, but we are working on it. For the moment, you can read:
== Source code, getting involved and contributing ==


* [[User:Tflink/taskotron development plan]]
Taskotron consists of multiple separate components, mainly hosted in the [https://pagure.io/group/taskotron {{code|taskotron}} namespace in Pagure]. The general tasks that are developed along with Taskotron are named with the ''task-'' prefix.
* [[User:Tflink/taskotron development subprojects]]
 
* [[User:Tflink/taskotron contribution guide]]
Please see the [[Taskotron contribution guide|contribution guide]] for instructions how to contribute.
* [http://roshi.fedorapeople.org/dexy-themed Install a dev instance]
* [[:Category:Taskotron]]


This documents some of the reasons for re-implementing AutoQA as Taskotron:
The main mailing list for Taskotron discussion is {{fplist|qa-devel}}. The main IRC channel is {{fpchat|#fedora-qa}}.
* [http://tirfa.com/down-with-test-automation-long-live-task-automation.html Down With Test Automation! Long Live Task Automation!]
* [http://tirfa.com/an-initial-idea-for-taskbot.html An Initial Idea for Taskbot]
* [http://tirfa.com/how-is-taskbot-different-from-autoqa.html How is Taskbot Different from AutoQA?]


== Get involved ==
== Documentation and further reading ==


* '''[[User:Tflink/taskotron contribution guide]] - a quick start guide'''
Please see the [https://qa.fedoraproject.org/docs/libtaskotron/latest/quickstart.html Libtaskotron quick start] and the [https://qa.fedoraproject.org/docs/libtaskotron/latest/ Taskotron documentation]. You may also find this further reading of interest:
* [https://bitbucket.org/fedoraqa Fedora QA on Bitbucket] - our code repositories
* [[QA/Phabricator|Phabricator]] - ticket tracking and code review system
* [https://admin.fedoraproject.org/mailman/listinfo/qa-devel qa-devel] - a mailing list for development discussion of Taskotron and other [[QA/Tools|QA tools]]
* {{fpchat|#fedora-qa}} - our IRC channel


* [[User:Tflink/taskotron development plan]]
* [[User:Tflink/taskotron development subprojects]]
* [[:Category:Taskotron]]
* [http://tirfa.com/tag/taskotron.html Tim Flink's blog - Taskotron tag]
* [[Taskotron/Tasks | Current Tasks]]


[[Category:QA]] [[Category:Taskotron]]
[[Category:QA]]
[[Category:Taskotron]]

Revision as of 12:50, 7 August 2017

Overview

Taskotron is a framework for automated task execution. It currently runs 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

Our systems

Source code, getting involved and contributing

Taskotron consists of multiple separate components, mainly hosted in the taskotron namespace in Pagure. The general tasks that are developed along with Taskotron are named with the task- prefix.

Please see the contribution guide for instructions how to contribute.

The main mailing list for Taskotron discussion is qa-devel. The main IRC channel is #fedora-qa[?].

Documentation and further reading

Please see the Libtaskotron quick start and the Taskotron documentation. You may also find this further reading of interest: