You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
A unit test suite that doesn't require a running server
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: