Warning
This document is for an old release of Galaxy. You can alternatively view this page in the latest release if it exists or view the top of the latest release's documentation.
galaxy_test.base package¶
Submodules¶
galaxy_test.base.api module¶
-
class
galaxy_test.base.api.
ApiTestInteractor
(test_case, api_key=None)[source]¶ Bases:
galaxy_test.base.interactor.TestCaseGalaxyInteractor
Specialized variant of the API interactor (originally developed for tool functional tests) for testing the API generally.
galaxy_test.base.api_asserts module¶
Utility methods for making assertions about Galaxy API responses, etc…
-
galaxy_test.base.api_asserts.
assert_status_code_is
(response: requests.models.Response, expected_status_code: int)[source]¶ Assert that the supplied response has the expect status code.
-
galaxy_test.base.api_asserts.
assert_status_code_is_ok
(response: requests.models.Response)[source]¶ Assert that the supplied response is okay.
The easier alternative
response.raise_for_status()
might be perferable generally.See also
-
galaxy_test.base.api_asserts.
assert_has_keys
(response: dict, *keys: str)[source]¶ Assert that the supplied response (dict) has the supplied keys.
-
galaxy_test.base.api_asserts.
assert_not_has_keys
(response: dict, *keys: str)[source]¶ Assert that the supplied response (dict) does not have the supplied keys.
-
galaxy_test.base.api_asserts.
assert_error_code_is
(response: Union[requests.models.Response, dict], error_code: int)[source]¶ Assert that the supplied response has the supplied Galaxy error code.
Galaxy error codes can be imported from
galaxy.exceptions.error_codes
to test against.from galaxy.exceptions import error_codes assert_error_code_is(response, error_codes.USER_REQUEST_MISSING_PARAMETER)
-
galaxy_test.base.api_asserts.
assert_object_id_error
(response: requests.models.Response)[source]¶
-
galaxy_test.base.api_asserts.
assert_error_message_contains
(response: Union[requests.models.Response, dict], expected_contains: str)[source]¶
galaxy_test.base.api_util module¶
galaxy_test.base.constants module¶
Just constants useful for testing across test types.
galaxy_test.base.env module¶
Base utilities for working Galaxy test environments.
galaxy_test.base.instrument module¶
Utilities to help instrument tool tests.
Including structured data nose plugin that allows storing arbitrary structured data on a per test case basis - used by tool test to store inputs, output problems, job tests, etc… but could easily by used by other test types in a different way.
-
class
galaxy_test.base.instrument.
StructuredTestDataPlugin
[source]¶ Bases:
nose.plugins.base.Plugin
-
name
= 'structureddata'¶
-
options
(parser, env)[source]¶ Register commandline options.
Implement this method for normal options behavior with protection from OptionConflictErrors. If you override this method and want the default –with-$name option to be registered, be sure to call super().
-
configure
(options, conf)[source]¶ Configure the plugin and system, based on selected options.
The base plugin class sets the plugin to enabled if the enable option for the plugin (self.enableOpt) is true.
-
addError
(test, *args, **kwds)¶
-
addFailure
(test, *args, **kwds)¶
-
addSuccess
(test, *args, **kwds)¶
-
galaxy_test.base.interactor module¶
-
class
galaxy_test.base.interactor.
TestCaseGalaxyInteractor
(functional_test_case, test_user=None, api_key=None)[source]¶ Bases:
galaxy.tool_util.verify.interactor.GalaxyInteractorApi
galaxy_test.base.nose_util module¶
Utilities for dealing with nose.
There was some duplication between Galaxy, Tool Shed, and Install/Test, trying to reduce that here.
galaxy_test.base.populators module¶
Abstractions used by the Galaxy testing frameworks for interacting with the Galaxy API.
These abstractions are geared toward testing use cases and populating fixtures. For a more general framework for working with the Galaxy API checkout bioblend.
The populators are broken into different categories of data one might want to populate
and work with (datasets, histories, libraries, and workflows). Within each populator
type abstract classes describe high-level functionality that depend on abstract
HTTP verbs executions (e.g. methods for executing GET, POST, DELETE). The abstract
classes are galaxy_test.base.populators.BaseDatasetPopulator
,
galaxy_test.base.populators.BaseWorkflowPopulator
, and
galaxy_test.base.populators.BaseDatasetCollectionPopulator
.
There are a few different concrete ways to supply these low-level verb executions.
For instance galaxy_test.base.populators.DatasetPopulator
implements the abstract
galaxy_test.base.populators.BaseDatasetPopulator
by leveraging a galaxy interactor
galaxy.tool_util.interactor.GalaxyInteractorApi
. It is non-intuitive
that the Galaxy testing framework uses the tool testing code inside Galaxy’s code
base for a lot of heavy lifting. This is due to the API testing framework organically
growing from the tool testing framework that predated it and then the tool testing
framework being extracted for re-use in Planemo, etc..
These other two concrete implementation of the populators are much more
direct and intuitive. galaxy_test.base.populators.GiDatasetPopulator
, et. al.
are populators built based on Bioblend gi
objects to build URLs and describe
API keys. galaxy_test.selenium.framework.SeleniumSessionDatasetPopulator
,
et al. are populators built based on Selenium sessions to leverage Galaxy cookies
for auth for instance.
All three of these implementations are now effectively light wrappers around requests. Not leveraging requests directly is a bit ugly and this ugliness again stems from these organically growing from a framework that originally didn’t use requests at all.
API tests and Selenium tests routinely use requests directly and that is totally fine, requests should just be filtered through the verb abstractions if that functionality is then added to populators to be shared across tests or across testing frameworks.
-
galaxy_test.base.populators.
skip_without_tool
(tool_id)[source]¶ Decorate an API test method as requiring a specific tool.
Have test framework skip the test case if the tool is unavailable.
-
galaxy_test.base.populators.
skip_without_datatype
(extension)[source]¶ Decorate an API test method as requiring a specific datatype.
Have test framework skip the test case if the datatype is unavailable.
-
galaxy_test.base.populators.
skip_if_toolshed_down
(method)¶
-
galaxy_test.base.populators.
skip_if_github_down
(method)¶
-
galaxy_test.base.populators.
uses_test_history
(**test_history_kwd)[source]¶ Can override require_new and cancel_executions using kwds to decorator.
-
class
galaxy_test.base.populators.
BaseDatasetPopulator
[source]¶ Bases:
galaxy_test.base.populators.BasePopulator
Abstract description of API operations optimized for testing Galaxy - implementations must implement _get, _post and _delete.
-
new_dataset
(history_id: str, content=None, wait: bool = False, **kwds) → str[source]¶ Create a new history dataset instance (HDA) and return its ID.
- Returns
the HDA id of the new object
-
new_dataset_request
(history_id: str, content=None, wait: bool = False, **kwds) → requests.models.Response[source]¶ Lower-level dataset creation that returns the upload tool response object.
-
fetch
(payload: dict, assert_ok: bool = True, timeout: Union[int, float] = 60, wait: Optional[bool] = None)[source]¶
-
wait_for_tool_run
(history_id: str, run_response: requests.models.Response, timeout: Union[int, float] = 60, assert_ok: bool = True)[source]¶
-
check_run
(run_response: requests.models.Response) → dict[source]¶
-
wait_for_history
(history_id: str, assert_ok: bool = False, timeout: Union[int, float] = 60) → str[source]¶
-
wait_for_history_jobs
(history_id: str, assert_ok: bool = False, timeout: Union[int, float] = 60)[source]¶
-
get_job_details
(job_id: str, full: bool = False) → requests.models.Response[source]¶
-
cancel_job
(job_id: str) → requests.models.Response[source]¶
-
delete_dataset
(history_id: str, content_id: str) → requests.models.Response[source]¶
-
create_tool_from_path
(tool_path: str) → requests.models.Response[source]¶
-
create_tool
(representation, tool_directory: Optional[str] = None) → requests.models.Response[source]¶
-
tools_post
(payload: dict, url='tools') → requests.models.Response[source]¶
-
get_history_dataset_content
(history_id: str, wait=True, filename=None, type='text', raw=False, **kwds)[source]¶
-
get_history_dataset_details_raw
(history_id: str, dataset_id: str) → requests.models.Response[source]¶
-
run_collection_creates_list
(history_id: str, hdca_id: str) → requests.models.Response[source]¶
-
-
class
galaxy_test.base.populators.
GalaxyInteractorHttpMixin
[source]¶ Bases:
object
-
galaxy_interactor
: galaxy_test.base.api.ApiTestInteractor¶
-
-
class
galaxy_test.base.populators.
DatasetPopulator
(galaxy_interactor)[source]¶ Bases:
galaxy_test.base.populators.GalaxyInteractorHttpMixin
,galaxy_test.base.populators.BaseDatasetPopulator
-
galaxy_interactor
: galaxy_test.base.api.ApiTestInteractor¶
-
-
class
galaxy_test.base.populators.
BaseWorkflowPopulator
[source]¶ Bases:
galaxy_test.base.populators.BasePopulator
-
load_workflow
(name: str, content: str = '{\n "a_galaxy_workflow": "true", \n "annotation": "simple workflow",\n "format-version": "0.1", \n "name": "TestWorkflow1", \n "steps": {\n "0": {\n "annotation": "input1 description", \n "id": 0, \n "input_connections": {}, \n "inputs": [\n {\n "description": "input1 description", \n "name": "WorkflowInput1"\n }\n ], \n "name": "Input dataset", \n "outputs": [], \n "position": {\n "left": 199.55555772781372, \n "top": 200.66666460037231\n }, \n "tool_errors": null, \n "tool_id": null, \n "tool_state": "{\\"name\\": \\"WorkflowInput1\\"}", \n "tool_version": null, \n "type": "data_input", \n "user_outputs": []\n }, \n "1": {\n "annotation": "", \n "id": 1, \n "input_connections": {}, \n "inputs": [\n {\n "description": "", \n "name": "WorkflowInput2"\n }\n ], \n "name": "Input dataset", \n "outputs": [], \n "position": {\n "left": 206.22221422195435, \n "top": 327.33335161209106\n }, \n "tool_errors": null, \n "tool_id": null, \n "tool_state": "{\\"name\\": \\"WorkflowInput2\\"}", \n "tool_version": null, \n "type": "data_input", \n "user_outputs": []\n }, \n "2": {\n "annotation": "", \n "id": 2, \n "input_connections": {\n "input1": {\n "id": 0, \n "output_name": "output"\n }, \n "queries_0|input2": {\n "id": 1, \n "output_name": "output"\n }\n }, \n "inputs": [], \n "name": "Concatenate datasets", \n "outputs": [\n {\n "name": "out_file1", \n "type": "input"\n }\n ], \n "position": {\n "left": 419.33335876464844, \n "top": 200.44446563720703\n }, \n "post_job_actions": {}, \n "tool_errors": null, \n "tool_id": "cat1", \n "tool_state": "{\\"__page__\\": 0, \\"__rerun_remap_job_id__\\": null, \\"input1\\": \\"null\\", \\"queries\\": \\"[{\\\\\\"input2\\\\\\": null, \\\\\\"__index__\\\\\\": 0}]\\"}", \n "tool_version": "1.0.0", \n "type": "tool", \n "user_outputs": []\n }\n }\n}\n', add_pja=False) → dict[source]¶
-
create_workflow_response
(workflow: dict, **create_kwds) → requests.models.Response[source]¶
-
wait_for_invocation
(workflow_id: str, invocation_id: str, timeout: Union[int, float] = 60, assert_ok: bool = True)[source]¶
-
wait_for_history_workflows
(history_id, assert_ok=True, timeout=60, expected_invocation_count=None)[source]¶
-
wait_for_workflow
(workflow_id, invocation_id, history_id, assert_ok=True, timeout=60)[source]¶ Wait for a workflow invocation to completely schedule and then history to be complete.
-
validate_biocompute_object
(bco, expected_schema_version='https://w3id.org/ieee/ieee-2791-schema/2791object.json')[source]¶
-
invoke_workflow_raw
(workflow_id, request: dict) → requests.models.Response[source]¶
-
invoke_workflow
(history_id: str, workflow_id: str, inputs: Optional[dict] = None, request: Optional[dict] = None, assert_ok: bool = True)[source]¶
-
download_workflow
(workflow_id: str, style: Optional[str] = None, history_id: Optional[str] = None) → dict[source]¶
-
update_workflow
(workflow_id: str, workflow_object: dict) → requests.models.Response[source]¶
-
refactor_workflow
(workflow_id: str, actions: list, dry_run: Optional[bool] = None, style: Optional[str] = None) → requests.models.Response[source]¶
-
run_workflow
(has_workflow, test_data=None, history_id=None, wait=True, source_type=None, jobs_descriptions=None, expected_response=200, assert_ok=True, client_convert=None, round_trip_format_conversion=False, raw_yaml=False)[source]¶ High-level wrapper around workflow API, etc. to invoke format 2 workflows.
-
-
class
galaxy_test.base.populators.
RunJobsSummary
(history_id, workflow_id, invocation_id, inputs, jobs, invocation, workflow_request)¶ Bases:
tuple
-
property
history_id
¶ Alias for field number 0
-
property
inputs
¶ Alias for field number 3
-
property
invocation
¶ Alias for field number 5
-
property
invocation_id
¶ Alias for field number 2
-
property
jobs
¶ Alias for field number 4
-
property
workflow_id
¶ Alias for field number 1
-
property
workflow_request
¶ Alias for field number 6
-
property
-
class
galaxy_test.base.populators.
WorkflowPopulator
(galaxy_interactor)[source]¶ Bases:
galaxy_test.base.populators.GalaxyInteractorHttpMixin
,galaxy_test.base.populators.BaseWorkflowPopulator
,gxformat2.interface.ImporterGalaxyInterface
-
galaxy_interactor
: galaxy_test.base.api.ApiTestInteractor¶
-
import_workflow
(workflow, **kwds)[source]¶ Import a workflow via POST /api/workflows or comparable interface into Galaxy.
-
-
class
galaxy_test.base.populators.
BaseDatasetCollectionPopulator
[source]¶ Bases:
object
-
class
galaxy_test.base.populators.
DatasetCollectionPopulator
(galaxy_interactor: galaxy_test.base.api.ApiTestInteractor)[source]¶ Bases:
galaxy_test.base.populators.BaseDatasetCollectionPopulator
-
__init__
(galaxy_interactor: galaxy_test.base.api.ApiTestInteractor)[source]¶ Initialize self. See help(type(self)) for accurate signature.
-
-
galaxy_test.base.populators.
load_data_dict
(history_id, test_data, dataset_populator, dataset_collection_populator)[source]¶ Load a dictionary as inputs to a workflow (test data focused).
-
galaxy_test.base.populators.
stage_inputs
(galaxy_interactor, history_id, job, use_path_paste=True, use_fetch_api=True, to_posix_lines=True)[source]¶ Alternative to load_data_dict that uses production-style workflow inputs.
-
galaxy_test.base.populators.
stage_rules_example
(galaxy_interactor, history_id, example)[source]¶ Wrapper around stage_inputs for staging collections defined by rules spec DSL.
-
galaxy_test.base.populators.
wait_on_state
(state_func: Callable, desc='state', skip_states=None, ok_states=None, assert_ok=False, timeout=60) → str[source]¶
-
class
galaxy_test.base.populators.
GiHttpMixin
[source]¶ Bases:
object
Mixin for adapting Galaxy testing populators helpers to bioblend.
-
class
galaxy_test.base.populators.
GiDatasetPopulator
(gi)[source]¶ Bases:
galaxy_test.base.populators.BaseDatasetPopulator
,galaxy_test.base.populators.GiHttpMixin
Implementation of BaseDatasetPopulator backed by bioblend.
-
class
galaxy_test.base.populators.
GiDatasetCollectionPopulator
(gi)[source]¶ Bases:
galaxy_test.base.populators.BaseDatasetCollectionPopulator
,galaxy_test.base.populators.GiHttpMixin
Implementation of BaseDatasetCollectionPopulator backed by bioblend.
-
class
galaxy_test.base.populators.
GiWorkflowPopulator
(gi)[source]¶ Bases:
galaxy_test.base.populators.BaseWorkflowPopulator
,galaxy_test.base.populators.GiHttpMixin
Implementation of BaseWorkflowPopulator backed by bioblend.
galaxy_test.base.rules_test_data module¶
galaxy_test.base.ssh_util module¶
galaxy_test.base.testcase module¶
-
class
galaxy_test.base.testcase.
FunctionalTestCase
(methodName='runTest')[source]¶ Bases:
unittest.case.TestCase
Base class for tests targetting actual Galaxy servers.
Subclass should override galaxy_driver_class if a Galaxy server needs to be launched to run the test, this base class assumes a server is already running.
-
test_data_resolver
: galaxy.tool_util.verify.test_data.TestDataResolver¶
-