You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After talking with @mccalluc I'm going to make a hello-world docker image that simply displays all data (file urls, parameters, etc.) that Refinery sends over and write non-selenium tests against that.
This image would also be really helpful to prospective VisTool developers who want to see what info they can get out of the system.
* Add VisualizationToolProxy so that we can check user perms. & provide persistant VisTool urls
* Add `user_has_access_to_tool()`
* Fix reference
* Add test coverage
* Fix typo
* Rename VizualizationProxy to AutoRelaunchProxy
* Simplify logic
* Less wordy error messages
* Fix test
* Just assert that we can launch Igv;
Towards #2238 and refinery-platform/visualization-tools#22
There already exist tests in https://github.com/refinery-platform/docker_igv_js & https://github.com/scottx611x/refinery-higlass-docker That assert that mock Refinery data can be ingested/handled. Its probably overkill/redundant to have these same tests in Refinery.
After talking with @mccalluc I'm going to make a
hello-world
docker image that simply displays all data (file urls, parameters, etc.) that Refinery sends over and write non-selenium tests against that.This image would also be really helpful to prospective VisTool developers who want to see what info they can get out of the system.
VisualizationTool
Annotation to https://github.com/refinery-platform/visualization-toolsThe text was updated successfully, but these errors were encountered: