[GH-ISSUE #2346] [Bug] Integration tests often fail #995

Closed
opened 2026-03-23 20:44:11 +00:00 by mirror · 4 comments
Owner

Originally created by @richardshiue on GitHub (Apr 25, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/2346

Originally assigned to: @a-wallen on GitHub.

Bug Description

The empty document and typing /grid to create a new grid integration test often fails during GitHub pull CI checks, even though the pr didn't have such changes and the error cannot be reproduced manually outside of testing.

Tests on a workspace with only an empty document /grid shortcut creates a new grid and view of the grid (failed)

  The following TestFailure was thrown running a test:
  Expected: at least 2 matching nodes in the widget tree
    Actual: _WidgetTypeFinder:<zero widgets with type "SelectionMenuItemWidget" (ignoring offstage
  widgets)>
     Which: means none were found but some were expected

How to Reproduce

Make a flutter-related pr and observe that the integration test fails.

Expected Behavior

The test shouldn't fail so often.

Operating System

CI ubuntu-latest

AppFlowy Version(s)

0.1.3

Screenshots

No response

Additional Context

No response

Originally created by @richardshiue on GitHub (Apr 25, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/2346 Originally assigned to: @a-wallen on GitHub. ### Bug Description The empty document and typing `/grid` to create a new grid integration test often fails during GitHub pull CI checks, even though the pr didn't have such changes and the error cannot be reproduced manually outside of testing. ``` Tests on a workspace with only an empty document /grid shortcut creates a new grid and view of the grid (failed) The following TestFailure was thrown running a test: Expected: at least 2 matching nodes in the widget tree Actual: _WidgetTypeFinder:<zero widgets with type "SelectionMenuItemWidget" (ignoring offstage widgets)> Which: means none were found but some were expected ``` ### How to Reproduce Make a flutter-related pr and observe that the integration test fails. ### Expected Behavior The test shouldn't fail so often. ### Operating System CI ubuntu-latest ### AppFlowy Version(s) 0.1.3 ### Screenshots _No response_ ### Additional Context _No response_
mirror 2026-03-23 20:44:11 +00:00
Author
Owner

@a-wallen commented on GitHub (Apr 27, 2023):

Thanks for opening this issue. We are still recovering from the upgrade to flutter 3.7.5, which disabled OpenGL support and caused our integration tests on macOS to fail. We are now running the integration tests on Linux, but I think some race condition causes this issue to happen while all the tests in CI are running.

Aside, macos (build) also flakes. That needs to be addressed after this is addressed too.

<!-- gh-comment-id:1526617947 --> @a-wallen commented on GitHub (Apr 27, 2023): Thanks for opening this issue. We are still recovering from the upgrade to flutter 3.7.5, which disabled OpenGL support and caused our integration tests on macOS to fail. We are now running the integration tests on Linux, but I think some race condition causes this issue to happen while all the tests in CI are running. Aside, `macos (build)` also flakes. That needs to be addressed after this is addressed too.
Author
Owner

@a-wallen commented on GitHub (May 26, 2023):

https://github.com/AppFlowy-IO/AppFlowy/pull/2622 fixes hard failure in CI for open_ai_smart_menu_test

<!-- gh-comment-id:1563740506 --> @a-wallen commented on GitHub (May 26, 2023): https://github.com/AppFlowy-IO/AppFlowy/pull/2622 fixes hard failure in CI for `open_ai_smart_menu_test`
Author
Owner

@a-wallen commented on GitHub (May 26, 2023):

It looks like https://github.com/AppFlowy-IO/AppFlowy/pull/2621 is solving the broken tests in Flutter-CI for Windows. The next step is solving the errors with pumpAndSettle awaiting for an infinite amount of time because of the circular progress indicator.

<!-- gh-comment-id:1563741146 --> @a-wallen commented on GitHub (May 26, 2023): It looks like https://github.com/AppFlowy-IO/AppFlowy/pull/2621 is solving the broken tests in `Flutter-CI` for Windows. The next step is solving the errors with `pumpAndSettle` awaiting for an infinite amount of time because of the circular progress indicator.
Author
Owner

@Xazin commented on GitHub (Oct 8, 2024):

Closing this for now as we don't have this issue and it's become a bit old 👍 We can revisit if it turns out to be a problem later.

<!-- gh-comment-id:2400241363 --> @Xazin commented on GitHub (Oct 8, 2024): Closing this for now as we don't have this issue and it's become a bit old 👍 We can revisit if it turns out to be a problem later.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#995
No description provided.