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
I've been using the jest-tap-reporter to generate TAP reports for my Jest tests. When parsing the TAP results from Jest tests, I noticed that the diag object is missing, which is important for diagnosing test failures. In contrast, when using the tap-parser library to parse TAP results from Node Tap, the diag object is present, providing valuable information about the failure.
Steps to Reproduce:
Run Jest tests with jest-tap-reporter
Parse the TAP results and examine the parsed results.
Expected Behavior:
The parsed TAP results from Jest tests using jest-tap-reporter should include the diag object, just like the results from Node Tap tests.
Actual Behavior:
The diag object is missing from the parsed TAP results generated by jest-tap-reporter.
Additional Information:
Please find the example parsed TAP results for a failed test case below:
Jest TAP Parsed Result:
{ok: false,name: '[FII-OPSU-QA-SEO-0001.98]-Opsfolio Suite page URL: <a href="http://localhost:4321/policies/information-technology-quality-infrastructure/common-user-login-access-policy/"></a> navigation and title check',id: 486,buffered: false,tapError: null,skip: false,todo: false,previous: null,plan: null,diag: null,// Missing 'diag' objecttime: null,fullname: '[FII-OPSU-QA-SEO-0001.98]-Opsfolio Suite page URL: <a href="http://localhost:4321/policies/information-technology-quality-infrastructure/common-user-login-access-policy/"></a> navigation and title check',closingTestPoint: false}
Node Tap Parsed Result:
{ok: false,name: 'Error occurred: Error: page.$eval: Error: failed to find element matching selector ".left-footer"',id: 9,buffered: false,tapError: null,skip: false,todo: false,previous: null,plan: null,diag: {operator: 'fail',at: '<anonymous> (/tests/opsfolio.test.ts:158:9)',stack: 'Error: Error occurred: Error: page.$eval: Error: failed to find element matching selector ".left-footer"\n'+' at Test.assert [as _assert] (/node_modules/tape/lib/test.js:479:48)\n'+' at Test.fail (/node_modules/tape/lib/test.js:573:7)\n'+' at /tests/opsfolio.test.ts:158:9\n'+' at step (/tests/opsfolio.test.ts:33:23)\n'+' at Object.throw (/tests/opsfolio.test.ts:14:53)\n'+' at rejected (/tests/opsfolio.test.ts:6:65)'},time: null,fullname: 'Error occurred: Error: page.$eval: Error: failed to find element matching selector ".left-footer"',closingTestPoint: false}
The text was updated successfully, but these errors were encountered:
I've been using the
jest-tap-reporter
to generate TAP reports for my Jest tests. When parsing the TAP results from Jest tests, I noticed that thediag
object is missing, which is important for diagnosing test failures. In contrast, when using thetap-parser
library to parse TAP results from Node Tap, thediag
object is present, providing valuable information about the failure.Steps to Reproduce:
jest-tap-reporter
Expected Behavior:
The parsed TAP results from Jest tests using
jest-tap-reporter
should include thediag
object, just like the results from Node Tap tests.Actual Behavior:
The
diag
object is missing from the parsed TAP results generated byjest-tap-reporter
.Additional Information:
Please find the example parsed TAP results for a failed test case below:
Jest TAP Parsed Result:
Node Tap Parsed Result:
The text was updated successfully, but these errors were encountered: