This approach was favored instead of client-side task #113 because the client feature would overwrite the "Internal\bundle_eval" test log of the PDB Validations.
With this approach based on Asbestos test import extension, test logs are kept intact with the test run and it offers a convenient display.
Example
Within a Test TestScript,
if a test action operation is of "AggregateModule" type then it has 1 test import "TestScriptModule"
then "TestScriptModule" has 1 test import of the actual TestScript file (this is required to propagate overall top-level TestResult status of the main modularized Test)
then "TheTestScript" has, say 4 imported test modules
then 4 test modules
In each of these test modules, Limit 1 module to 1 fhir testscript test, due to the 1:1 mapping requirement of TestScript to TestReport mapping standard.
This approach was favored instead of client-side task #113 because the client feature would overwrite the "Internal\bundle_eval" test log of the PDB Validations. With this approach based on Asbestos test import extension, test logs are kept intact with the test run and it offers a convenient display.
Example Within a Test TestScript, if a test action operation is of "AggregateModule" type then it has 1 test import "TestScriptModule" then "TestScriptModule" has 1 test import of the actual TestScript file (this is required to propagate overall top-level TestResult status of the main modularized Test) then "TheTestScript" has, say 4 imported test modules then 4 test modules In each of these test modules, Limit 1 module to 1 fhir testscript test, due to the 1:1 mapping requirement of TestScript to TestReport mapping standard.