GitRepoControllerTest fails due to 500 Internal Server Error (SZ-28)
rk@tigase.net opened 3 weeks ago

Summary

The unit test class GitRepoControllerTest fails with HTTP 500 errors, likely due to recent changes to the domain model or security configuration.

Details

The following test fails with:

Status expected:<200> but was:<500>

This suggests a controller-level failure — possibly missing mock dependencies, improper JSON payloads, or security config issues affecting endpoint access.

Action Items

  • Revisit the test setup (@WebMvcTest, controller mocks, etc.)
  • Add test logs / diagnostics to pinpoint cause of failure
  • Ensure test payloads match expected DTOs/entities

Priority

Medium – should be fixed before UI integration tests are finalized


  • rk@tigase.net commented 3 weeks ago

    Estimated Time: 2 hours

    • 30m – Investigate root cause using full logs and reproduce failure locally
    • 30m – Revise test class: add missing mocks, imports, or configuration as needed
    • 30m – Rerun and validate test suite, confirm test stability, commit and push fix
    • 30m – Run full regression tests (curl/Ansible) to verify UI-required endpoints
issue 1 of 1
Type
Bug
Priority
Normal
Assignee
Version
none
Sprints
n/a
Customer
n/a
Issue Votes (0)
Watchers (3)
Reference
SZ-28
Please wait...
Page is in error, reload to recover