Testing?

[nelsonic]

What is like to write tests for Elm code? Is there way to collect coverage info? How fast can we run a suite? (e.g. for a large project with 10k+ tests ... seconds or minutes?)

This looks like a good place to start: http://package.elm-lang.org/packages/elm-community/elm-test/2.1.0 and the fact that someone is working on a Book is a really good sign: http://elm-test.com

[nelsonic]

Codecov does not appear to have explicit support for elm-lang (yet) ... https://codecov.io/

need to ask @stevepeak if someone is already working on it or if we can contribute...?

[stevepeak]

I'll investigate 👍 Thank you @nelsonic

[naazy]

@nelsonic Is a section about the circle.yml for Elm better suited to this repo or https://github.com/dwyl/learn-circleci (or neither)?

[iteles]

@stevepeak Any further thoughts on whether codecov is thinking of supporting Elm? We're starting to use it in earnest now and would love to keep using our favourite coverage tool with it! :heart:

[stevepeak]

Hey @iteles, we certainly wish to support it and it's just a matter of understanding how to generate coverage reports and what format the reports are in. Here are the goals to support Elm:

1. Add an example repository to Codecov Github account. LIke https://github.com/codecov/example-java
2. Share with us an example exported coverage report so we can build a parser for it.

I'm happy to help out where I can here. Since you are familiar with the language I'm sure you can gather these items pretty fast 👍