Merge ~jocave/plainbox-provider-tpm2:create-category-nested-parts into plainbox-provider-tpm2:master

[Jonathan Cave]

Create nested test plans for TPM certification that are not "implementation specific". For example current certification plans include specific tpm-tools jobs for a specific version, but we may wish to add to those with clevis jobs or alter tpm jobs are attempted.

Based on the current selection for the -automated plan these will currently only be able to be used on UC20/20.04.

[Jonathan Cave (jocave)]

self-approve

review: Approve

diff --git a/units/test-plan.pxu b/units/test-plan.pxu
index f7d5eb3..72bc36c 100644
--- a/units/test-plan.pxu
+++ b/units/test-plan.pxu
@@ -92,3 +92,33 @@ include:
     clevis.*
 mandatory_include:
     com.canonical.plainbox::manifest
+
+
+unit: test plan
+id: tpm-cert-full
+_name: TPM tests
+_description:
+  TPM tests that should be run as part of Certification. This could be a
+  collection of tests using a variety of tools
+include:
+nested_part:
+    tpm-cert-manual
+    tpm-cert-automated
+
+unit: test plan
+id: tpm-cert-manual
+_name: TPM tests (Manual)
+_description:
+  TPM tests that should be run as part of Certification. This could be a
+  collection of tests using a variety of tools
+include:
+
+unit: test plan
+id: tpm-cert-automated
+_name: TPM tests (Automated)
+_description:
+  TPM tests that should be run as part of Certification. This could be a
+  collection of tests using a variety of tools
+include:
+nested_part:
+    tpm2.0_4.1.1-automated