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 test for the curl api should spin up a sqlite server on the side #21

Open
jetpacktuxedo opened this issue Apr 18, 2016 · 4 comments

Comments

@jetpacktuxedo
Copy link
Collaborator

this way unit tests don't pollute the real db

@jetpacktuxedo
Copy link
Collaborator Author

@Endi1
Copy link
Contributor

Endi1 commented Apr 28, 2016

@jetpacktuxedo
Copy link
Collaborator Author

That set of unit tests creates and destroys a sqlite db in the setup/teardown methods. The curl unit tests currently don't. They also curl against the actual server rather than spinning up a test copy to curl against. This causes the test pastes to be written to the actual DB.

@Endi1
Copy link
Contributor

Endi1 commented Apr 28, 2016

My bad, I was looking at the wrong file. Submitted a pull request for this issue.

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

No branches or pull requests

2 participants