Open moxaj opened 1 week ago
If I run an e2e test in our angular monorepo for application A, then try to run it for application B, all the tests for B fail, because app A is still running, and nx is running B's test against A.
"Reusing the server already running on http://localhost:4200"
Also, since the process is still alive after A's tests, I explicitly have to serve applications on a port other than the default 4200.
I would expect the dev server to be shut down after each e2e test.
No response
Node : 20.14.0 OS : win32-x64 npm : 10.2.3 nx : 18.3.1 @nx/js : 18.3.1 @nx/jest : 18.3.1 @nx/linter : 18.3.1 @nx/eslint : 18.3.1 @nx/workspace : 18.3.1 @nx/angular : 18.3.1 @nx/cypress : 18.3.1 @nx/devkit : 18.3.1 @nx/eslint-plugin : 18.3.1 @nrwl/tao : 18.3.1 @nx/web : 18.3.1 @nx/webpack : 18.3.1 typescript : 5.4.5 --------------------------------------- Registered Plugins: @nx/eslint/plugin @nx/jest/plugin @nx/cypress/plugin --------------------------------------- Community plugins: @fundamental-ngx/cdk : 0.48.4 @fundamental-ngx/core : 0.48.4
Also having this problem on windows and mac
Current Behavior
If I run an e2e test in our angular monorepo for application A, then try to run it for application B, all the tests for B fail, because app A is still running, and nx is running B's test against A.
"Reusing the server already running on http://localhost:4200"
Also, since the process is still alive after A's tests, I explicitly have to serve applications on a port other than the default 4200.
Expected Behavior
I would expect the dev server to be shut down after each e2e test.
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response