Proxyman is a handy tool not only for seeing the content of requests/responses, but also for reporting bugs.
Normally, QAs often escalate bugs to developers via tickets. However, this process is often time-consuming and developers still have to reproduce them manually.
Below is the way We use to report bugs and We think it could be more convenient for both devs and QAs
** Please bear in mind that We just made up the bug for demonstration.
1. Spot the bug:
Imagine that We was testing the Unsplash app on my iPhone and somehow We could not see any images. When We checked the response, there was an unexpected error saying that my access token was invalid. This seemed like a bug and We wanted to escalate to developers for further investigation.
So what is the best way to report this bug?
2. Export “flow”
There is a handy feature named “Export” offered by Proxyman, which allows me to export current flows to re-open them in the future. You can simply “Right click” on current URL -> Select “Export this flow” -> and “Save”
Right click and select “Export this Flow”
Decide where to “Save” the flow
Then here is the exported file
3. Attach the exported flow into Jira, Trello, Github,…
This exported file is one of the easiest ways to communicate with developers. You could attach it into a ticket on Jira, Trello, or Github then escalate to developers. Below is an example of the ticket that We report to developers (all information are faked)
4. Open an exported “flow”
As soon as the assigned developer opens the file, he would see the same flow as mine. In other words, this man could investigate the bug immediately based on the content of the Request/ Response without manually reproducing the bug on his device (We found it pretty cool xD)
5. Edit and Repeat
Another feature that might be useful is “Edit and Repeat” . By “Right click” on current flow -> Select “Edit and Repeat” you could “Edit” the Header/Body of a Request and “Re-send” it…
Right click and select “Edit and Repeat”
You can Edit the Header/ Body of a request and Re-send
… it might be helpful for developers investigating the bug.
So that’s all about the steps that We use for reporting bugs. How about you? Which is your favorite tools to communicate with developers? Please feel free to share with me your ideas (and also your comments so that We could make better reviews).
In case you’re interested in Proxyman, you can download the latest version here.
Happy debugging! :)