Hi I m new to Atrium and Kotlin so bear with me I have a col

Question

Hi I m new to Atrium and Kotlin so bear with me I have a collection of objects and I want to make assertions on its content using some of the objects properties What I currently have is not readable Is there a cleaner way ```data class Member val name String val interest String val favoriteNumber Int val members = listOf Member Me Kotlin Random nextInt Member MyDog food Random nextInt expect members containsExactly feature f it name toBe Me feature f it interest toBe Kotlin feature f it name toBe MyDog feature f it interest toBe food ```

robstoll · Answer

Hi Igor in case you use this combination name interest often then I would suggest you add a corresponding assertion function maybe you can come up with a better name ```fun Expect lt Member gt hasNameAndInterest name String interest String = this feature f it name toBe name feature f it interest toBe interest ``` then it can be rewritten to ```expect members containsExactly hasNameAndInterest Me Kotlin hasNameAndInterest MyDog food ```

robstoll · Answer

In case `toBe` was only an example and you want to perform other assertions on the properties e g `startsWith Kot ` then you could provide a shortcut for the properties ```val Expect lt Member gt name get = name this getExpectOfFeature allows to define an assertion group for the feature fun Expect lt Member gt name assertionCreator Expect lt String gt gt Unit = name this addToInitial assertionCreator private fun name expect Expect lt Member gt = ExpectImpl feature property expect Member name ``` Whether this boilerplate is worth it depends on how many times you use the property IMO Then you could use it as follows ```expect members containsExactly name toBe Me name startsWith Ro endsWith t ```

robstoll · Answer

< Igor Akkerman> I hope that helps otherwise let me know

Igor Akkerman · Answer

Hi Robert thanks a lot for your help I m really a fan of the flexibility of Atrium and the expressiveness of the assertion code and especially of the output in case of test failure Might there be a way on the side of the library to make the latter version require less boilerplate generalizing assertions on properties From AssertJ I remember it allowing to specify fields to do comparisons on It was using the field names as Strings though I noticed a tiny irregularity While the assertion works correctly in entry 1 the output shows name as Me while the object has MyDog Could the assertion have cached the value in a wrong way `ch tutteli atrium reporting AtriumError expect Member name=Me interest=Kotlin favoriteNumber=1771517067 Member name=MyDog interest=food favoriteNumber= 1574926733 java util Arrays ArrayList lt 1682681674 gt ` contains only in order heavy check mark arrow forward entry 0 Member name=Me interest=Kotlin favoriteNumber=1771517067 atriumtest AtriumTest Member lt 613298587 gt black medium small square an entry which arrow forward name Me lt 1446983876 gt black medium small square to be Me lt 1446983876 gt arrow forward interest Kotlin lt 1042790962 gt black medium small square to be Kotlin lt 1042790962 gt arrow forward entry 1 Member name=MyDog interest=food favoriteNumber= 1574926733 atriumtest AtriumTest Member lt 2130192211 gt black medium small square an entry which arrow forward name Me lt 1446983876 gt black medium small square to be MyDog lt 990897274 gt arrow forward interest Kotlin lt 1042790962 gt black medium small square to be foodX lt 539690370 gt heavy check mark arrow forward size 2 lt 593415583 gt black medium small square to be 2 lt 593415583 gt

robstoll · Answer

do you mean simplifying `feature f it name `

robstoll · Answer

or are you talking about something in the output

robstoll · Answer

what would you like to see

robstoll · Answer

ah forget what I just wrote smile I missed the `I noticed a tiny irregularity`

Igor Akkerman · Answer

You didn t miss it I hit enter to quickly and edited the original message wink

robstoll · Answer

ah ok

Igor Akkerman · Answer

Yes I meant simplifying `feature f it name `

robstoll · Answer

the irregularity is actually a bug I have on my radar for a longer time planned for 0 10 0 now see roadmap <https github com robstoll atrium 0100> You are the first noticing reporting it though

robstoll · Answer

Atrium should not show the value at all in it should be as follows ```an entry which gt gt name to be My Dog ```

Igor Akkerman · Answer

Actually it s better if it shows the actual value alongside the expected value so you see the diff immediately

robstoll · Answer

regarding simplifying `feature` it is mainly that complicated because Kotlin has unfortunately many bugs in the area of type inference and method overloading See the list here <https github com robstoll atrium kotlin bugs> would be nice if you can upvote some so jetbrains invests a bit more time in this area

robstoll · Answer

you are right it could be shown for `in order only` it would not make sense for `in any order`

Igor Akkerman · Answer

True

robstoll · Answer

good input I would have removed it for all functions I ll keep that in mind

Igor Akkerman · Answer

Great thanks

robstoll · Answer

you could also write `feature Member name ` in case you find that simpler

robstoll · Answer

see also <https github com robstoll atrium roadmap issues 21> maybe you can comment there regarding your use case

Igor Akkerman · Answer

ah missed that one that s perfectly readable writable then

Igor Akkerman · Answer

awesome

Igor Akkerman · Answer

I believe `feature Member name ` is good enough really No idea if something like `containsExactly Member name toBe Me Member interest toBe Kotlin ` would be technically possible

Igor Akkerman · Answer

To me comparing data classes by showing their toString diff is perfectly fine

Igor Akkerman · Answer

I added a comment to <https github com robstoll atrium roadmap issues 21>