#2865 feat: create test-utils module and refactor test imports by robfrank · Pull Request #2885 · ArcadeData/arcadedb (original) (raw)
Summary of Changes
Hello @robfrank, 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 significantly enhances the consistency and maintainability of the project's test suite by introducing a dedicated test-utils module. This change centralizes common testing infrastructure, reducing redundant dependencies and clarifying the distinction between core server components and test-specific code. The refactoring ensures that test helper classes are sourced from a single, well-defined location, which will simplify future test development and dependency management across various sub-modules.
Highlights
- New Test Utilities Module: A new Maven module,
arcadedb-test-utils, has been created to centralize common test utilities and helpers, promoting better organization and reusability of test code. - Dependency Refactoring: The
arcadedb-servertest dependency has been replaced with the newarcadedb-test-utilsartifact across multiplepom.xmlfiles (console, graphql, gremlin, grpc-client, grpcw, metrics, mongodbw, postgresw, redisw), removing the need for thetest-jartype specification. - Test Import Standardization: All test classes in various modules (console, gremlin, grpc-client, metrics, mongodbw, postgresw, redisw) now import helper utilities from the
com.arcadedb.testpackage instead ofcom.arcadedb.server, ensuring a clearer separation between production and test code. - Server Module Test-Jar Exclusion: The
servermodule'spom.xmlhas been updated to explicitly disabletest-jarpackaging, aligning with the new approach of centralizing test utilities. 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.
- 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. ↩