Code Monkey home page Code Monkey logo

Comments (6)

zuiderkwast avatar zuiderkwast commented on July 25, 2024 2

I think it should be pretty strait-forward to come up with a test case for most of the uncovered lines. Most functions are helper functions for either the subtyping relation, for type_check_expr (type inference/propagation) or for type_check_expr_in (typechecking against a known type). Basically every erlang expression can exist in a context where we expect a certain type (e.g. a function with a spec) and in a context where we don't.

If some code is really hard to understand why it is there, perhaps it shouldn't be there or it needs some renaming or explanation in comments. Post a comment on any part of the code and I'll be happy to try to answer.

from gradualizer.

josefs avatar josefs commented on July 25, 2024 1

SWEET! That's super useful @zuiderkwast!

For posterity I just want to say that the coverage report can be found in cover/index.html after running make tests COVER=1.

from gradualizer.

zuiderkwast avatar zuiderkwast commented on July 25, 2024

It is possible to generet a code coverage report with make tests COVER=1 if I remember correctly. (I implemented that in erlang.mk some years ago.)

from gradualizer.

Zalastax avatar Zalastax commented on July 25, 2024

How do I know what tests need to be written? It's tricky to look at the coverage report and figure out what will cause flow to reach each branch. Is it a better idea to pick a big corpus of code and type check that and then minimize each failing case?

from gradualizer.

NelsonVides avatar NelsonVides commented on July 25, 2024

make tests COVER=1 doesn't do anything since a long time. For a while, rebar3 cover was making the pretty html files, but now after the strong cut away from rebar, make cover produces only the coverage.xml file, which is not very human readable.

rebar3 do eunit -c, cover works for now, and the files this generates are correctly gitignored.

from gradualizer.

zuiderkwast avatar zuiderkwast commented on July 25, 2024

I think there are plain text cover files generated under cover/. If you need the html files, we can just add an option to generate them in the Makefile. Also, if you don't want to download the covertool to generate the xml file, we can make that a separate target, so that make cover only produces the html and/or text files.

from gradualizer.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.