I am currently working on a custom result listener able to retrieve all package dependencies of a test plan. In our team a test plan often consists of individual test plan references to individual system validation tests.
Through a bug I was made aware that the XML string of a test plan does not include the package dependencies of test plan references.
How can I access the package dependencies of these test plan references? Besides the obvious (and tedious) task of accessing the reference filepath and accessing the XML through that is there a better way?
Hi @jb111,
For context, the TestPlanPackageDependencySerializer class handles this process. During serialization, it keeps track of all the types it encounters. At the end, it performs a lookup to determine which plugin package each type originates from.
The absence of inherited package dependencies from a test plan reference isn’t a bug but rather a consequence of the loose coupling between test plans. This design allows you to replace a referenced test plan with another that may have different dependencies, but also prevents absolute knowledge of the dependencies before you actually try to load it.