-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Recommendation service e2e testing #198
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tried the test and they failed in 4 out 5 tests, was that intended?
✖ payment: valid credit card Rejected promise returned by test
✖ payment: invalid credit card
✖ payment: amex credit card not allowed
✖ payment: expired credit card
✔ recommendation: list products
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
The payment service had an issue with it that I fixed in this PR which ill reduce to only the fix Update: heres the new PR fixing those tests #230 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Correct. The payment test failures were fixed in this PR |
Towards #195
Merge after: #196
(If anyone knows a good git workflow for creating a PR based off another one that hasn't yet been merged yet please let me know so I can make these PRs cleaner since this one include all the previous branches commits - all I did was
git checkout -b recc-service-test
while on themic-max:e2e-tests
branch` anyways... shoot me a dm 😄)Changes
client.py
, essentially a manual version of this testThe 1 test sends 5 product ids. this makes sure that the recommendation service always sends back the same array 4 product ids (random ordering) - it caps at 5 recommendations and wont include anything you sent in the request. I was originally going to test it just by including 1 id in the request but then its possible the service sends back 5 products that dont include the one in my request just by chance. So this way is more robust, still not perfect though since the random generator isn't seeded and more reasons I won't get into.