automate version validation with prod test suite#8015
automate version validation with prod test suite#8015MaesterChestnut wants to merge 3 commits intomainfrom
Conversation
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. |
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
|
|
||
| integrationTestImplementation(gradleApi()) | ||
| integrationTestImplementation(gradleTestKit()) | ||
| integrationTestImplementation(sourceSets.main.output) |
There was a problem hiding this comment.
Curious: Why is this needed? Is this about VersionUtils?
There was a problem hiding this comment.
Hmm. Being in src/main/ means that this code ends up in the "production" jar, even though it is only used for tests. I wonder if there is a better location for test infrastructure code.
2 participants
No description provided.