Reported by:
Oleh B.
Issue:
When a check fails during test session execution, the failure results and error reasons are not displayed in the UI until the page is manually reloaded.
Specifics:
  • Browser: Chrome
  • Timing: Occurs during active test session execution
  • Workaround: Manual page reload reveals the results
Impact:
  • Disrupts debugging workflow
  • Users don't see failures in real-time
  • Have to constantly refresh to check status
  • Poor user experience during test monitoring
Expected Behavior:
  • Check failures should appear immediately when they occur
  • Results and error reasons should be visible without page reload
  • Real-time updates as checks complete (pass or fail)
Technical Analysis:
Likely issues:
  1. WebSocket/polling not updating UI with failure events
  2. Frontend state not refreshing on failure responses
  3. Race condition between check completion and UI update
  4. Browser-specific rendering issue (Chrome)
Testing Needed:
  • Does this occur in other browsers (Firefox, Safari, Edge)?
  • Is it specific to one installation?
  • Does it happen consistently or intermittently?
Priority:
Medium - Affects test monitoring and debugging