test: Test coverage for integration tests

[alexgarel]

This should bring coverage from the running backend server during integration tests.

[codecov-commenter]

Codecov Report

Attention: 15 lines in your changes are missing coverage. Please review.

Comparison is base (55a9b22) 49.54% compared to head (265a2a2) 51.62%.

Files	Patch %	Lines
lib/ProductOpener/Web.pm	0.00%	12 Missing ⚠️
lib/ProductOpener/TestCover.pm	50.00%	1 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9706      +/-   ##
==========================================
+ Coverage   49.54%   51.62%   +2.08%     
==========================================
  Files          67       73       +6     
  Lines       20650    20802     +152     
  Branches     4980     4992      +12     
==========================================
+ Hits        10231    10739     +508     
+ Misses       9131     8701     -430     
- Partials     1288     1362      +74     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[alexgarel]

This works and it's an improvement.

The only thing is that there are no cgi in coverage report, I don't know why… yet.

[alexgarel]

I though it was an easy one, but it's not !

The problem is that apache is running scripts independently in some way, but codecoverage initialize only once. Even forcing apache to only one process does not work.

I can force cgi scripts to report, but I end up with always 100% coverage, which is not true, and no info on branches, conditions, etc.

This thread has a link to a working coverage apache example, but it's using ApacheTest mechanism.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud