-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Storybook: different port for each module #2837
Comments
This fails for me even when not running in parallel.
The next storybook instance picks the next available port e.g |
Indeed, you're right; I assumed it was caused by the |
@FrozenPandaz it feels like a bug to me; am I wrong? |
We are experiencing a similar issue, probably the same. Reproduction can be found here: https://github.com/elisa-dc/test-storybook Steps to reproduce:
credits to @elisa-dc |
@dsebastien @samvloeberghs I was able to find a workaround to run all the e2e tests sequentially using the run-many task: > nx run-many --target=e2e --all It looks like this turns off storybook between test runs, which allows the tests to pass. Unfortunately this does not work with the |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
I have the same problem since 11.2.0 version of @nrwl/cypress |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Prerequisites
Please answer the following questions for yourself before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.
Expected Behavior
It would be nice to be able to run Cypress e2e tests in parallel against different libraries configured with Storybook.
Current Behavior
What is the current behavior?
Errors about ports already being used when executing
npm run affected:e2e -- --headless --base=remotes/origin/master --head=HEAD --parallel
My current workaround is to manually change the port for each project through angular.json and cypress.json so that there are no port conflicts
Apparently, the issue also happens without running in parallel.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
The text was updated successfully, but these errors were encountered: