Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Testing with Selenium & Sauce labs #3321

Merged
merged 24 commits into from
Feb 13, 2018
Merged

Testing with Selenium & Sauce labs #3321

merged 24 commits into from
Feb 13, 2018

Commits on Feb 8, 2018

  1. Initial selenium test

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    aa9272a View commit details
    Browse the repository at this point in the history

  2. Try configuring Travis to run selenium tests on Sauce

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    a8c4258 View commit details
    Browse the repository at this point in the history

  3. Encryption key needs to be for my account, not jupyter

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    9759074 View commit details
    Browse the repository at this point in the history

  4. Install selenium on Travis

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    c417727 View commit details
    Browse the repository at this point in the history

  5. Get more data from server info file

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    162e7aa View commit details
    Browse the repository at this point in the history

  6. Set cwd when launching notebook server 

    Will this help on Travis?
    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    f578d4e View commit details
    Browse the repository at this point in the history

  7. Use JUPYTER_TEST_BROWSER=chrome to test with Chrome

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    7bfb7a8 View commit details
    Browse the repository at this point in the history

  8. Debugging test

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    b2b449f View commit details
    Browse the repository at this point in the history

  9. Separate fixtures into conftest.py

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    0c65390 View commit details
    Browse the repository at this point in the history

  10. Try with --Cls.a=b option syntax

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    739b14a View commit details
    Browse the repository at this point in the history

  11. Try using sauce labs directly, not through Travis proxy

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    dca1255 View commit details
    Browse the repository at this point in the history

  12. Back to using proxy, with http instead of https 

    Idea from https://stackoverflow.com/questions/48236104/ssl-errors-using-
sauce-labs-in-travis-ci-with-selenium-webriver-tests-django-pr
    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    5391f32 View commit details
    Browse the repository at this point in the history

  13. Specify browserName in desired_capabilities for Sauce

    @takluyver
    takluyver committed Feb 8, 2018
    Configuration menu
    Copy the full SHA
    93d9fa6 View commit details
    Browse the repository at this point in the history

Commits on Feb 9, 2018

  1. Try connecting to Sauce for only some jobs in matrix

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    1eee66e View commit details
    Browse the repository at this point in the history

  2. Exclude selenium tests from regular test run

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    daeea41 View commit details
    Browse the repository at this point in the history

  3. Remove redundant JS test for dashboard navigation (converted to Selen… 

    …ium)
    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    2e8bf3b View commit details
    Browse the repository at this point in the history

  4. Re-enable other tests

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    a1189fc View commit details
    Browse the repository at this point in the history

  5. Exclude selenium tests on Appveyor

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    c0361cb View commit details
    Browse the repository at this point in the history

  6. Later browser versions are available on Windows

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    cdee97a View commit details
    Browse the repository at this point in the history

  7. Try running tests with Firefox 57 instead of 58

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    abc38a7 View commit details
    Browse the repository at this point in the history

  8. Try running with local Firefox on Travis

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    b1f9cb2 View commit details
    Browse the repository at this point in the history

  9. Install geckodriver for Selenium tests

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    3be1943 View commit details
    Browse the repository at this point in the history

  10. Untar the right version of geckodriver

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    58e7e48 View commit details
    Browse the repository at this point in the history

  11. Try stepping back one version of Firefox again

    @takluyver
    takluyver committed Feb 9, 2018
    Configuration menu
    Copy the full SHA
    9390b14 View commit details
    Browse the repository at this point in the history