Attachments support

[creage]

During our test runs some of tests might produce some artifacts, like screenshots, logs, etc. Since VSTest supports attachments, I wonder if it would be possible to add this feature to this reporter?

Some info about.

[no23reason]

Hi, if Jest "knows" about those attachments, it should be possible to add. If you have the time to make a PR I would be happy to assist you :)

[creage]

Jest might not know, but we can extend it with such feature using custom environment definition, right?

async handleTestEvent(event, state) {
    if (event.name === 'test_done' && event.test.errors.length){
        // generate log for failed test, take screenshots etc.
        // update test result with paths to generated assets
    }       
}

And then later, when generating a TRX, we should extend UnitTestResult node with new entry ResultFiles and list all of assets reported as new ResultFile

<UnitTestResult executionId="6ec687ce-ef77-4663-983e-234cc56bc552" testId="60969a90-a9f5-0eee-9352-958101d70ba3" testName="TypeTextAndSendMessageFromMessageSendMessagePage" computerName="AUTOTEST1" duration="00:01:45.4448068" startTime="2016-08-12T03:27:58.9283005-05:00" endTime="2016-08-12T03:29:44.4760561-05:00" testType="13cdc9d9-ddb5-4fa4-a97d-d965ccfc6d4b" outcome="Passed" testListId="8c84fa94-04c1-424b-9868-57a2d4851a1d" relativeResultsDirectory="6ec687ce-ef77-4663-983e-234cc56bc552">
  <ResultFiles>
    <ResultFile path="OUR_PATH_TO/ASSET.EXT" />
  </ResultFiles>
</UnitTestResult>

Or am I missing the point?

[no23reason]

Hm, that could work, but the API to define this could be tricky to design. Do you have the time to have a try at this?

[daewigma]

I took a try at this, but haven't done full E2E testing, so still in progress: https://github.com/no23reason/jest-trx-results-processor/pull/381

A couple things to note:

• Until Jest 27 is released, Env cannot be in TS. Since this gets compiled, it should be fine, but I wrote/tested in JS, then converted to TS, and did a bit of refactoring from my initial test setup, so it still needs to be tested again.
• I didn't do a full E2E test of this yet, but I did test the individual parts work as expected:
  • the env can set a global function that the test can pass the attachment path to
  • the test can save into a static property for the class
  • the reporter can access that property
• I didn't test the updated TRX generation yet
• I initially was setting it up using the startTime so I could differentiate between multiple runs if retry was set. after looking at the results, it appears only the last run is logged, also it appears that the start time /duration for the individual runs might be based off the overall suite start time, and average duration * testIndex, so this is likely ineffective