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
Feature/439767 - Configure e2e tests for next.js. #523
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
44113ec
next.js e2e tests initial approach
sc-olexandrtroyanovskyy 48f35ce
Timeouts were added for 3 tests for the disconnected mode. Port confi…
sc-olexandrtroyanovskyy 8320da3
comment update
sc-olexandrtroyanovskyy ab4984f
Merge branch 'dev' into feature/439767
sc-olexandrtroyanovskyy 43a87ee
Minor updates
sc-olexandrtroyanovskyy a9fbc0e
Implementing updates according to PR reivew.
sc-olexandrtroyanovskyy File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Next.js CLI supports a port parameter for the
dev
andstart
commands, which should be able to read an env variable. What if you change the Next.js sample app's "next:dev" to:It seems to use 3000 by default if
PORT
isn't defined (which is what we'd want), but should pick up our e2e setting I think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ambrauer If you use
cross-env
it will not pick up PORT env variable, I tried to do it (if you useappmodes.js
script).In case If I use
cross-env-shell NODE_OPTIONS='--inspect' next dev --port $PORT
it will work only if $PORT is defined, if this variable is not provided, it will throw error:UnhandledPromiseRejectionWarning: Error: Option requires argument: --port
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sc-illiakovalenko That's a bummer. I attempted to use a fork of
cross-env
which adds default value functionality. That solved the "option requires argument" error, however didn't pick up the port supplied byappmodes.js
.I suppose the other option would be to rewrite
appmodes.js
to fire up and test each app sequentially - avoiding any port conflicts - but that's beyond the scope of this task.