# Advanced Dependencies Test Suite Do we care to make the test bundle realistic in any way? * We can have a mega test bundle that does dependencies, separate from our main bundle if it causes performance problems * Then have an example bundle or two in our examples repo that really walks through how to use the feature. Make a paired tutorial to explain how to use them. What should our test bundle(s) have so that we have exercise all of depsv2? * More than one level deep of dependencies. So root -> A -> B * Supports a range of bundle versions, e.g. mysql bundle has more than one available version * Has a bundle interface specified as a bundle reference. This bundle could be a porter bundle or something handmade and published just to provide an interface * Has an embeded bundle interface that requires the output has a specific id * Additional interface requirements are applied to the dependency based on how it is used (i.e. we expect it to generate an output) * Pass an output from one dependency to another (e.g. an ip address or connection string) and use an output in the main bundle. * Create a "meta" bundle that doesn't do anything on its own but just ties together sub-bundles Install Matrix * install standalone and have it setup all its dependencies using defaults * install and reuse an existing installation based on criteria (labels * install and using a more recent version of a dependency * install and specify an existing installation to reuse (without resolving it, just sub it in) *