Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mismatch in test counts #8

Closed
blainekasten opened this issue Jan 12, 2017 · 14 comments
Closed

Mismatch in test counts #8

blainekasten opened this issue Jan 12, 2017 · 14 comments

Comments

@blainekasten
Copy link

I'm not sure where this could be going wrong. But this is what I'm seeing in TC.

Build tab:
image

Tests Tab:
image

I'm curious why the Tests tab would only report 785 when jest reports 1128

@richardscarrott
Copy link

@blainekasten Do you use forceExit in jest?

@blainekasten
Copy link
Author

nope.

@winterbe
Copy link
Owner

Hm, strange. Which Teamcity version do you use?

@blainekasten
Copy link
Author

blainekasten commented Jan 23, 2017 via email

@winterbe
Copy link
Owner

winterbe commented Jan 23, 2017

Sorry, can't help on this one. I'm using TC Professional 10.0.1 and can't reproduce this problem.

Is it possible for you to test with latest TC 10 release?

@richardscarrott
Copy link

Yeah we're seeing the same problem in TC 9.1

@blainekasten
Copy link
Author

@winterbe I have no control over our TC version. Is there anything we can do to help you support this version?

@winterbe
Copy link
Owner

This Jest Reporter relies on the TC build script interaction. Maybe something has changed between TC9 and TC10 which causes the issue.

However the total test count is not reporter by this project, it's measured by TC. So I really don't know why it's not working in TC9. I also don't have a TC9 installation in order to reproduce the issue.

You should check the TC Youtrack for open bugs regarding reported test count. Also feel free to debug this for your own. Feel free to send a PR if you find a fix.

@ToshB
Copy link

ToshB commented Mar 22, 2017

I have a similar issue in TC10.0:
Log Output: 6 skipped, 118 passed, 124 total
Reports as 109 Tests passed

Then someone checked in an it.only-statement, halving the number of actual run tests, which should have triggered a warning in Teamcity, but the reporter reported an increase in the number of tests:

Log Output: 69 skipped, 59 passed, 128 total
Reports as 113 Tests passed

@bumbu
Copy link

bumbu commented Jun 20, 2017

Same issue with TeamCity Enterprise 2017.1.1

@tmeador-dl
Copy link

tmeador-dl commented Jun 25, 2017

It looks like this might be happening because only the it statement descriptions are being reported, and not the combined describe/it descriptions. For instance I have multiple it statements that read 'should have property theSameProperty' but in different describe blocks. These tests are showing up in TeamCity as a single test with multiple run counts. (TeamCity Enterprise 10.0.2.)

@Ant-VAV
Copy link

Ant-VAV commented Aug 15, 2017

Same issue with TeamCity Enterprise 2017.1.2

@Ant-VAV
Copy link

Ant-VAV commented Aug 15, 2017

As one of possible methods to solve this issue: #16

@winterbe
Copy link
Owner

winterbe commented Aug 23, 2017

I just published the fix from @Ant-VAV (thanks for that). Please test again with version 0.7.0 to verify that the problem is solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants