Have something to say?

Tell us how we could make the product more useful to you.

Bug in downloading responses

Hi, I’m downloading a webm file from my backend via e.g. GET /interactions/1234/recordings/5678 It shows me in the preview window some byte code, so it can succesfully fetch the data. Then I’m clicking on β€œDownload Response” button. It suggests the correct name and file type β€œget_recording.webm” which I’m storing on disks. macOS shows me that the file file has a proper size of e.g. 12.4 MB, when I’m trying to play this recording it tells me that the file is corrupted. Postman and curl can successfully fetch and save this file so there is no problem with the file, but the β€œsave” functionallity with Testfully seems to have a problem with this kind of file type

Philip 2 months ago

Ability to Share Collections with Team Members

I’d like to request a feature that would allow users to share collections (including requests, environments, and tests) with other team members within the same workspace. This would greatly improve collaboration by ensuring everyone is working with the same set of resources without needing to duplicate or manually export/import them. Here are a few ideas for how this could work: Allow assigning view/edit permissions to shared collections. Enable real-time syncing so updates are reflected across users. Optionally integrate with team roles or folders for better organization. This feature would be especially helpful for teams working on large-scale APIs or projects requiring consistent testing across multiple contributors.

Abubakar Usman over 1 year ago

setNextRequest function not working

The setNextRequest() function doesn’t seem to be working. The documentation doesn’t explain how to use it (args etc), but the changelog says to use the request name, or null. I’ve tried calling it using a request name which didn’t respond. I’ve tried using the name hard coded, and pulled using pm.info.requestName. No response either time. I’ve also tried calling it with null to prevent the next step running, and again it does nothing. I’ve tried calling it using $.setNextRequest and using postman.setNextRequest, again no response. I contacted your technical support chat which said you usually reply in a few minutes, but so far I’ve had no response in nearly 24 hours. Full after script, it’s a simple UUID format validation and then polling an endpoint until a task is complete. The function is used to set the same request as the next one, so it calls itself until complete or retry count exceeded: ::javascript pm.test("Validate id UUID format", function() { const response = pm.response.json(); const uuidRegex = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i; pm.expect(response).to.have.property('id'); pm.expect(response.id).to.match(uuidRegex); }); const response = pm.response.json(); if (response.status === "in_progress") { console.log("Task still in progress, sleeping 3 seconds before retry"); // Add a counter to prevent infinite loops const retryCount = parseInt(pm.environment.get("forensic_retry_count")); console.log("Retries:", retryCount) pm.environment.set("forensic_retry_count", retryCount + 1); // Maximum retries (adjust as needed) const maxRetries = 10; if (retryCount

David Brooks over 1 year ago