Files
galaxy/test/functional/tools/section.xml
T
mvdbeek 5d083a657a Always attempt to build tool request for new API endpoint
Previously, the structured request needed by POST /api/jobs was only
built for tools with profile >= 24.2. For older tools case_state() was
never called, leaving request=None and making the new endpoint unusable.

The profile check was about validation strictness, not a fundamental
limitation: case_state(validate=False) can build a valid request for
any tool. Now we always attempt it, using validate=True for modern tools
and validate=False for older ones. Failures populate
request_unavailable_reason so "if_needed" can fall back gracefully.
2026-06-15 08:56:03 +02:00

48 lines
1.5 KiB
XML

<tool id="section" name="section" version="1.0.0">
<command><![CDATA[
echo $int.inttest > '$out_file1' &&
echo $float.floattest >> '$out_file1'
]]></command>
<inputs>
<section name="int" title="Integer Section" expanded="true">
<param name="inttest" value="1" type="integer" />
</section>
<section name="float" title="Float Section" expanded="false">
<param name="floattest" value="1.0" type="float" />
</section>
</inputs>
<outputs>
<data name="out_file1" format="txt" />
</outputs>
<tests>
<test>
<section name="int">
<param name="inttest" value="12456" />
</section>
<section name="float">
<param name="floattest" value="6.789" />
</section>
<output name="out_file1">
<assert_contents>
<has_line line="12456" />
<has_line line="6.789" />
</assert_contents>
</output>
</test>
<test>
<section name="int">
<param name="inttest" value="12456" />
</section>
<section name="float">
<param name="floattest" value="6.789" />
</section>
<output name="out_file1">
<assert_contents>
<has_line line="12456" />
<has_line line="6.789" />
</assert_contents>
</output>
</test>
</tests>
</tool>