refactor: add configurable result options for ExecuteSql tests#2271
Conversation
Summary of ChangesHello @duwenxin99, 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 refactors the Highlights
🧠 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 AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces configurable expected results for ExecuteSql tests, specifically for CREATE, DROP, and empty SELECT statements. The implementation correctly uses the functional options pattern, which is consistent with the existing testing framework. The changes are clear, well-structured, and improve the flexibility of the test suite, allowing for better validation against different SQL sources. The new options have sensible defaults, ensuring backward compatibility with existing tests. Overall, this is a solid refactoring that enhances the test infrastructure.
…eapis#2271) Adds WithExecuteCreateWant, WithExecuteDropWant, and WithExecuteSelectEmptyWant to RunExecuteSqlToolInvokeTest to allow sources like Snowflake to validate specific DDL/DML status responses instead of defaulting to null.
…eapis#2271) Adds WithExecuteCreateWant, WithExecuteDropWant, and WithExecuteSelectEmptyWant to RunExecuteSqlToolInvokeTest to allow sources like Snowflake to validate specific DDL/DML status responses instead of defaulting to null.
…eapis#2271) Adds WithExecuteCreateWant, WithExecuteDropWant, and WithExecuteSelectEmptyWant to RunExecuteSqlToolInvokeTest to allow sources like Snowflake to validate specific DDL/DML status responses instead of defaulting to null.
…eapis#2271) Adds WithExecuteCreateWant, WithExecuteDropWant, and WithExecuteSelectEmptyWant to RunExecuteSqlToolInvokeTest to allow sources like Snowflake to validate specific DDL/DML status responses instead of defaulting to null.
…eapis#2271) Adds WithExecuteCreateWant, WithExecuteDropWant, and WithExecuteSelectEmptyWant to RunExecuteSqlToolInvokeTest to allow sources like Snowflake to validate specific DDL/DML status responses instead of defaulting to null.
Adds WithExecuteCreateWant, WithExecuteDropWant, and WithExecuteSelectEmptyWant to RunExecuteSqlToolInvokeTest to allow sources like Snowflake to validate specific DDL/DML status responses instead of defaulting to null.