chore(repo): split slow e2e tests - ng-add, cypress, eslint linter, a…

[rarmatei]

…nd affected-graph

Split the following test suites into smaller, more focused tests:

• ng-add tests (cypress v9/v10, eslint, generate workspace, multiple projects)
• cypress tests (component testing for Angular and Next, e2e execution, app generation)
• eslint linter tests (dependency checks, flat config, linting errors, module boundaries, root configs)
• affected-graph tests (affected star, focus/exclude, html/json output, show projects, git integration)

Fixes CLOUD-3756

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
nx-dev	Ready	Preview	Oct 16, 2025 6:29pm

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 8c1461b

Command	Status	Duration	Result
nx affected --targets=lint,test,test-kt,build,e...	✅ Succeeded	9m 57s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	2m 20s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	3s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	<1s	View ↗
nx documentation	✅ Succeeded	49s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-10-16 17:35:32 UTC

[netlify]

✅ Deploy Preview for nx-docs ready!

Name	Link
🔨 Latest commit	8c1461b
🔍 Latest deploy log	https://app.netlify.com/projects/nx-docs/deploys/68f1290be128af0008a2bfad
😎 Deploy Preview	https://deploy-preview-33012--nx-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[nx-cloud]

Nx Cloud has identified a possible root cause for your failed CI:

The failure is classified as 'flaky_task' because the test suite was split from a large monolithic file into separate files, which changed the test execution context and timing. The specific failing test "should not affect other projects by generating a new project" relies on git state and affected project calculations, which are inherently timing-sensitive in e2e tests.

The actual test logic remains identical to the original implementation - it checks that generating a new library doesn't incorrectly mark previously committed apps as affected. No direct code changes were made to this specific test.

Git-based affected calculations in e2e tests are sensitive to file system operation timing, git index state, and test execution order. By splitting the tests into separate files, the execution context changed, which exposed a race condition or state management issue that wasn't visible in the original monolithic test structure.

The failure shows no signs of network errors, resource exhaustion, or external service issues. Additionally, the 'mcp__utilities__similar_task_failure_outputs' tool returned no output from the master branch, suggesting this test either passes in master or the timing issue is specific to the new isolated execution context.

While one related test in the same file had a fix added ('git add .' before commit in the "should detect changes to implicitly dependant projects" test), the failing test itself was not modified, further indicating the issue stems from test isolation rather than intentional logic changes.

A code change would likely not resolve this issue, so no action was taken.

View in Nx Cloud ↗

_{🎓 To learn more about Self Healing CI, please visit nx.dev}