Auto-tools/Projects/ManifestDestiny: Difference between revisions

The main objective of ManifestDestiny, or UniversalManifests in general, is to allow arbitrary key, value annotations on tests or groups of tests.  While the annotations are arbitrary to the parser, an integration layer (either at the harness level or more generically) uses agreed upon convention to determine e.g. what tests to run depending on harness invocation.  Keeping the logic out of the manifests and in the integration layer(s) allows a universal format for manifests, a shared body of code to parse these, and some shared code for the integration layer.  In addition, manifests are kept clean and readable.

== File Format ==