John Chilton

I don't think you should have to send special flags to filter the API tests down for a particular version of Galaxy but I do think in CI we expect...

- Add integration test for invalid admin key. - Add tool test to ensure error message is valid JSON. - Swap order of require_admin and expose_api - expose_api sets environment...

Allow recovering a normalized version of workflow request state from API

1

Implements https://github.com/galaxyproject/galaxy/issues/18981 Also made small improvements to the schema for running workflows. Filled in a bunch of stub descriptions, dropped ``step_parameters`` which never existed in the API. There is a...

``visit_input_values`` was not updated to reflect nested state vs. flat state.

From @mvdbeek > That's workflow_request_input_step_parameter, workflow_request_to_input_collection_dataset, workflow_request_to_input_dataset, workflow_request_step_states workflow_request_input_parameters etc ? I wonder if we should try systematically round-tripping these in our workflow tests If that works maybe we're ready...

Synchronize with Galaxy Post 24.2 Publication

1

- [ ] Rework test verification to use new library functionality (``verify_file_path_against_dict``) meant for reuse across Galaxy and Planemo - see comments in ``lib/galaxy/tool_util/verify/__init__.py``. - [ ] Migrate the CWL-style...