Coverage report ceased to work

[evertonfraga]

Since the recent changes in the test suite #134, the Coverage report stopped working, leading to a wrong 0% test coverage result.

It happened for the first time in Travis and it got carried over to the GH actions.

[ryanio]

Thanks for the report, I will look into it and see what could be going on.

[evertonfraga]

Thanks!

I think that might lead to a slightly broader discussion regarding how we're using Coveralls and how should it be used in conjunction with GH actions.

I put together this gist with how these reports are generated (npm run x) and how they are executed in GH actions.

I have some exploratory questions (that I can investigate myself as well)

• is npm run coveralls enough to send the reports?
• can it be fully replaced by coverallsapp/github-action@master?

if so, we gotta choose one to use

[ryanio]

Ah yes I forgot to include the .nycrc code from Holger here #134 (comment). I will open a PR for that now.

Good questions, I had some of the same questions, and also found this: ethereumjs/ethereumjs-config#22