Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Logging Integration Tests for debugging #302

Open
gsps1 opened this issue May 18, 2016 · 0 comments
Open

Improve Logging Integration Tests for debugging #302

gsps1 opened this issue May 18, 2016 · 0 comments

Comments

@gsps1
Copy link
Contributor

gsps1 commented May 18, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant