947
edits
Auto-tools/Projects/ManifestDestiny: Difference between revisions
Jump to navigation
Jump to search
Auto-tools/Projects/ManifestDestiny (view source)
Revision as of 23:44, 5 December 2011
, 5 December 2011→ManifestDestiny: correct links
(add link to integration) |
(→ManifestDestiny: correct links) |
||
| Line 1: | Line 1: | ||
= ManifestDestiny = | = ManifestDestiny = | ||
ManifestDestiny is software for reading test manifests in a proposed .ini file format. The source code is available at | ManifestDestiny is software for reading test manifests in a proposed .ini file format. The source code is available at | ||
https://github.com/mozilla/mozbase/tree/master/manifestdestiny. The canonical documentation lives at https://github.com/mozilla/mozbase/blob/master/manifestdestiny/README.mdwhich should be consulted for up-to-date and more thorough documentation. This wiki page just serves as a convenience stub. | |||
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. | 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 == | == File Format == | ||
Tests represented as sections in the .ini files: | Tests represented as sections in the .ini files. A simple test containing one file, 'aTest.js' would look like: | ||
[aTest.js] | [aTest.js] | ||