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

E2E test coverage #103

Closed
dicarlo2 opened this issue Mar 19, 2018 · 0 comments
Closed

E2E test coverage #103

dicarlo2 opened this issue Mar 19, 2018 · 0 comments
Labels
good first issue help wanted kind/feature Categorizes issue or PR as related to a new feature.

Comments

@dicarlo2
Copy link
Contributor

dicarlo2 commented Mar 19, 2018

Description

It'd be great if there was a way to get line coverage for the e2e tests, since they exercise the majority of the codebase. The difficulty comes in that the e2e tests run in multiple sub-processes, we've got the neo-one server running on one process, neo-one commands running in other processes and (potentially) a neo-one node running in another process.

At a high level the 2 main challenges are:

  1. E2E tests execute logic that runs in multiple subprocesses that themselves spawn more subprocesses.
  2. E2E tests run against the compiled output, so even if we fixed 1/, how do we get coverage against the original source code?

Some research:

@dicarlo2 dicarlo2 added kind/feature Categorizes issue or PR as related to a new feature. help wanted good first issue priority/important-soon Must be staffed and worked on either currently, or very soon. labels Mar 19, 2018
@dicarlo2 dicarlo2 added [zube]: Inbox and removed priority/important-soon Must be staffed and worked on either currently, or very soon. [zube]: Inbox labels May 22, 2018
@dicarlo2 dicarlo2 closed this as completed Nov 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue help wanted kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant