You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there are errors in Integration tests, we see the failed tests in the end.
As a next step you can look at the code to where it failed, say assertion for column size failed.
however if you want to see what's the actual request/response and what was different, etc., you would have to look at HTTP requests and responses.
Since we log everything to a same place, its tedious to find the right place in the log, often have to see which app was deployed for that integration test and do a search for that.
ITN logging can improve, one option is, when there are failures, we can also log HTTP request and response as part of the error message. other option is to log tests to separate files.
The text was updated successfully, but these errors were encountered:
When there are errors in Integration tests, we see the failed tests in the end.
As a next step you can look at the code to where it failed, say assertion for column size failed.
however if you want to see what's the actual request/response and what was different, etc., you would have to look at HTTP requests and responses.
Since we log everything to a same place, its tedious to find the right place in the log, often have to see which app was deployed for that integration test and do a search for that.
ITN logging can improve, one option is, when there are failures, we can also log HTTP request and response as part of the error message. other option is to log tests to separate files.
The text was updated successfully, but these errors were encountered: