build: configure BrowserStack

[dsebastien]

Goal: automate some UI tests on different devices.

We could make use of their open source offering:
https://www.browserstack.com/contact?ref=open_source&product=combined#open-source

• define config
• evaluate how to automate
• automate
• document
• integrate with protractor: https://www.browserstack.com/automate/protractor and example: https://github.com/browserstack/protractor-browserstack
• update CONTRIBUTING.md -> how to configure credentials...
• integrate with Travis (! browserstack credentials as env variables)
• once built once using protractor, make sure the project appears on the BrowserStack page
• add badge: https://www.browserstack.com/automate/status-badges

[dsebastien]

Mail sent

[dsebastien]

Sébastien & Alexis have access to the BrowserStack config. Can be extended to others later on

[dsebastien]

Added environment variables to travis config:

• BROWSERSTACK_ACCESS_KEY
• BROWSERSTACK_USERNAME

[dsebastien]

We've received our free year

[dsebastien]

Each dev on the project that wants Travis + BrowserStack support should add the variables above to the travis config for their fork

[christophercr]

@cnomes I just came across this article Using Jest matchers in Cypress although it is about Jest, it also says:

This technique could also be applied to using Jasmine’s expect as well.

So maybe you can do the same for Jasmine, I think you would need to use jasmine-core for this.

[christophercr]

The documentation in the Contributing guide will be tackled in #946