-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat: Add unit tests for firestore feature initialization #8996
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Adds unit tests for the functions in `src/init/features/firestore`. This includes tests for: - `askQuestions` and `actuate` in `index.ts` - `initRules` and `getDefaultRules` in `rules.ts` - `initIndexes` in `indexes.ts`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @joehan, 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 introduces comprehensive unit tests for the Firestore feature initialization logic. The tests cover the core functions responsible for asking user questions, actuating file writes, and initializing Firestore rules and indexes, ensuring the robustness and correctness of the setup process.
Highlights
- Core Initialization Logic Tested: New unit tests have been added for "askQuestions" and "actuate" functions within src/init/features/firestore/index.ts, verifying user interaction and file writing behavior.
- Firestore Rules Initialization Tested: Unit tests for "initRules" and "getDefaultRules" in src/init/features/firestore/rules.ts ensure the correct generation and handling of Firestore security rules.
- Firestore Indexes Initialization Tested: The "initIndexes" function in src/init/features/firestore/indexes.ts now has dedicated unit tests, covering the process of prompting for and writing Firestore index configurations.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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
-
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. ↩
There was a problem hiding this 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 adds unit tests for the Firestore feature initialization, which is a great addition for improving code quality and stability. The tests are generally well-structured. I've identified a non-deterministic test that relies on the current system time, which could lead to flaky test runs. I've provided a suggestion to make it deterministic. Additionally, I've included a couple of minor suggestions to improve test clarity and remove unused code.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Description
From Jules:
Adds unit tests for the functions in
src/init/features/firestore
. This includes tests for:askQuestions
andactuate
inindex.ts
initRules
andgetDefaultRules
inrules.ts
initIndexes
inindexes.ts