Skip to content

test: skip system tests requiring public access (#2717)#28

Merged
thiyaguk09 merged 1 commit intothiyaguk09:feat/bucket-encryption-configfrom
googleapis:main
Feb 5, 2026
Merged

test: skip system tests requiring public access (#2717)#28
thiyaguk09 merged 1 commit intothiyaguk09:feat/bucket-encryption-configfrom
googleapis:main

Conversation

@thiyaguk09
Copy link
Owner

Skips tests that attempt to assign public or authenticated user roles to IAM policies. These tests are currently failing with 403 errors due to environment permission restrictions.

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

Description

Please provide a detailed description for the change.
As much as possible, please try to keep changes separate by purpose. For example, try not to make a one-line bug fix in a feature request, or add an irrelevant README change to a bug fix.

Impact

What's the impact of this change?

Testing

Have you added unit and integration tests if necessary?
Were any tests changed? Are any breaking changes necessary?

Additional Information

Any additional details that we should be aware of?

Checklist

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease
  • Appropriate docs were updated
  • Appropriate comments were added, particularly in complex areas or places that require background
  • No new warnings or issues will be generated from this change

Fixes #issue_number_goes_here 🦕

Skips tests that attempt to assign public or authenticated user roles
to IAM policies. These tests are currently failing with 403 errors due
to environment permission restrictions.
@gemini-code-assist
Copy link

Summary of Changes

Hello @thiyaguk09, 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 temporarily disables several system tests that interact with public IAM roles for Google Cloud Storage buckets and files. The tests were consistently failing with 403 permission errors due to limitations in the current testing environment. By skipping these tests, the PR ensures the overall test suite can pass without these known failures, while clearly marking them for future re-evaluation when environment permissions are adjusted.

Highlights

  • Test Skipping: System tests that attempt to assign public or authenticated user roles to IAM policies are now skipped.
  • Error Mitigation: This change addresses recurring 403 errors caused by current environment permission restrictions during these specific tests.
  • Future Re-enablement: Comments have been added to the skipped tests, indicating they should be re-enabled once the test environment supports public IAM roles.

🧠 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
  • samples/system-test/buckets.test.js
    • Skipped the 'should make bucket publicly readable' test due to 403 errors when assigning public IAM roles.
  • samples/system-test/files.test.js
    • Skipped the 'should make a file public' test due to 403 errors when assigning public IAM roles.
  • system-test/storage.ts
    • Skipped tests related to making buckets public, making files public, setting policies with public roles, and respecting predefined ACLs during file copy, all due to 403 errors when assigning public IAM roles.
Activity
  • The author identified system tests failing with 403 errors when attempting to assign public or authenticated user roles to IAM policies.
  • The author implemented it.skip for the affected tests across samples/system-test/buckets.test.js, samples/system-test/files.test.js, and system-test/storage.ts.
  • Comments were added to each skipped test explaining the reason for skipping (environment permission restrictions) and a TODO to re-enable them in the future.
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.

@thiyaguk09 thiyaguk09 self-assigned this Feb 5, 2026
Copy link

@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

This pull request skips several system tests that are failing due to permission restrictions in the test environment. The changes correctly use it.skip to disable the tests and include comments explaining the reason.

My main feedback is on the duplicated comment block across multiple tests in system-test/storage.ts. I've suggested a way to centralize the skip reason to improve maintainability.

Overall, the changes are clear and address the issue described.

Comment on lines +292 to +296
/**
* TODO: Re-enable once the test environment allows public IAM roles.
* Currently disabled to avoid 403 errors when adding 'allUsers' or
* 'allAuthenticatedUsers' permissions.
*/

Choose a reason for hiding this comment

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

medium

This comment block is repeated for several skipped tests in this file. To improve maintainability and reduce duplication, consider defining a constant for the skip reason at a higher scope.

For example:

const PUBLIC_ACCESS_SKIP_REASON = 'Skipping test that requires public IAM roles due to environment restrictions. TODO: Re-enable when permissions are available.';

// ...

// ${PUBLIC_ACCESS_SKIP_REASON}
it.skip('should make a bucket public', async () => {
  // ...
});

This makes it easier to update the reason in one place if needed in the future.

@thiyaguk09 thiyaguk09 merged commit aef4dcd into thiyaguk09:feat/bucket-encryption-config Feb 5, 2026
14 checks passed
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.

1 participant