jest-junit incorrectly merges 2 test suites about jest-junit HOT 8 CLOSED

Jest does not give the ability for reporters to easily iterate through describe blocks recursively so even if you wanted a reporter to treat describe blocks as test suites it would be an error-prone, edge case heavy, pain.

I am very willing to accept pull requests if you wanted to give it a shot.

from jest-junit.

Thanks for submitting an issue!

I think the confusion here is that Jest actually considers each test file a suite, not each describe block. So this is how jest-junit represents things.

You can absolutely have multiple describe blocks per file and even nest them as you have done here. jest-junit can use those describe block names in various places based on your configuration.

Here is how your test looks to jest-junit. You can see jest iterates through the tests not the describe blocks.

  "numFailedTestSuites": 0,
  "numFailedTests": 0,
  "numPassedTestSuites": 1,
  "numPassedTests": 2,
  "numPendingTestSuites": 0,
  "numPendingTests": 0,
  "numRuntimeErrorTestSuites": 0,
  "numTodoTests": 0,
  "numTotalTestSuites": 1,
  "numTotalTests": 2,
  "openHandles": [],
  "snapshot": {
    "added": 0,
    "didUpdate": false,
    "failure": false,
    "filesAdded": 0,
    "filesRemoved": 0,
    "filesRemovedList": [],
    "filesUnmatched": 0,
    "filesUpdated": 0,
    "matched": 0,
    "total": 0,
    "unchecked": 0,
    "uncheckedKeysByFile": [],
    "unmatched": 0,
    "updated": 0
  },
  "startTime": 1678243830484,
  "success": false,
  "testResults": [
    {
      "leaks": false,
      "numFailingTests": 0,
      "numPassingTests": 2,
      "numPendingTests": 0,
      "numTodoTests": 0,
      "openHandles": [],
      "perfStats": {
        "end": 1678243831136,
        "runtime": 506,
        "slow": false,
        "start": 1678243830630
      },
      "skipped": false,
      "snapshot": {
        "added": 0,
        "fileDeleted": false,
        "matched": 0,
        "unchecked": 0,
        "uncheckedKeys": [],
        "unmatched": 0,
        "updated": 0
      },
      "testFilePath": "/Users/jsonp/Desktop/test/__tests__/sum.test.js",
      "testResults": [
        {
          "ancestorTitles": [
            "addition",
            "positive numbers"
          ],
          "duration": 2,
          "failureDetails": [],
          "failureMessages": [],
          "fullName": "addition positive numbers should add up",
          "invocations": 1,
          "location": null,
          "numPassingAsserts": 1,
          "retryReasons": [],
          "status": "passed",
          "title": "should add up"
        },
        {
          "ancestorTitles": [
            "subtraction",
            "positive numbers"
          ],
          "duration": 0,
          "failureDetails": [],
          "failureMessages": [],
          "fullName": "subtraction positive numbers should subtract",
          "invocations": 1,
          "location": null,
          "numPassingAsserts": 1,
          "retryReasons": [],
          "status": "passed",
          "title": "should subtract"
        }
      ],
      "failureMessage": null
    }
  ],
  "wasInterrupted": false
}```

from jest-junit.

Thanks @palmerj3

From what I understand each test file must contain only one top-level describe() block. Is there any workaround so that I can avoid updating the test file?

from jest-junit.

Sorry there is not

from jest-junit.

"Jest actually considers each test file a suite"
Can you point me to the jest code or documentation where I can check this?

from jest-junit.

Jest passes reporters who listen for the onTestResult event AggregatedResultWithoutCoverageAggregatedResultWithoutCoverage .

This type contains the testResults property of type TestResultTestResult.

Each index in TestResult has a testFilePath and aggregate reporting results such as numFailingTests, numPassingTests, etc which map exactly to Junit TestSuite level reporting.

Hence, Jest treats test files as suites.

I've worked on the reporter system enough to go into more detail if needed but this should suffice.

from jest-junit.

Thanks @palmerj3! If it is Jest that is causing the pain, I guess it would be better if an issue is raised to Jest project to make it easier for reporters to be able treat describe block as test suites. However, I do not know enough to be able to suggest changes in Jest. Would you help raising an issue with Jest, if you agree?

from jest-junit.

I see jest-html-reporter and jest-html-reporters(in particular) are able to display the describe() blocks under the file name as I would expect it to be. But I do not know how they're able to do it. I've updated the repo linked above with these packages for comparison.

jest-html-reporter:

jest-html-reporters:

from jest-junit.