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

Make it easier to test "Overriding API Responses" feature #1597

Open
sachinjain024 opened this issue Apr 15, 2024 · 1 comment
Open

Make it easier to test "Overriding API Responses" feature #1597

sachinjain024 opened this issue Apr 15, 2024 · 1 comment
Assignees
Labels

Comments

@sachinjain024
Copy link
Contributor

Override API Response is a very handy feature for frontend developers to unblock themselves from backend developers, simulate API errors, override configs, test negative cases, etc. but the responses overridden by Requestly aren't captured in Chrome Devtools so it always creates confusion for the end users whether the rule has applied or not.

Here are a few changes we are doing to improve the overall experience of testing a rule.

  1. When the user saves the rule for the first time, give the visibility to testing feature
  2. Auto-Save sessions when a user comes back to the rule editor, the user can view and delete the session.
  3. Remove Execution Logs
  4. Show a widget on the page whenever a rule is applied and by default keep it on for Script Rule, Response Rule and let user configure for other rule types.
@sachinjain024
Copy link
Contributor Author

sachinjain024 commented Apr 15, 2024

Here's a demo video of the implicit workflow of Testing the Rule

Screen.Recording.2024-04-12.at.8.06.07.PM.mov

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

No branches or pull requests

1 participant