Bug #18769
closed
Test & confirm no stale data or flickering during data table refreshes
Description
#16951 describes how some tests that refresh the data table have been using workarounds due to stale data being present in the table.
Also, after implementation of #18207 I had these comments:
I played with ce8i5 cluster a bit.
- Regular navigation works fine under "Projects" seems to mostly work fine. On click it clears the table, and loads the contents when ready as expected.
Here are the issues I'm seeing:
- Hitting the refresh button on a project causes it to load twice resulting in a flicker (it clears the contents, the contents show up, then it clears them again, then the content shows up a 2nd time).
- Navigating to a collection, then navigating back to the parent project or using the browser back button still seems to be showing old results as well as flickering:
- It displays the project view with the old project contents
- It clears the contents and shows the loading graphic
- Then it shows the newly loaded contents
- I went into "Shared with me" and clicked on a project. It showed the old contents, then the loading graphic, then the new contents.
Confirm that these issues are fixed, and remove workarounds from the Cypress tests.
Updated by Peter Amstutz almost 3 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz almost 3 years ago
- Related to Bug #16951: Can refresh listing when opening context menu, resulting in wrong item being operated on. added
Updated by Peter Amstutz almost 3 years ago
- Related to Bug #18207: Workbench2 is not clearing the project content when switching added
Updated by Peter Amstutz almost 3 years ago
- Related to Bug #18661: Refresh Button makes the project's listing to flicker while it loads 2 times in a row added
Updated by Lucas Di Pentima almost 3 years ago
I haven't found any use of {force: true} on project listing cypress tests. I did found some on the collections tests so I branched off from #18315 changes and removed those at arvados-workbench2|58820ac (branch 18769-cypress-click-force-removal).
Did a test run (developer-tests-workbench2: #596 ) that failed with the expected errors, so they're still valid for the collection panel's file browser.
Updated by Lucas Di Pentima almost 3 years ago
Disables "actionability checks" on the click() action: https://docs.cypress.io/guides/core-concepts/interacting-with-elements#Actionability -- so, using {force:true} is not recommended.
Updated by Lucas Di Pentima almost 3 years ago
Created #18787 to handle the file browser issue.
Updated by Lucas Di Pentima almost 3 years ago
- Related to Bug #18787: Collection's file browser re-rendering issues added
Updated by Peter Amstutz almost 3 years ago
I went through the flickering issues I had seen before and they seem to all be fixed, thanks!
Updated by Peter Amstutz almost 3 years ago
Lucas Di Pentima wrote:
I haven't found any use of
{force: true}on project listing cypress tests. I did found some on the collections tests so I branched off from #18315 changes and removed those at arvados-workbench2|58820ac (branch18769-cypress-click-force-removal).Did a test run (developer-tests-workbench2: #596
) that failed with the expected errors, so they're still valid for the collection panel's file browser.
Does this pass without the file browser part, if so it can be merged?
Updated by Peter Amstutz almost 3 years ago
integration/favorites.spec.js:67: cy.get('[data-cy=collection-files-panel]').find('input[type=checkbox]').click({ force: true });
Updated by Lucas Di Pentima almost 3 years ago
Rebased branch 18769-cypress-click-force-removal with just the favorites test fixed at arvados-workbench2|05fb88d.
Test run: developer-tests-workbench2: #605
Updated by Lucas Di Pentima almost 3 years ago
Peter Amstutz wrote:
integration/favorites.spec.js:67: cy.get('[data-cy=collection-files-panel]').find('input[type=checkbox]').click({ force: true });
Ok, even though the .click() is made on the file browser, it seems that wasn't needed. But if you prefer to be on the safe side and avoid a flaky test I think we could just ignore this branch.
Updated by Lucas Di Pentima almost 3 years ago
- Target version changed from 2022-03-02 sprint to 2022-03-16 sprint
Updated by Peter Amstutz almost 3 years ago
- Status changed from In Progress to Resolved