Uploaded image for project: 'Apache Fineract'
  1. Apache Fineract
  2. FINERACT-1168

Integration Tests failure due to internal server errors should show server side failure stack trace

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      IT failures like FINERACT-1167, already raised in FINERACT-927, are a PITA (impossible) to debug.

      This is an IT failure due to a #500 means "something internal went wrong on the server" - but we don't know what...

      To know what the problem was, the server should return the exception in the HTTP body of the 500 response. The IT should then capture that, and include it in the JUnit test failure.

      But in production, 500 errors should NOT show the stack trace - that is typically considered a security problem. So we need some env var / sys prop to enable it, just for debugging. Spring Boot probably actually already has some... knob, for this?

      Petri Tuomola thought this may interest you.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                vorburger Michael Vorburger
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: