-
Notifications
You must be signed in to change notification settings - Fork 645
Add tests for the mirage mock server implemenation #2120
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
☔ The latest upstream changes (presumably #2122) made this pull request unmergeable. Please resolve the merge conflicts. |
bors
added a commit
that referenced
this pull request
Jan 15, 2020
mirage/factories: Use predictable values instead of random fake values This generally is easier to work with in my experience. If we want random values we can still generate them on a case-by-case basis, but by default we will have somewhat stable test fixtures now. This should unblock #2120 :) r? @locks
@bors r+ |
📌 Commit 32a5201 has been approved by |
bors
added a commit
that referenced
this pull request
Jan 15, 2020
Add tests for the mirage mock server implemenation For the frontend test suite we use a mock API server based on https://www.ember-cli-mirage.com/. Since we want to make sure that our mock server returns consistent results that match what the production server would return, we should also write tests for the mock server. This PR implements a first few tests for our current mirage setup. The results of those tests are not entirely perfect yet so we will likely have to refactor some of the mirage code, which should become quite a bit safer with these new tests. r? @locks
☀️ Test successful - checks-travis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the frontend test suite we use a mock API server based on https://www.ember-cli-mirage.com/. Since we want to make sure that our mock server returns consistent results that match what the production server would return, we should also write tests for the mock server.
This PR implements a first few tests for our current mirage setup. The results of those tests are not entirely perfect yet so we will likely have to refactor some of the mirage code, which should become quite a bit safer with these new tests.
r? @locks