You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
◆ contains, in any order:
⚬ an element which:
» is less than: 0 (kotlin.Int <1234789>)
» but no such element was found.
Instead of:
◆ contains, in any order:
⚬ an entry which:
» is less than: 0 (kotlin.Int <1234789>)
⚬ ▶ number of occurrences: 0
◾ is at least: 1
This change shall not affect cases like atLeast(2) or exactly(1)
Your first contribution?
Write a comment I'll work on this if you would like to take this issue over.
This way we get the chance to revise the description in case things have changed in the meantime, we might give you additional hints and we can assign the task to you, so that others do not start as well.
Do not hesitate to ask questions here or to contact us via Atrium's slack channel if you need help
(Invite yourself in case you do not have an account yet).
The text was updated successfully, but these errors were encountered:
robstoll
changed the title
don't show number of occurrences for atLeast(1)
don't show number of occurrences for contains.inAnyOrder.atLeast(1)
Jan 14, 2020
Platform (jvm, js, android): all
Extension (none, kotlin 1.3, jdk8): none
Code related feature
Based on discussion in robstoll/atrium-roadmap#56
We would like to see
Instead of:
This change shall not affect cases like
atLeast(2)
orexactly(1)
Your first contribution?
I'll work on this
if you would like to take this issue over.This way we get the chance to revise the description in case things have changed in the meantime, we might give you additional hints and we can assign the task to you, so that others do not start as well.
(Invite yourself in case you do not have an account yet).
The text was updated successfully, but these errors were encountered: