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

initial work to support server selenium tests #8139

merged 1 commit into from Aug 7, 2018


None yet
1 participant
Copy link

bryevdv commented Aug 7, 2018

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_page etc jsut be made to support server apps out of the box? Or should bokeh_server_page remain distinct?

Also note the workarounds for #7970 that should be removed when that issue is resolved.

cc @philippjfr

@bryevdv bryevdv merged commit bf7a804 into master Aug 7, 2018

2 checks passed

Better Code Hub ✅ Better Code Hub approves this code
continuous-integration/travis-ci/pr The Travis CI build passed

@bryevdv bryevdv added this to the 1.0 milestone Aug 7, 2018

@mattpap mattpap deleted the bryanv/selenium_server_test branch Aug 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment