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
Collections is a great feature, and running/displaying tests results in it is fine.
However, it could also be interesting for a future release :
To see the Traces of calls inside collection result panel,
And eventually to be able to review each request/result of each call inside the collection result without to have to "jump" to them.
Also, seeing which test comes from which operation could be interesting for collections involving many operations.
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:
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.
"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.
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: