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.

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

Need CI-testing setup #1

Closed
Zodiase opened this issue May 3, 2016 · 11 comments
Closed

Need CI-testing setup #1

Zodiase opened this issue May 3, 2016 · 11 comments
Assignees

Comments

@Zodiase
Copy link
Owner

Zodiase commented May 3, 2016

No description provided.

@Zodiase Zodiase changed the title Need CI-testing setupNeed CI-testing setup Need CI-testing setup May 3, 2016
@Zodiase
Copy link
Owner Author

Zodiase commented May 3, 2016

Reference: https://travis-ci.org/

@xhuang26
Copy link
Collaborator

xhuang26 commented May 18, 2016

currently considered automated testing tools:
phantomJS: a full WebKit; support many browser standards; headless on linux; but need more configurations
phantomJS + Selenium: cover more powerful testing cases if needed in the future
CasperJS: build on top of phantomJS, more light-weighted compared to phantomJS, high-level functions and methods for doing common tasks
ZombieJS: relies on emulator of DOM API, faster, light-weighted, limited scope, have trouble testing with OAUTH (might not be important for this map-visualizer though)
nightwatch.js

@xhuang26
Copy link
Collaborator

xhuang26 commented May 18, 2016

travis CI for headless browser testing: https://docs.travis-ci.com/user/gui-and-headless-browsers/
connecting travis CI with sauselab for remote webdriver: http://samsaccone.com/posts/testing-with-travis-and-sauce-labs.html

@xhuang26
Copy link
Collaborator

instead of using sauselab, just include "java -jar selenium-server-standalone-2.53.0.jar &" in tranvis.yml in order to run webdriver on tranvisCI ---works fine now

@xhuang26
Copy link
Collaborator

xhuang26 commented May 19, 2016

webdriverJS is deprecated, use webdriverIO instead:
webdriverIO github: https://github.com/webdriverio/webdriverio#list-of-current-helper-methods
webdriverIO syntax: http://webdriver.io/guide/usage/selectors.html
syntax comparison between webdriverIO, selenium-webdriverjs and WD: webdriverio/webdriverio#138

@xhuang26
Copy link
Collaborator

xhuang26 commented May 23, 2016

es6 environment with phantomjs: webdriverio/webdriverio#1323
currently works fine for webdriverio + firefox.
Phantomjs cannot fully support es6 without babel or karma
Trying to figure out how to make a way around it

@xhuang26
Copy link
Collaborator

good example of how to add custom command in webdriverio:
webdriverio/webdriverio#429

@Zodiase
Copy link
Owner Author

Zodiase commented May 25, 2016

I've added eslint and babel-cli and corresponding npm commands in this project for linting and transpiling es6 code to es5. @xhuang26 You might want to pull the changes and update your test setup. For example, use the transpiled code in lib folder (after running npm run build) for testing.

@Zodiase
Copy link
Owner Author

Zodiase commented May 25, 2016

With the linter in place, you may now run npm run lint to see issues in src/*.js related to coding standards. You might also want to add another command, npm run lint-test for example, for linting your test files.

@xhuang26
Copy link
Collaborator

babel-polyfil: Symbol/Map in es6 can be understood
using babel-polyfill and phantomjs works fine now

Zodiase added a commit that referenced this issue Jun 1, 2016
@Zodiase Zodiase closed this as completed Jun 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants