Replaces grid-based history name verification with a more robust check using the history card list.
Ensures tests are aligned with current UI behavior.
The tool panel view renders the default view before switching to the EDAM I think, so retrying the assertion instead of just retrying any DOM click failures should allow that to stabilize. The UI flicker seems to be a regression though - but this test didn't prevent that so now it has to test something else.
Also I think the EDAM stuff is just on by default now so this doesn't need to be an integration test - as such moved it to the vanilla Selenium tests.
- Add some basic typing to them.
- Include more information in assertion errors thrown when they target an incorrectly configured server.
- Allow for explicit anonymous interactor creation so we can cleanly apply these decorators to Selenium tests (Selenium test interactors use API keys that can be created from the UI - so they don't have complete user information available upfront).
- Add decorator skip_without_visualization_plugin.
- Add some decorators to the visualization tests and implement a second test.
- Use managed_history decorator to ensure existing test has an hid of 1 as assumed.
add forgotten files, format
add more methods for selenium navigation
add needed selectors
jobs grid test: proper admin handling and wait for the workflow invocation
blackened
fix copypasta name
Co-authored-by: John Chilton <jmchilton@gmail.com>
with manual fixes to 3 files to make them compatible with black 22.12.0 .
We need to keep black pinned at `<23` until we vendorise `packaging`, since
the new version of black depends on `packaging >=22.0` which is the version
where `LegacyVersion` (which we use for tool lineages) was removed.
This selenium test is for testing the previous history export UI that is based on jobs and not tasks.
Since Celery is enabled by default in the test instance it is more consistent to convert it into an integration selenium test to modify the config and disable Celery.
davelopez