There is a TravisCI project configured to execute on every GitHub push, it can be viewed at: https://travis-ci.org/bokeh/bokeh.
TravisCI runs all the available test but also run most of the examples in the repository. If you want to skip these examples runs, you can disable them just adding [ci disable examples] to your last commit message before pushing.
Additionally, there is a diff machinery in place to let you know, quickly and broadly, how your changes impact on the examples available for testing. You will find the link to the diff machinery report in the TravisCI log, for instance, you can see report here: https://travis-ci.org/bokeh/bokeh/jobs/90594568#L1150 Finally, the diff machinery is only run on python 2, so you will find the report in the 4th job of any build (labeled as GROUP=examples_flake_docs).
You can run all available tests (python and JS unit tests, as well as example and integration tests) from the top level directory by executing:
Currently this script does not support Windows.
To run just the python unit tests, run either command:
py.test -m 'not (js or examples or integration)'
python -c 'import bokeh; bokeh.test()'
To run just the examples, run the command:
py.test -m examples
To run just the integration tests, run the command:
py.test -m integration
To run just the BokehJS unit tests, execute:
py.test -m js
Or, in the bokehjs subdirectory of the source checkout.
To learn more about marking test functions and selecting/deselecting them for a run, please consult the pytest documentation about custom markers.
To help the test script choose the appropriate test runner, there are some naming conventions that examples should adhere to. Non-IPython notebook example scripts that rely on the Bokeh server should have ‘server’ or ‘animate’ in their filenames.
To run any of the tests with coverage use the following:
To run any of the tests without standard output captured use:
See the py.test documentation at http://pytest.org/latest/ for further information on py.test and it’s options.