Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Enable coverage reporting #3100
Enable coverage reporting #3100
Changes from all commits
b82d545
89ac4c7
d58f234
d3b2549
5877439
93279c1
6d1b9c7
3192156
856abbe
464b464
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this interfere with / override
ava
settings in individual package'syarn test
?It looks like this is meant for use by a top-level
yarn test
which runs tests in all packages in parallel. When I last looked into doing that, I got stuck on the differentrequire
options we needed for different sets of tests (in particular importinginstall-ses
, orinstall-metering-and-ses
). Did you find a solution for that?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only when run from the top level. If
yarn test
is run in the specific package, the package's settings will take effect.Yes. It turns out we only use
"require"
for two modules:"esm"
(which appears in basically every"ava"
config), and an enzyme setup script (only used inpackages/ui-components/package.json
). So, the situation is not nearly as grim.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I think @dtribble was once keen on using the AVA config to jam a
-r @agoric/install-ses
into e.g. all zoe tests, to avoid adding a line to the top of every test file, and that was going to push us to e.g. move all@agoric/install-metering-and-ses
tests into one directory, and have two top-level AVA calls (with one set of-r
options each). I think we talked him down from that :).I've got
nodeArguments: [ "--expose-gc" ]
in the SwingSet package.json, to enable GC controls while testing. We may need to move that to the top-level package.json to make sure swingset tests work both from the top level and frompackages/SwingSet
(and also when e.g. Zoe does swingset-based tests, although if they're short enough, we can probably tolerate the inability to provoke GC).This file was deleted.