Waking up an old discussion here ... I'm new to Elm and considering it for a new project.
I was surprised / disappointed to learn that code coverage is not yet supported in Elm. Has there been any further consideration of support for code coverage in Elm? The lack of coverage is not an absolute show-stopper for me, but my experience with other languages has taught me to be far more comfortable with data model code that is thoroughly tested. (Like others in this thread, I am less concerned with unit test coverage for view code.) -Eric On Tuesday, October 20, 2015 at 2:37:26 PM UTC-7, Igor Tur wrote: > > I see it this way: > > - Source maps are required for Code Coverage (example > https://www.npmjs.com/package/istanbul-coverage-source-map) > - Code Coverage is required for integration into any enterprise > environment (it doesn't really open the door, but absence may close the > door) > > Also something like elmLint would be required. > > And then integration with SonarCube (or similar) systems - for source code > analysis, complexity and overall control of source code changes. > > Thank you, > Igor > > > On Wednesday, July 1, 2015 at 6:38:52 PM UTC-7, Evan wrote: > >> Based on Texas' post >> <https://groups.google.com/forum/#!topic/elm-discuss/fZRGysggvdU>, I am >> really curious to hear folks thoughts on source maps for my personal >> planning and prioritization! >> >> Last time source maps came up, I was choosing between "fix the type >> checker" and "do source maps". Fixing inference in 0.9 (or whatever) was a >> really really big deal and I think it was the right choice, but we never >> revisited the source maps. It also does not fit into my workflow (which is >> very atypical) so it's not something that I *personally* miss. >> >> So essentially, how would source maps help you? >> >> - Do you have times when you want them? >> - Do you think it has a marketing / perception benefit that'd make it >> worth it no matter what? >> >> If you aren't a regular poster, I'm extra interested to hear your >> perspective! I need to collect data and perspectives on this to prioritize >> it. >> > -- 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.
