-
Notifications
You must be signed in to change notification settings - Fork 25
Clean up getTests function, remove async/await library #38
Conversation
e7b9106
to
3a733fa
Compare
CI is failing, can you also update this PR to run CI on Node 8, 10 and eventually 11? |
We should really add ethereumjs/ethereumjs-config#16 (Git hooks), I also stumble upon this regularly (linting errors). @whymarrh if you want you can open a small PR on this towards the blockchain or other library so that we get started, should be a pretty small one. |
On it |
587cef8
to
d75302a
Compare
ab7085e
to
9ba22f7
Compare
@holgerd77 should be good now, I cleaned up the Travis config as well |
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.
- These code changes are rather heavy. Can you please add a test case for this method, since "getTests" is completely untested atm, so that we can make sure that API functionality is working as before?
- Is Node 11 not working?
- Can you please re-add the JSDoc comment for the method?
I added a test case for the default arguments, but I'm not quite sure how this is used in the wild—what other tests would be useful? |
91b31a2
to
ec667d3
Compare
While using async/await in source code it's better to set minimum node.js version to 8.0 in package.json:
And even better to define last tested version as an upper bound to avoid regression issues. |
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, have also done a short integration test on the VM, looks good! 😄
Hmm, might have been merged too early/quickly, the integration tests I did on the VM show a huge decrease in coverage - see ethereumjs/ethereumjs-monorepo#477 - I think the blockchain tests are not run correctly (at all). Can you have a look at that? |
I added a old commit hash to ethereumjs/ethereumjs-monorepo#477 so we have something to compare against. I can take a look at what's happening—this is weird because we have a test for methods that the vm is using that used to pass as well. |
You can have a look at the CI run, the state tests are just not running, respectively all skipped, this should likely be the cause for coverage decrease (see CircleCI coveralls run). |
Fixes #37
This PR cleans up
getTests
, also replacing the async-await library with nativeasync
/await
.