You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, thanks for creating this template it helps a lot to start plugin development.
In test GitHub job you provide section to evaluate tests coverage and post it to coveralls.io. After building plugin coverage calculated and posted, but coveralls shows it as 0%.
Steps to reproduce:
Generate repo from this template
Update .github/workflows/test.yml by removing Kong Enterprice versions
Create an account on coveralls.io and add your new repo
I've checked source of pongo.sh from kong-pongo and saw that you just forward --coverage argument to busted and saw your notice that coverage only calculated for unit tests, but based on content of coverage files I expect to see something greater than zero on coveralls.io.
I detected the only suspicious thing - if you enable verbose output of luacov-coveralls by adding -v switch you will see source_files: 0.
The text was updated successfully, but these errors were encountered:
Hello, thanks for creating this template it helps a lot to start plugin development.
In
test
GitHub job you provide section to evaluate tests coverage and post it to coveralls.io. After building plugin coverage calculated and posted, but coveralls shows it as 0%.Steps to reproduce:
.github/workflows/test.yml
by removing Kong Enterprice versionsExpected result:
step (4): Build successfull
step (5): Coverage greater than 0% shown
Actual result:
step (5): Coverage 0% shown
Going through my steps I've created repo https://github.com/seprokof/kong-plugin , added repo to coveralls.io https://coveralls.io/github/seprokof/kong-plugin and build is https://github.com/seprokof/kong-plugin/actions/runs/5438212946 . I've added little bit of debug info but outputting content of coverage files during the build.
I've checked source of
pongo.sh
fromkong-pongo
and saw that you just forward--coverage
argument tobusted
and saw your notice that coverage only calculated for unit tests, but based on content of coverage files I expect to see something greater than zero on coveralls.io.I detected the only suspicious thing - if you enable verbose output of
luacov-coveralls
by adding-v
switch you will seesource_files: 0
.The text was updated successfully, but these errors were encountered: