Skip to content

Commit

Permalink
(test): use jest w/ coverage instead STILL NOT WORKING see #6
Browse files Browse the repository at this point in the history
- jest's coverage reporting only knows how to use inline source maps,
  so make them output as inline instead of external .map files
  - can remove exorcist now since inline source maps are built-in
    to browserify

FIXME: jest --coverage on browserify.spec.js runs into an infinite loop
- likely bc it's relying on istanbul-lib-instrument and running it on
  ammo and failing spectacularly -- need it to ignore ammo code

FIXME: webpack passes like with nyc but ignores nothing... :/
  • Loading branch information
agilgur5 committed Nov 26, 2019
1 parent 798ffce commit 5ca5e2f
Show file tree
Hide file tree
Showing 10 changed files with 3,204 additions and 3,290 deletions.
2 changes: 1 addition & 1 deletion .gitignore
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
build/
.nyc_output/
coverage/

### Node ###

Expand Down
15 changes: 15 additions & 0 deletions jest.config.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
module.exports = {
// don't need to run babel on anything (and browserify bundle will error out if we do)
transform: {},
setupFilesAfterEnv: [
// polyfill worker
'@react-frontend-developer/jsdom-worker'
],
coveragePathIgnorePatterns: [
'/node_modules/', // default
'webpack:/node_modules/',
'webpack:/webpack',
'webpack:/test-utils/',
'<rootDir>/test-utils/' // ignore test-utils
]
}
10 changes: 0 additions & 10 deletions nyc.config.js

This file was deleted.

Loading

0 comments on commit 5ca5e2f

Please sign in to comment.