jam-cloud/agent-tasks/web-test-suite-revival/failed-tests-burn-down/progress.md

Progress

Goal

Burn down failures listed in web/failed_tests.txt by running each test individually and fixing failures.

Status

• Create tracker
• Run each listed test individually
• Fix failing tests incrementally
• Re-run fixed tests to confirm

Notes

• Started: 2026-02-14
• Confirmed green (run individually) for spec/features/accept_friend_request_dialog_spec.rb examples listed in failed_tests.txt (:22, :38, :52, :66, :82, :93) after updating spec launch path/assertions.
• Attempted next block (account_affiliate_spec and account_payment_spec) still failing due account screens not rendering from hash navigation in current client state.
• Verified websocket gateway can be started locally with:
  • cd websocket-gateway && JAMENV=test bundle exec bin/websocket_gateway.sh
  • server logs show bind on 0.0.0.0:6759.
• Even with gateway running, current failures in account feature specs remain at account screen selectors not present (div.account-mid.identity, .account-mid.affiliate ...).
• 2026-02-14 continued burn-down from top of failed_tests.txt using individual invocations (primarily web/bin/rspec-fast).
• Confirmed green (individually):
  • spec/controllers/api_corporate_controller_spec.rb:11
  • spec/controllers/api_jam_track_mixdowns_controller_spec.rb:{19,43,65,81,90,108,123}
  • spec/controllers/api_search_controller_spec.rb:18
  • spec/controllers/api_users_controller_spec.rb:{24,37,147,161,197,221,290,302,311}
  • spec/controllers/share_tokens_controller_spec.rb:10
  • spec/features/accept_friend_request_dialog_spec block remains green.
• Reconfirmed blockers:
  • Account-related feature setup still fails to reach visible account screen selectors (div.account-mid.identity / .account-mid.affiliate ...) and cascades into account_spec, account_payment_spec, account_affiliate_spec.
  • activate_account_spec still failing for not-logged-in flows (:20, :52) while logged-in flows pass.
• Observed repeated .no-websocket-connection markup in capybara snapshots despite websocket-gateway listener on :6759; this likely contributes to account-feature instability.