test(e2e): 2.48 E2E tests

[sepidehdehghani992]

running E2E tests for 2.48

Changes

Add a brief description of the changes in this PR to help give the reviewer context.

Deploys

• Deploy to Tamanu Internal

Tests

• Run E2E Tests

Remember to...

• ...write or update tests
• ...add UI screenshots and testing notes to the Linear issue
• ...add any manual upgrade steps to the Linear issue
• ...update the config reference, settings reference, or any relevant runbook(s)
• ...call out additions or changes to config files for the deployment team to take note of

[gemini-code-assist]

Summary of Changes

Hello @sepidehdehghani992, I'm Gemini Code Assist¹! 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 focuses on the preparatory steps for implementing End-to-End testing for the 2.48 release. It includes the addition of a placeholder file, which serves the immediate purpose of enabling the PR to be opened against the release branch, signaling the commencement of E2E test integration.

Highlights

• E2E Test Setup: This pull request is initiated to set up and run End-to-End (E2E) tests specifically for version 2.48 of the application.
• Placeholder File for PR Creation: A new file, E2E.md, was added as a temporary measure to allow the creation of this pull request against the designated release branch.

🧠 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.

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a new markdown file, E2E.md, which appears to be a temporary placeholder. While the intention might be to facilitate E2E testing, including such temporary files in the main codebase, especially in a release branch, can lead to unnecessary clutter and should generally be avoided. It's recommended to remove this file unless it has a permanent, documented purpose.

[gemini-code-assist]

This file, E2E.md, contains content indicating it's a temporary placeholder ("adding random new file so I can make PR against release branch"). Including temporary or placeholder files in the main codebase, especially in a release branch, can lead to unnecessary clutter and confusion. It's recommended to remove this file unless it serves a specific, permanent purpose that is not immediately clear from its content.