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

Unit tests require a running Neo4j instance #9

Open
glesica opened this issue Apr 3, 2017 · 0 comments
Open

Unit tests require a running Neo4j instance #9

glesica opened this issue Apr 3, 2017 · 0 comments

Comments

@glesica
Copy link
Owner

glesica commented Apr 3, 2017

Right now the unit tests require a running server. Worse, they mutate the server, meaning we could accidentally screw with someone's local DB (which shouldn't matter, but might).

We should split the tests into two parts:

  1. A unit test suite that doesn't require a running server
  2. A functional test suite that does require a running server and (ideally) bootstraps an ephemeral server itself on a custom port, possibly using Docker

The unit tests can probably just use recorded payloads from an actual server to test response parsing. We can make assertions about the requests themselves as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant