947
edits
Auto-tools/Projects/ManifestDestiny: Difference between revisions
Jump to navigation
Jump to search
m
Auto-tools/Projects/ManifestDestiny (view source)
Revision as of 01:34, 15 December 2010
, 15 December 2010→Architecture
(→Architecture: briefly note architecture) |
m (→Architecture) |
||
| Line 40: | Line 40: | ||
ManifestDestiny uses a two-tiered 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. | In addition, a harness may (optionally) have a harness-specific integration layer to make use of conventions appropriate only for that test type. | ||