This page has information about the project to de-couple Fuego's
test log parser, to make it a standalone program.

Neil Williams had some good feedback (some of it negative) on the
automated testing mailing list.

This page seeks to organize that content, and capture ideas about
the process of making Fuego's parser standalone.

vision [edit section]

= vision =
Create a standalone test program output parser, that can be used
by multiple test systems, so that parsing is not baked into
each test system.

Let it develop on its own, independent of a particular test system.

input [edit section]

= input =
Run artifacts from a test program
 * stdout
 * kernel output (console log during run)
 * stderr
 * return code
 * trace during run
 * system log during run (with items from the test program)

There can be multiple channels of information to extract data from
during a test program run.

format, markers or tags [edit section]

== format, markers or tags ==
 * TAP
 * LAVA

output [edit section]

= output =
Standardized output in multiple formats:
 * junit
 * xunit
 * kernelci format
 * squad format
 * run.json (should be similar to kernelci)

current dependencies on Fuego [edit section]

= current dependencies on Fuego =
 * Fuego environment variables
   * FIXTHIS - list vars here
 * Fuego paths?