openmct/platform/framework/test/suite.json

[
    "FrameworkInitializer",
    "bootstrap/ApplicationBootstrapper",
    "load/Bundle",
    "load/BundleLoader",
    "load/Extension",
    "register/CustomRegistrars",
    "register/ExtensionRegistrar",
    "register/PartialConstructor",
    "register/ServiceCompositor",
    "resolve/BundleResolver",
    "resolve/ExtensionResolver",
    "resolve/ImplementationLoader",
    "resolve/RequireConfigurator"
]
[Tests] Initial spec runner Initial spec runner; looks in bundles, assumes conventions. Supports initial repository set up and build scripts, for WTD-519. 2014-10-30 17:24:30 -07:00			`[`
[Framework] Add skeleton specs Add empty specs for all classes introduced for the framework layer, WTD-518. Note that Main is omitted, as this launches the full application. 2014-11-06 08:03:35 -08:00			`"FrameworkInitializer",`
			`"bootstrap/ApplicationBootstrapper",`
			`"load/Bundle",`
			`"load/BundleLoader",`
			`"load/Extension",`
			`"register/CustomRegistrars",`
			`"register/ExtensionRegistrar",`
			`"register/PartialConstructor",`
			`"register/ServiceCompositor",`
			`"resolve/BundleResolver",`
			`"resolve/ExtensionResolver",`
[Framework] Add RequireJS configurator Add a configuration step (as part of the resolve phase) to the framework layer, where bundle-defined paths and shims are passed to RequireJS configuration. This permits both the use of non-AMD modules and the exposure of libraries across bundles. WTD-568. 2015-01-02 17:46:50 -08:00			`"resolve/ImplementationLoader",`
			`"resolve/RequireConfigurator"`
[Tests] Initial spec runner Initial spec runner; looks in bundles, assumes conventions. Supports initial repository set up and build scripts, for WTD-519. 2014-10-30 17:24:30 -07:00			`]`