Compare the Top Code Coverage Tools that integrate with Lua as of October 2025

This a list of Code Coverage tools that integrate with Lua. Use the filters on the left to add additional filters for products that have integrations with Lua. View the products that work with Lua in the table below.

What are Code Coverage Tools for Lua?

Code coverage tools are software utilities designed to analyze the source code of an application and report on the level of code that is tested by automated tests. They usually measure the percentage of lines, blocks, or branches of code that have been executed in a test suite. Many popular programming languages have their own code coverage tools available for developers to use. Compare and read user reviews of the best Code Coverage tools for Lua currently available using the table below. This list is updated regularly.

  • 1
    Codecov

    Codecov

    Codecov

    Develop healthier code. Improve your code review workflow and quality. Codecov provides highly integrated tools to group, merge, archive, and compare coverage reports. Free for open source. Plans starting at $10/user per month. Ruby, Python, C++, Javascript, and more. Plug and play into any CI product and workflow. No setup required. Automatic report merging for all CI and languages into a single report. Get custom statuses on any group of coverage metrics. Review coverage reports by project, folder and type test (unit tests vs integration tests). Detailed report commented directly into your pull request. Codecov is SOC 2 Type II certified, which means a third-party audits and attests to our practices to secure our systems and your data.
    Starting Price: $10 per user per month
  • 2
    LuaCov

    LuaCov

    LuaCov

    LuaCov is a simple coverage analyzer for Lua scripts. When a Lua script is run with the luacov module loaded, it generates a stats file with the number of executions of each line of the script and its loaded modules. The luacov command-line script then processes this file generating a report file which allows one to visualize which code paths were not traversed, which is useful for verifying the effectiveness of a test suite. LuaCov includes several configuration options, which have their defaults stored in src/luacov/defaults.lua. These are the global defaults. To use project specific configuration, create a Lua script setting options as globals or returning a table with some options and store it as .luacov in the project directory from where luacov is being run. For example, this config informs LuaCov that only foo module and its submodules should be covered and that they are located inside src directory.
    Starting Price: Free
  • 3
    Coveralls

    Coveralls

    Coveralls

    We help you deliver code confidently by showing which parts of your code aren’t covered by your test suite. Free for open-source repositories. Pro accounts for private repositories. Instant sign-up through GitHub, Bitbucket, and Gitlab. Maintaining a well-tested codebase is mission-critical. Figuring out where your tests are lacking can be painful. You're already running your tests on a continuous integration server, so shouldn't it be doing the heavy lifting? Coveralls works with your CI server and sifts through your coverage data to find issues you didn't even know you had before they become a problem. If you're just running your code coverage locally, you won't be able to see changes and trends that occur during your entire development cycle. Coveralls lets you inspect every detail of your coverage with unlimited history. Coveralls takes the pain out of tracking your code coverage. Know where you stand with your untested code. Develop with confidence that your code is covered.
    Starting Price: $10 per month
  • Previous
  • You're on page 1
  • Next