This is an area I've been a little uncomfortable with. There seems two be a
couple of options though:
1) https://github.com/avh4/elm-testable - I haven't used it but it seems
that it provides replacement commands that you can run assertions against.
This approach seems limited as it only
... which is ironic given all emphasis on 'effects as data'
On Monday, 7 November 2016 09:51:56 UTC+1, Austin Bingham wrote:
>
> I asked more or less the same question about a month ago and got no
> responses:
>
>
>
I asked more or less the same question about a month ago and got no
responses:
https://www.reddit.com/r/elm/comments/593vua/how_to_test_the_complete_update_cycle/
https://groups.google.com/d/msg/elm-discuss/634UXiZjRFQ/lVeDED1oBQAJ
The only practical answer right now seems to be to use
I've often worried about the commands bit.
For the view side, you need to test that you are deriving the right data to
render, while it is Evan that needs to test that, given certain data,
expected DOM elements get produced?
On Monday, 7 November 2016 07:44:36 UTC+1, Francesco Orsenigo wrote:
>
