-
Notifications
You must be signed in to change notification settings - Fork 5
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
See "traces" in collections and some other ideas for Traces #211
Comments
Thank you for your report. You can view the traces and the result for each operation by clicking on the operation in the collection. On the right side all the response details of the operation should be visible. Does this meet your needs? To improve the visibility of the traces, we have added an issue to our backlog. |
Hello, "You can view the traces and the result for each operation by clicking on the operation in the collection. On the right side all the response details of the operation should be visible. Does this meet your needs?" The idea was to have them directly on the "Collection execution result" panel, where currently there's only one tab with the results of all the tests. This way, if operation C reuse some informations from operation A and B that are displayed by Trace() calls, it could be easier to review in one look what was done. edit : I have also updated first post with a request related to test results displaying. |
Okay, got it. We will add this to the backlog as well and see what we can do. |
Hello,
Collections is a great feature, and running/displaying tests results in it is fine.
However, it could also be interesting for a future release :
Additionnally I would also be interested to have some kind of overload for the Trace() method to make them "more visible", when those traces are related to the things I am currently testing. Currently "custom" traces are kinda lost in the "Traces" panel which is cluttered by "technical" traces like Connect / request sent, etc.
Thank you !
The text was updated successfully, but these errors were encountered: