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.

Sign up for GitHub

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

Jump to bottom

Split database tests away from unit tests and name them integration tests #421

Open
emilgoldsmith opened this issue Jul 6, 2018 · 0 comments
Open

Split database tests away from unit tests and name them integration tests #421

emilgoldsmith opened this issue Jul 6, 2018 · 0 comments

Comments

@emilgoldsmith
Copy link
Member

Expected Behavior

Unit tests shouldn't be accessing other processes like databases, and the database tests are also flaky, which unit tests should never be.

Possible Solution

Make a third class of tests, right now we have unit and e2e, we'll make a third one integration that for now can be just database tests and in the future maybe do more as well
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@emilgoldsmith