Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore feasibility with the Broad #12

Open
ksuderman opened this issue Aug 14, 2023 · 2 comments
Open

Explore feasibility with the Broad #12

ksuderman opened this issue Aug 14, 2023 · 2 comments
Labels
testing Unit, integration, and acceptance tests
Milestone

Comments

@ksuderman
Copy link
Owner

ksuderman commented Aug 14, 2023

To simplify acceptance testing on production instances it would be useful to have access to the Galaxy API to:

  • upload workflows and install tools with Planemo
  • upload datasets and histories
  • run workflows
  • query the instance for job statuses

Once the tests have been developed they can run at the Broad (i.e. on a local network and behind any firewalls). However, during development it would be necessary to access the Galaxy API from outside Terra.

@ksuderman ksuderman added this to the AnVIL testing milestone Aug 14, 2023
@ksuderman ksuderman moved this to Todo in AnVIL Tasks Aug 14, 2023
@ksuderman ksuderman added the testing Unit, integration, and acceptance tests label Aug 16, 2023
@ksuderman
Copy link
Owner Author

The first three items can likely be done with Playwright easily enough. We need to decide if the fourth item is important enough for the effort involved.

@ksuderman ksuderman moved this from Todo to Backlog in AnVIL Tasks Sep 6, 2023
@ksuderman ksuderman moved this from Backlog to Todo in AnVIL Tasks Sep 9, 2023
@ksuderman
Copy link
Owner Author

Running tests in headless mode presents problems with 2FA so we will need to explore solutions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Unit, integration, and acceptance tests
Projects
Status: Todo
Development

No branches or pull requests

1 participant