[Masterview-devel] Unit tests and directive loading

[Jeff Barczewski]

On 10/5/06, Deb Lewis <djlewis at acm.org> wrote:
> Jeff - figured out why running the unit test suite went whacko even though
> individual tests all run.  Combination of not having a check in directive
> unit tests that exposed the issue (the "missing test" condition!) and a
> legit consequence of the changes being mad in directive loading, metadata
> specification, and shift to separate mv: and mvx: namespaces (builtin vs.
> addon directives).
>
> So... I have to make a sweep over *all* the unit tests for directives and
> tweak their loading setup; simply doing require on the direcive impl class
> doesn't have the same effect as "normal" masterview system loading anymore.
> [explanation below].
>
> Not thrilled with this and it has ripples out to how a directive developer
> has to set up their tests as well, but don't see an alternative yet.
>
> We needed to make a cleanup pass through our directive test cases anyway to
> switch everything over to the simplifed DirectiveTestHelper services, so
> this was needed at some point anyway.
>
> ~ Deb
>
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> ON DIRECTIVE LOADING, METADATA DEFAULTS, AND NAMESPACES
>
> I starting writing this up here and it got long and I concluded we should
> capture this more reliably in our own documentation, so I put a design note
> on this subject into our underutilized masterview-devel project that resides
> alongside the main masterview code project in the repository:
>
> masterview/trunk/masterview-devel/design_notes/DirectiveLoadingAndMetadataDe
> faults.txt
>
> Some form of this eventually ought to get into proper docs in the masterview
> project proper, but for now I just wanted to capture the working design
> notes and rationale.
>
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Ok, thanks for the heads up. I will take a look at it.