-
Notifications
You must be signed in to change notification settings - Fork 0
MPT-14888 Add E2E tests for catalog items #118
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
Conversation
1d6108e to
70508af
Compare
| service = async_mpt_vendor.catalog.items | ||
| update_data = {"name": "e2e - delete me (updated)"} | ||
| item = await service.update(async_created_item.id, update_data) | ||
| assert item.name == "e2e - delete me (updated)" |
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.
We could and we do it some times, although this goes against the Requirement 2 of the TDR:
1. E2E tests should check the communication between the client and the real MPT API
2. It shouldn’t test the MPT API itself. Means tests should not check permutations of the cases of the MPT API, and also, it shouldn’t check that MPT creates/updates/deletes entities properly
3. E2E tests should check that simple requests/responses are not failing
For now we try to minimise the request done to the API for performance purposes.
3245df1 to
5964e1c
Compare
5964e1c to
e5590af
Compare
|



No description provided.