I believe Elm lends itself best to property-based testing <http://blog.jessitron.com/2013/04/property-based-testing-what-is-it.html> of pure code rather than unit testing. Property-based testing can make stronger assertions than unit testing, as long as your code is pure (yet another reason for why you should keep the part of your code that interacts with the "real world" minimal)
In general, you do not need to test whether a constructor creates an item of a given type - that's what the type system is for (and a small part of the beauty of using a strongly-typed language) -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
