Skip to content
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

Have integration tests run their own server on a port other than 3000 #2714

Closed
Tyriar opened this issue Feb 12, 2020 · 0 comments · Fixed by #3298
Closed

Have integration tests run their own server on a port other than 3000 #2714

Tyriar opened this issue Feb 12, 2020 · 0 comments · Fixed by #3298
Labels
help wanted type/debt Technical debt that could slow us down in the long run

Comments

@Tyriar
Copy link
Member

Tyriar commented Feb 12, 2020

Right now the tests rely on the demo being up and running on port 3000, it would be nicer if instead the tests set up their own server on a different port and tore it down after running the tests.

@Tyriar Tyriar added help wanted type/debt Technical debt that could slow us down in the long run labels Feb 12, 2020
bmf-ribeiro pushed a commit to bmf-ribeiro/xterm.js that referenced this issue Apr 6, 2021
 - Use port 3001 instead of  300 to not conflict with the demo
Tyriar added a commit that referenced this issue Apr 6, 2021
…ntegration-tests

Fix #2714 - Start demo server before running integration tests
This was referenced May 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted type/debt Technical debt that could slow us down in the long run
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant