Repository navigation
Ability to run integration tests locally #26
Description
I have problems getting saucelabs to run our test suite (it was added by @jharding in twitter/typeahead.js project back in 2014, but broke at some point in time).
Now, some of the problem is covered by #20 and #21. But actually being able to run the integration tests locally would help so that we can see and debug errors with the actual suite.
The file integration/test.js is the actual test, but also sets up Saucelabs-specific variables.
The task will be to make a split, so that we can run a simple task locally (which probably could use Phantom).
For example:
npm run test:integration
Activity
[-]Abilitty to run integration tests locally[/-][+]Ability to run integration tests locally[/+]sheeley commentedon Nov 21, 2015
@jesperronn have you done any work on this? Want me to take a look?
jesperronn commentedon Nov 21, 2015
@sheeley to be honest, no. I haven't looked into it since. Running the tests will be a big plus for the project, so I encourage you (and anybody else) to look into it. And make a fix.
colinrotherham commentedon Dec 13, 2016
@jesperronn @sheeley I've updated dependencies and got the tests running again here (couple of Promise-based tests needed updating, mainly PhantomJS etc).
It's on this pull request: #104
(via this commit: 9c6e693)