initial work to support server selenium tests#8139
Merged
Conversation
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an initial stab at a workflow for adding selenium tests for bokeh server apps. Some things will probably change, but this is enough to support other currently ongoing work.
Some questions (to be addressed in later PRs):
should server tests e.g. for widgets, be located with all the other widget tests? Or should the be segregated? If so, in what sort of layout
Should
single_plot_pageetc jsut be made to support server apps out of the box? Or shouldbokeh_server_pageremain distinct?Also note the workarounds for #7970 that should be removed when that issue is resolved.
cc @philippjfr