Mark the repo as unmaintained and archive it about jest-teamcity-reporter HOT 4 OPEN

@fatso83, looks like you did't understand the gap I mentioned.
TeamCity has a built-in ability to render code coverage stats in overview + it collects historical trends.
So we need to post those stats using service messages and TeamCity will take care of the rest.
jest-teamcity plugin should post those data from generated jest coverage results.

from jest-teamcity-reporter.

HI there, we still use this package and recently found an issue
I checked proposed jest-teamcity and figured out it lacks code coverage reporting code - so it simply does not fit

from jest-teamcity-reporter.

@Maxim-Zabunkov Code coverage is generated by jest itself and jest-junit does a fine job of creating the junit xml files.

When running jest --ci --coverage I get a nice coverage-final.json JSON file with stats on each file. This is built-in.

from jest-teamcity-reporter.

Probably right about that. We had stopped using TC by the time I created that last comment anyhow 😄

from jest-teamcity-reporter.