corejavascript/typeahead.js

Ability to run integration tests locally

Open

#26 opened on Oct 25, 2015

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (956 stars) (232 forks)batch import
help wanted

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

Contributor guide

Tech stack
javascriptnodejs
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic JavaScriptNode.js and npmFamiliarity with test runners
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Examine the file `integration/test.js` to understand the current structure. Identify the Saucelabs specific code and extract it, then create a separate local test script using a headless browser like PhantomJS. Update `package.json` to add a new script `test:integration` for local runs. Refer to the comments in the issue for additional context.