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

Update to recent js-reporters and mocha #179

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update to recent js-reporters and mocha #179

wants to merge 1 commit into from

Conversation

eugenet8k
Copy link
Contributor

  • Update to mocha 3.2.0
  • Update to js-reporters 1.2.0
  • Fix few issues in server.js caused by the update
    • js-reporters use NodeJS process which fails in a browser.
      Add fake init ahead of script to avoid errors.
    • js-reporters dist has var index$10 which is treated as regex ref.
      Use split/join approach instead of regex replace.

* Update to mocha 3.4.2
* Update to js-reporters 1.2.0
* Fix few issues in `server.js` caused by the update
 - `js-reporters` use NodeJS `process` which fails in a browser.
   Add fake init ahead of script to avoid errors.
 - `js-reporters` dist has `var index$10` which is treated as regex ref.
   Use split/join approach instead of regex replace.
@paulfalgout paulfalgout mentioned this pull request Aug 14, 2017
Krinkle added a commit to qunitjs/js-reporters that referenced this pull request Sep 24, 2020
Follows-up 3708273. Now that I've had a while to take
inventory, I think we can bring this back to make distribution
and re-use a bit easier for things like browserstack-runner.

Highlights:

* Switch from 'chalk' to 'kleur'.
  Kleur is a a dependency-free alternative that is safe to run
  in a browser environment without needing to do anything extra
  to emulate Node etc.

  Downstream browserstack-runner was having to mock the Node
  'process' global previously because of this. There are ways
  around that, but it's naturally simplest to just not have any
  code that is just naturally agnostic of Node vs browser.

  Ref browserstack/browserstack-runner#179.

* Use Karma to run the unit tests in the browser.

* Use NYC to generate a code coverage report over the unit
  and integration tests.
Krinkle added a commit to qunitjs/js-reporters that referenced this pull request Sep 24, 2020
Follows-up 3708273. Now that I've had a while to take
inventory, I think we can bring this back to make distribution
and re-use a bit easier for things like browserstack-runner.

Highlights:

* Switch from 'chalk' to 'kleur'.
  Kleur is a a dependency-free alternative that is safe to run
  in a browser environment without needing to do anything extra
  to emulate Node etc.

  Downstream browserstack-runner was having to mock the Node
  'process' global previously because of this. There are ways
  around that, but it's naturally simplest to just not have any
  code that is just naturally agnostic of Node vs browser.

  Ref browserstack/browserstack-runner#179.

* Use Karma to run the unit tests in the browser.

* Use NYC to generate a code coverage report over the unit
  and integration tests.
Krinkle added a commit to qunitjs/js-reporters that referenced this pull request Sep 24, 2020
Follows-up 3708273. Now that I've had a while to take
inventory, I think we can bring this back to make distribution
and re-use a bit easier for things like browserstack-runner.

Highlights:

* Switch from 'chalk' to 'kleur'.
  Kleur is a a dependency-free alternative that is safe to run
  in a browser environment without needing to do anything extra
  to emulate Node etc.

  Downstream browserstack-runner was having to mock the Node
  'process' global previously because of this. There are ways
  around that, but it's naturally simplest to just not have any
  code that is just naturally agnostic of Node vs browser.

  Ref browserstack/browserstack-runner#179.

* Use Karma to run the unit tests in the browser.

* Use NYC to generate a code coverage report over the unit
  and integration tests.
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.

1 participant