I haven't personally used Kakao or Kaspresso, so take my response with a grain of salt. But from what I've seen about them, they seem more opinionated than Barista on how to write your tests. They are very linked to the concept of page object with a custom DSL, which can be helpful for some projects for sure.
Barista is more "low level", closer to Espresso but with a simpler API and some hidden "magic" as described above. You decide how to structure your own tests. In this post, I showed how we do our PageObjects, but you're free to use any other approach.
In my personal and debatable opinion, our PageObjects are more semantic, because we write them from the perspective of what the user would be doing. However, the DSL from Kakao exposes some information about the structure of the screen (button this, recyclerview that). I'm not saying that's wrong, it's just different.
I hope I could shed some light on your question :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I haven't personally used Kakao or Kaspresso, so take my response with a grain of salt. But from what I've seen about them, they seem more opinionated than Barista on how to write your tests. They are very linked to the concept of page object with a custom DSL, which can be helpful for some projects for sure.
Barista is more "low level", closer to Espresso but with a simpler API and some hidden "magic" as described above. You decide how to structure your own tests. In this post, I showed how we do our PageObjects, but you're free to use any other approach.
In my personal and debatable opinion, our PageObjects are more semantic, because we write them from the perspective of what the user would be doing. However, the DSL from Kakao exposes some information about the structure of the screen (button this, recyclerview that). I'm not saying that's wrong, it's just different.
I hope I could shed some light on your question :)