Skip to content

fix: remove flaky spinner visibility check in E2E tests for improved …#2646

Merged
robfrank merged 1 commit intomainfrom
fix/e2e-studio-failing-tests
Oct 12, 2025
Merged

fix: remove flaky spinner visibility check in E2E tests for improved …#2646
robfrank merged 1 commit intomainfrom
fix/e2e-studio-failing-tests

Conversation

@robfrank
Copy link
Collaborator

This pull request makes small improvements to the end-to-end tests for ArcadeDB Studio, focusing on removing flaky or redundant test verifications.

Testing reliability improvements:

  • In e2e-studio/tests/create-database.spec.ts, removed the check for the login spinner's visibility, which was prone to flakiness when login completed quickly. The test now only waits for the spinner to be hidden and the studio panel to be visible.
  • In e2e-studio/tests/query-beer-database.spec.ts, removed a redundant verification for the graph stats count, relying instead on a more robust check for the displayed text.

@gemini-code-assist
Copy link
Contributor

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 focuses on enhancing the stability and reliability of the end-to-end test suite for ArcadeDB Studio. It achieves this by identifying and removing specific test assertions that were either flaky due to timing issues or redundant, thereby streamlining the tests without compromising their effectiveness. The changes aim to reduce false negatives and improve the overall efficiency of the testing process.

Highlights

  • Improved Login Test Reliability: In e2e-studio/tests/create-database.spec.ts, the test for the login spinner's visibility was removed. This check was prone to flakiness when the login process completed too quickly. The test now robustly waits for the spinner to be hidden and the studio panel to become visible, ensuring a more stable verification of successful login.
  • Removed Redundant Graph Stats Check: In e2e-studio/tests/query-beer-database.spec.ts, a redundant verification for the exact count '10' within the graph statistics was eliminated. The test now relies on a more comprehensive and robust check for the full displayed text 'Displayed 10 vertices and 0 edges', simplifying the test and reducing potential flakiness.
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.

Footnotes

  1. 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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 makes good improvements to the end-to-end tests by removing flaky and redundant assertions, which will improve test suite reliability. The changes in both create-database.spec.ts and query-beer-database.spec.ts are positive. I've added one suggestion to create-database.spec.ts to consider refactoring duplicated login logic into a shared helper function to further improve maintainability. Overall, this is a solid contribution to improving test quality.

@codacy-production
Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (0fec242) 73027 46273 63.36%
Head commit (9b1693f) 73027 (+0) 46270 (-3) 63.36% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#2646) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

@robfrank robfrank merged commit a675f2b into main Oct 12, 2025
20 of 22 checks passed
@robfrank robfrank deleted the fix/e2e-studio-failing-tests branch October 12, 2025 07:43
robfrank added a commit that referenced this pull request Nov 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant