chore(tests): centralize integration and bdd suites#3064
chore(tests): centralize integration and bdd suites#3064strantalis wants to merge 10 commits intoopentdf:mainfrom
Conversation
Summary of ChangesHello @strantalis, 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 refactors the project's testing infrastructure by centralizing all BDD and integration tests into a dedicated 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. Changelog
Activity
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. Tests once scattered wide, Now gather in one strong fold, Code's truth, clearly shown. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request effectively centralizes the integration and BDD test suites into a root tests module, which is a great step towards decoupling tests from application code and improving the project structure. The changes are consistent across documentation, build files, and source code. I've identified a few minor areas for improvement regarding documentation consistency, test code duplication, and test message clarity. Overall, this is a solid refactoring effort.
58c7072 to
42ac852
Compare
Yeah. Just thinking it would be nice to somehow track this information but we can discuss more. |
marythought
left a comment
There was a problem hiding this comment.
This seems like a big step forward to enabling easier, more flexible code iteration and changes 🙏
Signed-off-by: strantalis <strantalis@virtru.com>
Signed-off-by: strantalis <strantalis@virtru.com>
Signed-off-by: strantalis <strantalis@virtru.com>
Signed-off-by: strantalis <strantalis@virtru.com>
Signed-off-by: strantalis <strantalis@virtru.com>
Signed-off-by: strantalis <strantalis@virtru.com>
Signed-off-by: strantalis <strantalis@virtru.com>
Signed-off-by: strantalis <strantalis@virtru.com>
Signed-off-by: strantalis <strantalis@virtru.com>
841750f
52945d1 to
841750f
Compare
Signed-off-by: strantalis <strantalis@virtru.com>
Summary
Testing