Right now, when a integration test throws an exception or don't pass, we have a huge stack trace instead of a concise error message. In the example below, the error was that there was happening a redirect instead of a status 200:
[info] Home page should
[info] + be delivered correctly
[info] + should contain a list of most starred repo when user is not connected
[info] + should contain a list of the user's starred repo when he is connected
[error] a.a.OneForOneStrategy - Unable to provision, see the following errors:
1) Error injecting constructor, java.lang.RuntimeException: There is no started application
at models.daos.drivers.Neo4j.(Neo4j.scala:21)
...
We should try to avoid throwing unknown exceptions and try to manage them (wrap them) to create more readable errors when a test fails
Right now, when a integration test throws an exception or don't pass, we have a huge stack trace instead of a concise error message. In the example below, the error was that there was happening a redirect instead of a status 200:
We should try to avoid throwing unknown exceptions and try to manage them (wrap them) to create more readable errors when a test fails