Skip to content

[ECP-9912] Configure NOK currency for E2E tests#3256

Merged
candemiralp merged 2 commits intomainfrom
ECP-9912
Feb 23, 2026
Merged

[ECP-9912] Configure NOK currency for E2E tests#3256
candemiralp merged 2 commits intomainfrom
ECP-9912

Conversation

@candemiralp
Copy link
Contributor

Description

This configuration change is required to perform E2E tests for Vipps payment method. Please see the test PR.

@candemiralp candemiralp requested a review from a team as a code owner February 23, 2026 10:19
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @candemiralp, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new Makefile target to streamline the setup process for End-to-End tests, particularly for the Vipps payment method. It configures the Magento environment to allow Norwegian Krone (NOK) currency and sets an exchange rate from EUR to NOK, which is crucial for testing specific payment flows.

Highlights

  • E2E Test Setup: A new setup-e2e target was added to the .github/Makefile to configure the environment for End-to-End tests, specifically enabling NOK currency and setting an exchange rate.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • .github/Makefile
    • Added a new setup-e2e target for E2E test configuration.
    • Configured Magento to allow USD, EUR, and NOK currencies.
    • Inserted or updated an exchange rate for EUR to NOK in the database.
    • Included a command to flush the Magento cache after configuration.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/e2e-test.yml
Activity
  • No activity (comments, reviews, progress) was found in the provided context.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request introduces a new setup-e2e target in the Makefile to configure NOK currency for E2E tests. This includes setting allowed currencies, inserting a currency rate into the database, and flushing the cache. The changes are straightforward and address the stated objective.

Comment on lines +87 to +88
mysql -h "$$DB_SERVER" -P "$$DB_PORT" -u "$$DB_USER" -p"$$DB_PASSWORD" "$$DB_NAME" -e \
"INSERT INTO $${DB_PREFIX}directory_currency_rate (currency_from, currency_to, rate) VALUES ('EUR', 'NOK', 11) ON DUPLICATE KEY UPDATE rate = VALUES(rate);"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The INSERT ... ON DUPLICATE KEY UPDATE statement is generally good for idempotency. However, directly embedding SQL with string concatenation for DB_PREFIX can be a security risk if DB_PREFIX is user-controlled or not properly sanitized. While DB_PREFIX is likely an internal variable in a Makefile, it's a good practice to be cautious with direct SQL injection possibilities. Consider using a more robust method for database interaction if DB_PREFIX could ever be influenced by external input, or ensure it's strictly controlled.

@candemiralp candemiralp merged commit f4d3128 into main Feb 23, 2026
6 of 7 checks passed
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants