It supports automated testing of embedded targets from a host system, as it's primary method of test execution.
The quick introduction to Fuego is that it consists of a host/target script engine, with a Jenkins front-end, and over 50 pre-packaged tests, installed in a docker container.
The slides from LCJ are available here: Introduction-to-Fuego-LCJ-2016.pdf
And here is the video from ELC: YouTube video
You can find more presentations about Fuego on our Presentations page.
Fuego Quickstart Guide for how to get up an running quickly in Fuego.
To use Fuego, download both of these, in parallel directories. They are downloadable with the commands.
- Documentation has information on this wiki.
Note that this is a new list (as of September 2016). Previously, discussions about Fuego (and its predecessor JTA) were held on the ltsi-dev mailing list:
See the Presentations page for a list of presentations that you can read or view for more information about Fuego.
It can be summed up like this:
There are numerous aspects of testing that are still done in an ad-hoc and company-specific way. Although there are open source test frameworks (such as Jenkins or LAVA), and open source test programs (such as cylictest, LTP, linuxbench, etc.), there are lots of aspects of Linux testing that are not shared.
The purpose of Fuego is to provide a test framework for testing embedded Linux, that is distributed and allows individuals and organizations to easily run their own tests, and at the same time allows people to share their tests and test results with each other.
Historically, test frameworks for embedded Linux have been difficult to set up, and difficult to extend. In cases where a test program was reasonably self-contained, the test system was not easy to to extend. Many Linux test systems are not easily applied in cross or embedded environments. Some very full frameworks are either not viewed as processor-neutral, and are difficult to set up, or are targeted at running tests on a dedicated group of boards or devices.
The vision of open source in general is one of sharing source code and capabilities, to expand the benefits to all participants in the ecosystem. The best way to achieve this is to have mechanisms to easily use the system, and easily share enhancements to the system, so that all participants can use and build on each others efforts.
The goal of Fuego is to provide a framework that any group can install and use themselves, while supporting important features like cross-compilation, host/target test execution, and easy test administration. Test administration consists of starting tests (both manually and automatically), viewing test results, and detecting regressions. Ease of use is critical, to allow testers to use tests that are otherwise difficult to individually set up, configure, and interpret the results from. It is also important to make it very easy to share tests (scripts, configuration, results parsing, and regression detection methods).
Some secondary goals of this project are the ability for 3rd parties to initiate or schedule tests on our hardware, and the ability to share our test results with others.
The use of Jenkins as the core of the test framework already supports many of the primary and secondary goals. The purpose of this project is to augment the Jenkins system to support embedded configurations of Linux, and to provide a place for centralized sharing of test configurations and collateral.
There is no such thing as a "Linux Test distribution". Fuego aims to be this. It intends to provide test programs, scripts to build, deploy and run them, and tools to analyze, track, and visualize test results.
For more details about a high-level vision of open source testing, please see OSS Test Vision.
http://elinux.org/Fuego has some historical information about Fuego.
Other test systems for notes and comparisons
Fuego To Do List
See http://fuegotest.org/fuego-1.5/FrontPage for the 1.5 version of this wiki. It's under construction.
Help for documentation about this wiki.