Use cases affected by error notification absence:
1) When the current tab is Issues or Analytics, and the new scope arrives, there will be no changes until the response with the new data arrives. That means that due to the potential request timeout, the user will see the "stale" data for the previous scope.
2) When the current tab is not Tests or Errors, and the new scope arrives, the user will be navigated to Issues/Analytics correspondingly with no data displayed until the response comes. The user will see the "stuck" empty/loading screen.
3) During the regular background refresh, there is no indication of a failed request due to timeout or any other error. The user cannot see any recent changes and is unaware of any connection issues with BE.
Use cases affected by error notification absence: 1) When the current tab is Issues or Analytics, and the new scope arrives, there will be no changes until the response with the new data arrives. That means that due to the potential request timeout, the user will see the "stale" data for the previous scope.
2) When the current tab is not Tests or Errors, and the new scope arrives, the user will be navigated to Issues/Analytics correspondingly with no data displayed until the response comes. The user will see the "stuck" empty/loading screen.
3) During the regular background refresh, there is no indication of a failed request due to timeout or any other error. The user cannot see any recent changes and is unaware of any connection issues with BE.