-
Notifications
You must be signed in to change notification settings - Fork 404
FDC: update api version, integration tests, and CONTRIBUTING.md #2972
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
base: master
Are you sure you want to change the base?
Conversation
expect(resp.data.users).to.deep.include(expectedUser); | ||
expect(resp.data.users.length).to.greaterThan(1); | ||
resp.data.users.forEach((user) => { | ||
expect(expectedUserIds).to.include(user.id); |
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.
Why don't we compare the full objects here? You can use deep.equal
to compare the arrays I believe
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 check the full objects, but these objects are updated / edited by other test cases so I wanted to make the checks rely only on their IDs - the other tests which mutate the data check individual fields.
To make the tests even more air-tight, I could use different users / IDs for each test, rather than passing the same ID/object around to be used in different test scenarios. LMK WYT
v1alpha
tov1