[GH-ISSUE #5628] [feature]: in test suites, add a tab Request JSON #2181

Open
opened 2026-03-16 23:29:36 +03:00 by kerem · 2 comments
Owner

Originally created by @JohannesBe on GitHub (Nov 28, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5628

Is there an existing issue for this?

  • I have searched the existing issues

Summary

When you run an extensive test suite and a request fails (let's say request number 7 out of 9), it is hard to know what exactly happened, especially when making use of variables that were set by prior request.

As such, I suggest to add a tab called Request JSON or something similar to the bottom pane when you open a specific request of the test suite.

Related: #5627 , though this one is from a different view (the test view instead of single request view)

Why should this be worked on?

Right now it is really hard to know what exactly was sent over the wire during testing.

Originally created by @JohannesBe on GitHub (Nov 28, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5628 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary When you run an extensive test suite and a request fails (let's say request number 7 out of 9), it is hard to know what exactly happened, especially when making use of variables that were set by prior request. As such, I suggest to add a tab called `Request JSON` or something similar to the bottom pane when you open a specific request of the test suite. Related: #5627 , though this one is from a different view (the test view instead of single request view) ### Why should this be worked on? Right now it is really hard to know what exactly was sent over the wire during testing.
Author
Owner

@Abhishekmishra2808 commented on GitHub (Nov 28, 2025):

@JohannesBe
Hi! I’d like to work on this feature.

My approach:

Add a new Request JSON tab in the test-suite request details panel.
Pass the final resolved request body (after variables/env/scripts) to this tab.
Use the existing JSON viewer component to display it.
Keep the change scoped only to the test-suite request view.

If this looks good, please assign it to me.Then I'll start working on this issue.

<!-- gh-comment-id:3589670372 --> @Abhishekmishra2808 commented on GitHub (Nov 28, 2025): @JohannesBe Hi! I’d like to work on this feature. **My approach:** Add a new Request JSON tab in the test-suite request details panel. Pass the final resolved request body (after variables/env/scripts) to this tab. Use the existing JSON viewer component to display it. Keep the change scoped only to the test-suite request view. If this looks good, please **assign it to me**.Then I'll start working on this issue.
Author
Owner

@JohannesBe commented on GitHub (Dec 1, 2025):

Unfortunately, I cannot assign people, so we'll have to wait for a repo maintainer to do that :)

<!-- gh-comment-id:3595261107 --> @JohannesBe commented on GitHub (Dec 1, 2025): Unfortunately, I cannot assign people, so we'll have to wait for a repo maintainer to do that :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#2181
No description provided.