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

Replace instanbul with nyc #153

Closed
vweevers opened this issue May 13, 2018 · 6 comments
Closed

Replace instanbul with nyc #153

vweevers opened this issue May 13, 2018 · 6 comments
Assignees

Comments

@vweevers
Copy link
Member

When we have a solid setup here, we can copy it to levelup (Level/levelup#459) and others.

@vweevers
Copy link
Member Author

vweevers commented May 13, 2018

Some research. Goal: combine lcov reports of node and browser tests and send it to coveralls.

@vweevers
Copy link
Member Author

vweevers commented May 13, 2018

Plan:

  • Remove TypeScript tests from memdown (to clean up npm scripts)
  • Remove existing coverage and report-coverage npm scripts and istanbul dependencies
  • Add coverage script: nyc report --reporter=text-lcov | coveralls
  • Add hook to .travis.yml: after_success: npm run coverage. Each Travis node job will send lcov reports to coveralls.
  • Add a feature to airtap to write LCOV files instanbul files to disk. Each browser result should be written to its own file.
  • Change our Travis browser job to run npm run test-browsers && npm run report-coverage.
  • Configure Coveralls to merge results of parallel builds.

@ralphtheninja
Copy link
Member

Good work @vweevers

@vweevers
Copy link
Member Author

Before attacking the airtap part, which requires writing code, we can setup code coverage for node only and test parallel builds.

@vweevers
Copy link
Member Author

vweevers commented Jul 1, 2018

Nice, nyc doesn't seem to care about the .nyc-output/*.json filenames. We could write .nyc-output/airtap-001.json, .nyc-output/airtap-002.json or perhaps .nyc-output/<browser>-<version>-<os>.json, and nyc report still works.

@vweevers
Copy link
Member Author

vweevers commented Jul 1, 2018

Waiting on airtap/airtap#194

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

No branches or pull requests

2 participants