Autoqa Architecture Fedora Project Wiki Autoqa defines "watchers" that look for various "events" happening within the fedora development build process and then announce them. a single watcher can check for and then announce multiple events. Every watcher has one or more events associated with it. watchers are run by cron or otherwise, and for every event detected they run the autoqa script to schedule appropriate test. the 'tests' subdirectory contains the tests.
Autoqa Resultsdb Schema Fedora Project Wiki Autoqa is an automated test system for fedora. when certain events occur, autoqa launches automated tests. at present there are event watchers for koji builds, bodhi updates, repo changes, and nightly installed images; these events trigger a small number of tests, but more tests are needed. The project was founded in 2003 as a result of a merger between the red hat linux (rhl) and fedora linux projects. it is sponsored by red hat primarily, but its employees make up only 35% of project contributors, and most of the over 2,000 contributors are unaffiliated members of the community. This document provides a high level technical overview of autoqa agent's system architecture, describing the major layers, components, and data flows that enable the system to execute browser based tests from markdown specifications. A sneak peak into autoqa future plans can be displayed on the following page: fedorahosted.org autoqa roadmap. the information there are by no means complete and immutable, but they try to reflect our best intentions and estimates.
Autoqa Resultsdb Schema Fedora Project Wiki This document provides a high level technical overview of autoqa agent's system architecture, describing the major layers, components, and data flows that enable the system to execute browser based tests from markdown specifications. A sneak peak into autoqa future plans can be displayed on the following page: fedorahosted.org autoqa roadmap. the information there are by no means complete and immutable, but they try to reflect our best intentions and estimates. This page will help you set up an environment for autoqa development. this guide documents approaches that we have found convenient, but of course you can do anything differently, as you like. Looking to contribute? check out whatcanidoforfedora.org, which will guide you to different areas where you can help, and to the people who can help you get started. or, take a look at the join fedora page. All items will be focused on outlining the steps required to accomplish a specific task. this page will detail activities for test developers, administrators, release engineers and package maintainers. this page follows a similar design to the fedora talk admin cases and related pages. The control.autoqa file allows a test to define any scheduling requirements or modify input arguments. this file will decide whether to run this test at all, on what architectures distributions it should run, and so on.
Autoqa Resultsdb Use Cases Fedora Project Wiki This page will help you set up an environment for autoqa development. this guide documents approaches that we have found convenient, but of course you can do anything differently, as you like. Looking to contribute? check out whatcanidoforfedora.org, which will guide you to different areas where you can help, and to the people who can help you get started. or, take a look at the join fedora page. All items will be focused on outlining the steps required to accomplish a specific task. this page will detail activities for test developers, administrators, release engineers and package maintainers. this page follows a similar design to the fedora talk admin cases and related pages. The control.autoqa file allows a test to define any scheduling requirements or modify input arguments. this file will decide whether to run this test at all, on what architectures distributions it should run, and so on.
Fedora Community Ui Guidelines Fedora Project Wiki All items will be focused on outlining the steps required to accomplish a specific task. this page will detail activities for test developers, administrators, release engineers and package maintainers. this page follows a similar design to the fedora talk admin cases and related pages. The control.autoqa file allows a test to define any scheduling requirements or modify input arguments. this file will decide whether to run this test at all, on what architectures distributions it should run, and so on.
Comments are closed.