Comment 3 for bug 1569540

We have a VERY similar need for certification and snappy where reusability of testplan sections becomes critical and we also would like to reduce maintenance costs and error prone copy/pastes.

I'm working on a new feature for nested testplans, example:

unit: test plan
id: foo
_name: bar
_description:
 baz
estimated_duration: 10m
include:
    foo/.*
nested_part:
    2013.com.canonical.certification::toto
    2016.com.canonical.certification::bibi
bootstrap_include:
    titi
certification_status_overrides:
    apply blocker to 2013.com.canonical.certification::zozo/false

Loading nested parts will load the include, mandatory_include and bootstrap_include sections and all overrides (category, certification status).

The testplan order will then be testplan "include" + all nested testplan "include" in the same order they are defined in "nested_part"