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

test: additional examples for default responses #468

Merged
merged 30 commits into from
Jul 23, 2019

Conversation

lag-of-death
Copy link
Contributor

@lag-of-death lag-of-death commented Jul 17, 2019

This adds failing examples for #413. The passing ones are in #465.

Closes #413

@XVincentX XVincentX force-pushed the test/add-e2e-default-responses-tests_failing branch from 30c7739 to 0aaf369 Compare July 17, 2019 11:06
@XVincentX XVincentX force-pushed the test/add-e2e-default-responses-tests_failing branch from 4c58071 to 890dbfa Compare July 17, 2019 11:40
@XVincentX XVincentX force-pushed the test/add-e2e-default-responses-tests_failing branch from a33b95f to e97d23b Compare July 17, 2019 11:45
@XVincentX
Copy link
Contributor

@philsturgeon

Comment on these failing tests: according to the code this is failing “on purpose”. The ability to look for the closest response is implemented only for successful responses; so you can do 2XX, and you’ll get the first one. Do you want to make the change and expand it to other responses as well, such as 4XX (which is the part of this test?)

philsturgeon
philsturgeon previously approved these changes Jul 17, 2019
@@ -24,7 +24,7 @@
"caseless": "^0.12.0",
"faker": "^4.1.0",
"fp-ts": "^1.19.3",
"json-schema-faker": "json-schema-faker/json-schema-faker",
"json-schema-faker": "XVincentX/json-schema-faker",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this intentional?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, this is a leftover. Will fix.

@philsturgeon
Copy link
Contributor

@lag-of-death I had a go at fixing the conflicts but there is still a yarn.lock change floating around which I don't think should be there. These tests look great, if you can fix that I'll thumbs up and we're done here! 🎉

@lag-of-death
Copy link
Contributor Author

@phil, yarn.lock updated now

philsturgeon
philsturgeon previously approved these changes Jul 19, 2019
@lag-of-death
Copy link
Contributor Author

BLOCKED: #413 (comment)

@XVincentX XVincentX force-pushed the test/add-e2e-default-responses-tests_failing branch from cf31d14 to 7b24d3c Compare July 22, 2019 16:25
@XVincentX XVincentX force-pushed the test/add-e2e-default-responses-tests_failing branch from 36870ae to 6c07710 Compare July 23, 2019 07:02
@XVincentX XVincentX requested a review from philsturgeon July 23, 2019 07:04
@XVincentX XVincentX changed the title test: add failing examples for default responses test: additional examples for default responses Jul 23, 2019
@XVincentX XVincentX merged commit 5d89972 into master Jul 23, 2019
@XVincentX XVincentX deleted the test/add-e2e-default-responses-tests_failing branch July 23, 2019 08:04
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

Successfully merging this pull request may close these issues.

Test Harness: Default Responses
4 participants