riok / Kreya

Kreya is a GUI client for gRPC and REST APIs with innovative features for environments, authorizations and more.
https://kreya.app
279 stars 5 forks source link

See "traces" in collections and some other ideas for Traces #211

Open AFract opened 3 months ago

AFract commented 3 months ago

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 !

ni507 commented 3 months ago

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.

AFract commented 3 months ago

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.

ni507 commented 3 months ago

Okay, got it.

We will add this to the backlog as well and see what we can do.