Project

General

Profile

Actions

Bug #21600

closed

Banner tests failing

Added by Lisa Knox about 2 months ago. Updated 9 days ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Workbench2
Story points:
-
Release:
Release relationship:
Auto

Description

developer-run-tests-services-workbench2: #557 /consoleFull

tests failing on main


Subtasks 1 (1 open0 closed)

Task #21605: ReviewIn Progress03/18/2024Actions
Actions #1

Updated by Lisa Knox about 2 months ago

  • Category set to Workbench2
Actions #2

Updated by Tom Clegg about 2 months ago

  • Category changed from Workbench2 to Workbench2
  • Project changed from 53 to Arvados
Actions #3

Updated by Lisa Knox about 2 months ago

developer-run-tests-services-workbench2: #582

21600-banner-tests @ a6f2e4ea0bf519125271141c154df7e0a245b082

  • ✅ All agreed upon points are implemented / addressed.
  • ✅ Anything not implemented (discovered or discussed during work) has a follow-up story.
  • ✅ Code is tested and passing, both automated and manual, what manual testing was done is described
  • ✅ Documentation has been updated.
  • ✅ Behaves appropriately at the intended scale (describe intended scale).
  • ✅ Considered backwards and forwards compatibility issues between client and server.
  • ✅ Follows our coding standards and GUI style guidelines.
Notes:
  • I was unable to reproduce the issue locally. I introduced a 1-second sleep in the part of the test that was failing because the normal waitForDom() method wasn't working. The delay passed Jenkins tests 5 times in a row. Recommend merging this fix to clear up the build path and doing more research.
Actions #4

Updated by Peter Amstutz about 2 months ago

  • Target version set to Development 2024-03-27 sprint
Actions #5

Updated by Lisa Knox about 2 months ago

developer-run-tests-services-workbench2: #627

21600-banner-tests @ be3378300d63ce537a5843c5fc23ecd76f4f1f5c

  • ✅ All agreed upon points are implemented / addressed.
  • ✅ Anything not implemented (discovered or discussed during work) has a follow-up story.
  • ✅ Code is tested and passing, both automated and manual, what manual testing was done is described
  • ✅ Documentation has been updated.
  • ✅ Behaves appropriately at the intended scale (describe intended scale).
  • ✅ Considered backwards and forwards compatibility issues between client and server.
  • ✅ Follows our coding standards and GUI style guidelines.
Actions #6

Updated by Lucas Di Pentima about 2 months ago

Just in case it's useful, I've made some improvements on this test suite at 21600-wb2-flaky-banner-tests
Test run: developer-run-tests-services-workbench2: #628

Actions #7

Updated by Lisa Knox about 2 months ago

developer-run-tests-services-workbench2: #630

21600-banner-tests @ aee2fb2b736a714d3c8dc5b4624bff3fae8d7ba4

Notes:
  • Incorporated changes from Lucas to fix the tooltip tests, which were passing but still janky in the previous commit.
Actions #8

Updated by Anonymous about 2 months ago

  • Status changed from In Progress to Resolved
Actions #9

Updated by Peter Amstutz 9 days ago

  • Release set to 70
Actions

Also available in: Atom PDF