Overview
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 is free software and uses the same license as Lua.
Download
LuaCov can be downloaded via LuaRocks:
LuaCov is written in pure Lua and has no external dependencies.
Alternatively, you can get the code directly from the git repo.
Instructions
Using LuaCov consists of two steps: running your script to collect coverage data, and then running luacov on the collected data to generate a report.
To collect coverage data, your script needs to load the luacov Lua module. This can be done from the command-line, without modifying your script, like this:
or
(Alternatively, you can add require("luacov") to the first line of your script.)
Once the script is run, a file called luacov.stats.out is generated. If the file already exists, statistics are added to it. This is useful, for example, for making a series of runs with different input parameters in a test suite. To start the accounting from scratch, just delete the stats file.
To generate a report, just run the luacov command-line script. It expects to find a file named luacov.stats.out in the current directory, and outputs a file named luacov.report.out.
This is an example output of the report file:
============================================================
../test.lua
============================================================
-- Which branch will run?
1 if 10 > 100 then
0 print("I don't think this line will execute.")
0 else
1 print("Hello, LuaCov!")
1 end
Note that to generate this report, luacov reads the source files. Therefore, it expects to find them in the same location they were when the luacov module ran (the stats file stores the filenames, but not the sources themselves).
LuaCov saves its stats upon normal program termination. If your program is a daemon -- in other words, if it does not terminate normally -- you can use the luacov.tick module, which periodically saves the stats file. For example, to run (on Unix systems) LuaCov on Xavante, just modify the first line of xavante_start.lua so it reads:
History
- 0.9.1 [December 7, 2015]
-
- Fixed error when running LuaCov using Lua 5.1.
- 0.9 [December 6, 2015]
-
- with_luacov() function for covering coroutines created via the C API.
- fix priorities in modules list
- improve coverage analysis/exclusions list
- improve handling of multiline function declarations
- LDoc documentation
- 0.8 [September 30, 2015]
-
- Improved lexer which reduces false positives
- luacov.pause() and luacov.resume() functions
- "modules" option for configuration
- Plus several fixes and code cleanups.
- 0.7 [January 12, 2015]
-
- Improvement in detection of long strings.
- Added "savestepsize" option.
- Fix handling "codefromstring" option.
- 0.6 [September 10, 2014]
-
- Support for custom reporter objects
- Configuration option for processing/skipping strings
- Several fixes: behavior of on_exit, inclusion/exclusions lists, etc.
- 0.5 [February 8, 2014]
-
- Improved performance in reporter module
- More improvements in exclusions list
- 0.4 [December 3, 2013]
-
- Lua 5.2 compatibility fixes
- Several improvements in exclusions list
- 0.3 [October 10, 2012]
-
- Added configuration options and files
- Summary in report
- Improved handling of long strings and comments
- Support for coroutines and os.exit()
- 0.2 [April 30, 2009]
-
- Ignore code loaded from strings.
- 0.1 [July 16, 2007]
-
- Initial release.
Credits
LuaCov was originally designed and implemented by Hisham Muhammad as a tool for testing LuaRocks. A number of people have improved it since: see the Git logs for the full list of contributors!
Contact
For more information please contact us. Comments are welcome!