Background I have a test suite and I need to know the coverage of the project. I have played around with mix test --cover but I find the native erlang’s coverage analysis tool to be insufficient at best. The native coverage tool doesn’t tell you about branch coverage nor function coverage. It’s on…

[image] Fl4m3Ph03n1x: For BEAM, every line is a statement. No exactly, the difference is that JS is interpreted, so it has no notion of “compiled code”. In Erlang on the other hand there is such possibility, and single line can result in multiple VM “statements”, for example: Integer.to_stri…

[image] Fl4m3Ph03n1x: Is there any tool that uses Istanbul for code coverage metrics with Elixir instead of the native erlang one? No, as InstanbulJS is ECMAScript specific. There is no “general purpose” coverage analysis tool, as this kind of metric is highly language/platform dependant. …

[image] hauleth: You can check out cover module to see what you can get out of it. As far as I know this is only coverage tool available. I already did it. This module is what I refer to as the native cover tool and all the drawbacks I present are actually drawbacks of cover - which is why …

… [image] dimitarvp: Have you tried GitHub - parroty/excoveralls: Coverage report tool for Elixir with coveralls.io integration. · GitHub ? [image] Fl4m3Ph03n1x: I am now using ExCoveralls . It is considerably better than the previous options, it allows me to easily configure which folder…

The point is that in Erlang there is no much difference between statements and lines, so I would roughly say that line = statement. Second stat is branch which also do not make much sense, as most of the time Erlang will use pattern match, so it will be split into 2 categories: function clauses li…

[image] hauleth: The point is that in Erlang there is no much difference between statements and lines , so I would roughly say that line = statement . What's the difference between statements and lines? opened 09:32PM - 04 Jun 16 UTC…

[image] Fl4m3Ph03n1x: No. Lines are not statements. Erlang do not have notation of “statement” in its’ .beam files , only lines are stored. While in theory you could use 'Abst' chunk to extract “statements” it would be infeasible due to macros (especially in Elixir), and even then there is no …

[image] hauleth: Erlang do not have notation of “statement” in its’ .beam files , only lines are stored. While in theory you could use 'Abst' chunk to extract “statements” it would be infeasible due to macros (especially in Elixir), and even then there is no mapping between 'Abst' values and 'Cod…

FWIW the current cover tool does not use the assembly stored in .beam files. What it does is to retrieve the Erlang AST for the module, transform it and recompile. The transformation consists primarily of introducing calls to :ets.update_counter/3 each time the line annotation of the AST changes. T…