ci(cloud-sql): skip failing tests

[glasnt]

As noted in #8794, these tests require refactoring.

They are currently failing and is blocking #10129

This PR skips these tests, pending rework.

• I have followed Sample Format Guide
• pom.xml parent set to latest shared-configuration
• Appropriate changes to README are included in PR
• These samples need a new API enabled in testing projects to pass (let us know which ones)
• These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
• Tests pass: mvn clean verify required
• Lint passes: mvn -P lint checkstyle:check required
• Static Analysis: mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
• This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
• This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
• Please merge this PR for me once it is approved

[gemini-code-assist]

Summary of Changes

Hello @glasnt, 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 temporarily disables several failing integration tests across the Cloud SQL Java servlet samples for MySQL, PostgreSQL, and SQL Server. The tests, testGetTemplateData and testServletPost, are currently unstable and require refactoring, as documented in issue #8794. By skipping these tests, the PR unblocks other ongoing development work, specifically issue #10129, while a proper solution for the test failures is being prepared.

Highlights

• Test Skipping: Two specific test methods, testGetTemplateData and testServletPost, in the Cloud SQL servlet samples for MySQL, PostgreSQL, and SQL Server have been marked with @Ignore to prevent them from executing during CI runs.
• Issue Resolution: This change addresses the immediate issue of failing tests that were blocking further development (specifically issue fix(deps): update java #10129), as detailed in https://github.com/GoogleCloudPlatform/java-docs-samples/issues/8794, by temporarily skipping them.

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 skips several failing Cloud SQL servlet tests by using the @Ignore annotation. This is a reasonable approach to unblock the CI pipeline while the tests are being refactored. The changes are clear and directly address the issue. I've added a few suggestions to improve maintainability by using a constant for the issue URL.

[gemini-code-assist]

To improve maintainability and avoid duplicating the issue URL, consider defining it as a private static final String constant. This constant can then be used here and for the other ignored test on line 115.

For example:

private static final String SKIP_FAILING_TESTS_ISSUE = "https://github.com/GoogleCloudPlatform/java-docs-samples/issues/8794";

// ...

@Ignore(SKIP_FAILING_TESTS_ISSUE)

[gemini-code-assist]

To improve maintainability and avoid duplicating the issue URL, consider defining it as a private static final String constant. This constant can then be used here and for the other ignored test on line 116.

For example:

private static final String SKIP_FAILING_TESTS_ISSUE = "https://github.com/GoogleCloudPlatform/java-docs-samples/issues/8794";

// ...

@Ignore(SKIP_FAILING_TESTS_ISSUE)

[gemini-code-assist]

To improve maintainability and avoid duplicating the issue URL, consider defining it as a private static final String constant. This constant can then be used here and for the other ignored test on line 125.

For example:

private static final String SKIP_FAILING_TESTS_ISSUE = "https://github.com/GoogleCloudPlatform/java-docs-samples/issues/8794";

// ...

@Ignore(SKIP_FAILING_TESTS_ISSUE)