Skip to content

test(core): skip windows quoting integration test when pwsh.exe is not available - #29647

Open
supunyasanthaofficial wants to merge 1 commit into
google-gemini:mainfrom
supunyasanthaofficial:fix/test-pwsh-integration-guard
Open

supunyasanthaofficial wants to merge 1 commit into
google-gemini:mainfrom
supunyasanthaofficial:fix/test-pwsh-integration-guard

Conversation

@supunyasanthaofficial

Copy link
Copy Markdown

Fixes #29646

Summary

Guards shellExecutionService.windows.integration.test.ts so that it is skipped when PowerShell 7 (pwsh.exe) is not available on Windows.

As documented in the test comments, these tests require pwsh.exe to preserve inline double quotes through native executable invocation and fail when routing through Windows PowerShell 5.1.

Using const hasPwsh = isWindows && Boolean(resolveExecutable('pwsh.exe')) ensures that environments without PowerShell 7 installed cleanly skip the suite, avoiding test failures on standard Windows setups while continuing to execute in CI.

@supunyasanthaofficial
supunyasanthaofficial requested a review from a team as a code owner October 6, 2026 04:23
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 improves the stability of the core shell execution integration tests on Windows. By restricting the execution of tests that specifically require PowerShell 7 to environments where it is available, it prevents false negatives in environments relying on Windows PowerShell 5.1.

Highlights

  • Test Reliability: Updated the Windows integration test suite to conditionally skip execution when PowerShell 7 (pwsh.exe) is not detected.
  • Environment Detection: Introduced a check using resolveExecutable to verify the presence of pwsh.exe, ensuring tests only run in environments where they are supported.
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 the 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 counterproductive. 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.

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

@github-actions github-actions Bot added the size/xs An extra small PR label Oct 6, 2026
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown

📊 PR Size: size/XS

  • Lines changed: 4
  • Additions: +3
  • Deletions: -1
  • Files changed: 1

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

Copy link
Copy Markdown
Contributor

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 modifies the Windows integration tests for ShellExecutionService to conditionally skip tests based on the presence of pwsh.exe rather than just checking if the operating system is Windows. It imports resolveExecutable to verify the availability of pwsh.exe and updates the test suite's skip condition accordingly. There are no review comments, and I have no feedback to provide.

@gemini-cli gemini-cli Bot added the area/platform Issues related to Build infra, Release mgmt, Testing, Eval infra, Capacity, Quota mgmt label Oct 6, 2026

This branch has not been deployed

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

Labels

area/platform Issues related to Build infra, Release mgmt, Testing, Eval infra, Capacity, Quota mgmt size/xs An extra small PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(core): shellExecutionService.windows.integration.test.ts fails on Windows environments without PowerShell 7 (pwsh.exe)

1 participant