-
Notifications
You must be signed in to change notification settings - Fork 69
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
Update permissions settings and project names for E2E test setup #10315
base: develop
Are you sure you want to change the base?
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.28 MB ℹ️ View Unchanged
|
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.
@dmvrtx Thanks for working on this. The changes makes sense, however I have added some suggestions.
tests/e2e/env/setup.sh
Outdated
@@ -67,27 +84,29 @@ if [[ "$E2E_USE_LOCAL_SERVER" != false ]]; then | |||
echo "Secrets created" | |||
|
|||
step "Starting SERVER containers" | |||
redirect_output docker compose -f docker-compose.yml -f docker-compose.e2e.yml up --build --force-recreate -d | |||
redirect_output docker compose -p transact-platform-server-e2e -f docker-compose.yml -f docker-compose.e2e.yml up --build --force-recreate -d |
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.
Specifying the project name is not required. Instead, we can rename the dependency directory for transact-platform-server
to transact-platform-server-e2e
. Same for dec tools directory.
Since docker picks up the immediate parent directory as project name, transact-platform-server-e2e
will be picked as the name automatically and we don't need to specify it everywhere. Also we don't need to specify it using the COMPOSE_PROJECT_NAME
env variable.
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.
List of changes to be done in this approach.
On env/shared.sh
:
- Replace
export SERVER_PATH="$E2E_ROOT/deps/transact-platform-server"
withexport SERVER_PATH="$E2E_ROOT/deps/transact-platform-server-e2e"
- Replace
export DEV_TOOLS_DIR="wcp-dev-tools"
withexport DEV_TOOLS_DIR="wcp-dev-tools-e2e"
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.
Implemented this great suggestion in 81cfb99
tests/e2e/env/setup.sh
Outdated
@@ -67,27 +84,29 @@ if [[ "$E2E_USE_LOCAL_SERVER" != false ]]; then | |||
echo "Secrets created" | |||
|
|||
step "Starting SERVER containers" | |||
redirect_output docker compose -f docker-compose.yml -f docker-compose.e2e.yml up --build --force-recreate -d | |||
redirect_output docker compose -p transact-platform-server-e2e -f docker-compose.yml -f docker-compose.e2e.yml up --build --force-recreate -d |
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.
List of changes to be done in this approach.
On env/shared.sh
:
- Replace
export SERVER_PATH="$E2E_ROOT/deps/transact-platform-server"
withexport SERVER_PATH="$E2E_ROOT/deps/transact-platform-server-e2e"
- Replace
export DEV_TOOLS_DIR="wcp-dev-tools"
withexport DEV_TOOLS_DIR="wcp-dev-tools-e2e"
Changes proposed in this Pull Request
docker compose
doesn't override containers and networks.Testing instructions
npm run test:e2e-reset
to clean-up E2E tests configuration. Ensure thattests/e2e/deps
path doesn't contain checked out repositories.npm run test:e2e-setup
. Consult with the documentation about the necessary configuration settings if you haven't done it before.npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge