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:57, 4 January 2011
, 4 January 2011→ManifestDestiny: note new repository location
(add a contact section) |
(→ManifestDestiny: note new repository location) |
||
| 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 http:// | ManifestDestiny is software for reading test manifests in a proposed .ini file format. The source code is available at http://hg.mozilla.org/automation/ManifestDestiny , though it may be moved if a better repository can be found. Brief instructions can be found in the README.txt file in that mercurial repository as well as in the tests. | ||
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. | ||