diff options
| author | Josh Soref <2119212+jsoref@users.noreply.github.com> | 2022-02-22 17:01:28 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-22 22:01:28 +0000 |
| commit | 2b8e6958f40ef36c1508118ac36a43694283a83c (patch) | |
| tree | fa9a9b6843546bdb297b00bc78b83ab4c318f724 /test/coverage.md | |
| parent | 85faeb34719e2b0898d319b02416f669d70f4562 (diff) | |
| download | rspamd-2b8e6958f40ef36c1508118ac36a43694283a83c.tar.gz rspamd-2b8e6958f40ef36c1508118ac36a43694283a83c.zip | |
Spelling (#4086)
[Rework] Massive spelling fix from @jsoref
Diffstat (limited to 'test/coverage.md')
| -rw-r--r-- | test/coverage.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/test/coverage.md b/test/coverage.md index c5ee8b071..8d177f318 100644 --- a/test/coverage.md +++ b/test/coverage.md @@ -28,7 +28,7 @@ However, there are some moment to highlight: - To make it possible, we explicitly run `umask 0000` in "build" and "functional" stages in .circleci/config.yml - After run, we persist coverage data in "coverage.${CIRCLE\_JOB}.dump" during this build flow, see `capture_coverage_data`, to use it on the final stage. -- we user `cpp-coverals` because it is able to save data for coveralls without actually sending it. We send on our own +- we use `cpp-coveralls` because it is able to save data for coveralls without actually sending it. We send on our own along with Lua-coverage. Lua coverage @@ -40,7 +40,7 @@ First part contains nothing interesting, just see `test/lua/tests.lua`. 1. Coverage collecting is initiated and dumped in `test/functional/lua/test_coverage.lua` (there are a lot of comments inside). This file should be included on the very early stage of test run. Usually it's included via config. -2. Coverage is dumped into ${TMPDIR}/%{woker_name}.luacov.stats.out +2. Coverage is dumped into ${TMPDIR}/%{worker_name}.luacov.stats.out 3. All worker coverage reports are merged into `lua_coverage_report.json` (see `collect_lua_coverage()`) 4. finally, `lua_coverage_report.json` is persisted in build flow (see `functional` stage) |