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

Refactor/reorg test driver to resurect browser testing. #1868

Closed
wants to merge 5 commits into from

Conversation

johnjbarton
Copy link
Contributor

Relies on demo/expressServer.js to expand the test list into a
list of files using the same functions called by the node test driver.
This dependency cost is balanced by no longer having to manually
ensure the tests are added to testRunner.html

Status: Tests run but the mocha progress bar over-writes itself
until the feature tests also converted to ES6 (in progress).

Add MochaDepencencies.js for platform probing.
Refactor TraceurTestRunner to glob asynchronously.
Refactor TraceurTestRunner -> BrowserTestRunner, NodeTestRunner.
Add "node-only:" prefix to suite() titles to exclude node-specific tests.
(Formerly just not included in testRunner.html).
Tweek ModuleStore error message to add URL.
Reorg unit test classes to run() in the endpoint so error messages are
easier to place.

Tests run but the mocha progress bar over-writes itself
until the feature tests also converted to ES6 (in progress).

Add MochaDepencencies.js for platform probing

Refactor TraceurTestRunner to glob asynchonously

Refactor TraceurTestRunner -> BrowserTestRunner, NodeTestRunner

Add node-only: to exclude node-specific tests. (Formerly just not included
in testRunner.html).
Tweek ModuleStore error message to add URL.
Reorg unit test classes to run() in the endpoint so error messages are
easier to place.
@arv arv added the in progress label Apr 5, 2015
server.on('error', function(e) {
console.log('Port ' + port + ' did not work out');
console.log('Port ' + port + ' did not work out');
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe console.error?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@arv
Copy link
Collaborator

arv commented Apr 5, 2015

Very nice. Looking forward to run the test with a real debugger again.

@johnjbarton
Copy link
Contributor Author

PTAL

var express = require('express');
var http = require('http');
var serveIndex = require('serve-index');

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need a copyright header?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@johnjbarton
Copy link
Contributor Author

PTAL

unitTestRunner.run().then(
(failures) => {
process.exit(failures);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wrong indentation

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed it.

@arv
Copy link
Collaborator

arv commented Apr 6, 2015

LGTM

@arv arv removed the in progress label Apr 7, 2015
@johnjbarton johnjbarton deleted the browser-tests branch April 21, 2015 00:59
@johnjbarton johnjbarton restored the browser-tests branch May 12, 2015 23:32
@johnjbarton johnjbarton deleted the browser-tests branch January 29, 2016 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants