947
edits
Auto-tools/Projects/ManifestDestiny: Difference between revisions
Jump to navigation
Jump to search
Auto-tools/Projects/ManifestDestiny (view source)
Revision as of 01:33, 15 December 2010
, 15 December 2010→Architecture: briefly note architecture
(→ManifestDestiny: note reason for no logic in manifests) |
(→Architecture: briefly note architecture) |
||
| Line 37: | Line 37: | ||
== Architecture == | == Architecture == | ||
ManifestDestiny uses a two-tiered architecture: | |||
- a manifest parser, that will read the tests into the appropriate data structure from the .ini manifests | |||
- a generic integration layer, that will make harness-agnostic conventions functional (e.g. disabling according to operating-system type). | |||
In addition, a harness may (optionally) have a harness-specific integration layer to make use of conventions appropriate only for that test type. | |||
The integration layers contain the logic to turn convention into functionality. | |||
== Usage == | == Usage == | ||