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

Add selenium tests #103

Merged
merged 43 commits into from
Oct 1, 2018
Merged

Add selenium tests #103

merged 43 commits into from
Oct 1, 2018

Conversation

cowlicks
Copy link
Owner

Closes #7

Currently this is just a dump of code that:

  • Uses selenium to run chrome with Privacy Possum installed
  • Start a simple express app
  • visit the express app with the chrome instance

Now that we have something to build off, we need to:

  • Make an express app to serve some in-browser unit tests
  • finish the etag test, and add more complex tests
  • Move the tests out a directory that is packaged with the extension
  • update the .travis.yml to run these headlessley
  • run the tests in firefox

I'll probably merge this as soon as it can run on travis-ci to be useful. The rest of the unfinished stuff can be made into separate issues.

@cowlicks
Add selenium-webdriver as a dev dependency
e484baa
@cowlicks
Add express and vhost as dev dependencies
eb3ac70
@cowlicks
Initial commit of selenium + express w/ Chrome
fb089d3
@cowlicks
Add selenium-webdriver as a dev dependency
660a204
@cowlicks
Add selenium/cookies.js tests
53949bc
@cowlicks
refactoring selenium management
530c1a5
@cowlicks
Add note on running selenium tests.
f27ecd6
@cowlicks
fix name of selenium/cookies.js
d7426f7
@cowlicks
Add cookie parser as dev dependency
9200ec5
@cowlicks
Expand and refactor cookie app
b0f78de
@cowlicks
Add actual mocha tests.
f27dc92
@cowlicks
Update npm run selenium.
b513375 
This reflects selenium test name change. And uses mocha to run the
tests.
@cowlicks
Test with a matrix in .travis.yml
a0dbb39
@cowlicks
git mv ./src/js/selenium .
e1f9910
@cowlicks
give selenium tests their own package.json
6bdd453
@cowlicks
Make selenium script point to correct ext src
902a2b1
@cowlicks
Add run_in_dir func and selenium_dir to test tools
28dd4d3
@cowlicks
Use run_in_dir in unittest script
0078af5
@cowlicks
Add scripts/selenium_test.sh
1d12b07
@cowlicks
Add selenium_test target to Makefile
f6ed8b6
@cowlicks
make npm_install.sh take a directory argument
aa1b92c
@cowlicks
Add npm_install_selenium, use new npm_install.sh
494e653
@cowlicks
call script and install from inside travis matrix
94e015b
@cowlicks
Install xvfb as dev-dep for selenium
cef34d3
@cowlicks
WIP use xvfb to run selenium code
9ca59e9
@cowlicks
Add selenium to .travis.yml
3725395
@cowlicks
Add chromedriver to selenium dev-deps
8301926
@cowlicks
Install chrome in travis.yml
b3620dd
@cowlicks
Try starting xvfb in .travis.yml
f0bcbf2
@cowlicks
Pass the --no-sandbox flag to chrome
dafc3e4 
This should fix the bug referred to here:
https://docs.travis-ci.com/user/chrome#sandboxing
@cowlicks cowlicks merged commit 09981f5 into master Oct 1, 2018
@cowlicks cowlicks mentioned this pull request Jan 31, 2019
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@cowlicks