Calling a scriptlet within a scriptlet in same suite.

[olw-medcom]

Hey there!

I have a shared suite called 'ekg-shared-suite' containing scriptlets.

I have a scriptlet called EKG-FHIR-Validation.xml inside the shared suite and I aim to have another scriptlet in the same suite called "Case-1" call the other scriptlet like this:

<?xml version="1.0" encoding="UTF-8"?>
<scriptlet id="Case-1" xmlns="http://www.gitb.com/tdl/v1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
           xsi:schemaLocation="http://www.gitb.com/tdl/v1/ ../../../../../testbedSchemas/gitb_tdl.xsd">
    <params>
        <var name="input" type="string" />
    </params>
    <steps>
        <!-- <call path="Scriptlets/EKG-FHIR-Validation.xml"> I've tried with and without the from -->

        <call path="Scriptlets/EKG-FHIR-Validation.xml" from="ekg-shared-suite">
            <input name="input">$input</input>
        </call>

        [...]

    </steps>
</scriptlet>

This is my directory structure:
.
├── Scriptlets
│   ├── EKG-FHIR-Validation.xml
│   ├── FHIRPath-S1-1.xml
│   └── FHIRPath-S1-6
│   ├── Case1.xml
└── shared-ekg-suite.xml

But gitb-srv is unable to lookup the ressource:
24/03/2026 10:23:46 ERROR c.g.e.r.RemoteTestCaseRepository - [] Failed to look up resource path [Scriptlets/EKG-FHIR-Validation.xml] for test case [334] from test suite [ekg-shared-suite]

Can you spot what I am doing wrong?

[costas80]

It's not obvious what the issue is. I tested on my end a similar setup (test case calling scriptlet from other test suite, and that scriptlet calling another one from the same test suite) and it works fine. Also there is no need to add the from if you are referring to a scriptlet in the same test suite.

Some things to check would be:

• The from you specify must match the id of the other test suite.
• Make sure that the path value is correct. Have you for example added in the test suite archive a root folder that does not figure in the path?
• When you say that you are referring to a "shared" test suite, how have you linked this to the specification in question? You should either add it to the specification (not as a shared test suite), or add it to the domain as a shared test suite and then link it to your specification in question.
• Are you getting any warnings during test suite validation?

If I had to guess what the issue is, I'd say that you defined a shared test suite but have not linked it to your spec(s). A shared test suite that is not linked to a spec will not be available to lookup resources from. Could this be it?

[olw-medcom]

Hm fair enough, I will research further, I just had to ensure it wasn't a bug. Closing this 😊

[costas80]

Hi @olw-medcom - we had another posting a similar issue to what you reported in the latest 1.29.0 release. It's no doubt linked so I'll re-open this until we publish a patch.

[costas80]

Update published (both in the nightly as well as patch 1.29.1). Can you check @olw-medcom whether this resolves your initial issue (the bug that was fixed seems exactly like what you were facing).