fix(testing): infer correct file output paths for atomized targets

[jaysoo]

There is a bug when outputFile is specified in playright.config.ts, and atomizer is enabled via ciTargetName, then the path of the output file is wrong.

For example, if you have this reporters entry:

reporter: [
  [
    'junit',
    {
      outputFile: 'dist/report.xml',
    },
  ],
],

Then the atomized output file would be something like dist/report.xml/example-spec-ts, where report.xml is a directory. The correct output file should be dist/example-spec-ts/report.xml to avoid conflict with the non-atomized output of dist/report.xml.

Current Behavior

If you run nx e2e proj then nx e2e-ci proj then you can run into an issue where report.xml (or whatever the file name is) is a directory in the cache, but it is a file currently -- or vice versa. This happens due to the bug described above.

Expected Behavior

The outputFile should never cause a conflict where a path should be a directory but is currently a file, or vice versa.

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Jan 27, 2025 8:38pm

[nx-cloud]

View your CI Pipeline Execution ↗ for commit b497996.

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	✅ Succeeded	29m 10s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	1m 6s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	1s	View ↗
nx-cloud record -- nx format:check --base=82c4e...	✅ Succeeded	23s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	22s	View ↗
nx documentation --no-dte	✅ Succeeded	44s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-01-27 21:10:52 UTC

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.