-
Notifications
You must be signed in to change notification settings - Fork 181
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
Update Eplanning Bidder with sizes priority by device type #1143
Conversation
assertThat(result.getErrors()).isEmpty(); | ||
assertThat(result.getValue()).hasSize(1) | ||
.extracting(HttpRequest::getUri) | ||
.containsOnly("https://eplanning.com/clientId/1/FILE/ROS?r=pbs&ncb=1&ur=FILE&e=testadun_itco_de%3A" |
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.
Can be used containsExactly() and then no .hasSize(1) needed
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 think it is much more easier for reader to identify that there can be only one request by hasSize(1) than counting how many values were passed to containsExactly. But probably one hasSize() use for test dedicated to checking that bidder produces only one request is enough, and in all other places containsExactly can be used.
* Update Eplanning Bidder with sizes priority by device type * Minor cleaning * Replace containsOnly with containsExactly
* Update Eplanning Bidder with sizes priority by device type * Minor cleaning * Replace containsOnly with containsExactly
* Update Eplanning Bidder with sizes priority by device type * Minor cleaning * Replace containsOnly with containsExactly
No description provided.