Skip to content

Commit

Permalink
Double timeouts on integration tests
Browse files Browse the repository at this point in the history
The current timeout of 1000ms gives us a lot of false negatives on different node tests on Travis. The problem might be related to running lots of tests in parallel. Since this is hard to confirm on a local machine I have no scientific grounds for setting 2000ms specifically
  • Loading branch information
Munter committed Jan 4, 2017
1 parent 0fd44d8 commit ffc978a
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions test/integration/suite.spec.js
Expand Up @@ -5,7 +5,7 @@ var run = require('./helpers').runMocha;
var args = [];

describe('suite w/no callback', function () {
this.timeout(1000);
this.timeout(2000);
it('should throw a helpful error message when a callback for suite is not supplied', function (done) {
run('suite/suite-no-callback.fixture.js', args, function (err, res) {
assert(!err);
Expand All @@ -17,7 +17,7 @@ describe('suite w/no callback', function () {
});

describe('skipped suite w/no callback', function () {
this.timeout(1000);
this.timeout(2000);
it('should not throw an error when a callback for skipped suite is not supplied', function (done) {
run('suite/suite-skipped-no-callback.fixture.js', args, function (err, res) {
assert(!err);
Expand All @@ -30,7 +30,7 @@ describe('skipped suite w/no callback', function () {
});

describe('skipped suite w/ callback', function () {
this.timeout(1000);
this.timeout(2000);
it('should not throw an error when a callback for skipped suite is supplied', function (done) {
run('suite/suite-skipped-callback.fixture.js', args, function (err, res) {
assert(!err);
Expand Down

0 comments on commit ffc978a

Please sign in to comment.