Key Changes in Bruno v3.2.0

Bruno v3.2.0, a minor update released on March 18, 2026, focuses on expanding core functionalities and improving the developer and QA experience. This release is particularly significant for API testing workflows.

  • Open-Source Collaboration: A major highlight is the move of Git URL and API Spec URL collection imports from the enterprise edition to open source. This democratizes collaboration and version control for all users. Additionally, ZIP file import for collections simplifies sharing.
  • Enhanced Debugging & Scripting: QA engineers will benefit from a red status indicator for script errors in Request, Collection, and Folder Script tabs, making debugging faster. Stack traces for script and test failures are also improved. New scripting capabilities include object variable interpolation and the ability to remove headers from requests using scripts. The bruno-js library now includes a hasCookie function for more granular cookie management.
  • API Testing & Integration: Bruno now supports multipart/mixed content types, broadening its API testing scope. The OpenAPI sync feature helps keep collections aligned with API specifications. API spec export now includes environment variables, and translation capabilities for Bruno to Postman conversion have been enhanced, aiding teams migrating from other tools.
  • Usability & Workflow: New “scratch requests” allow for quick, temporary testing. Interface zoom control settings improve accessibility. For reporting, options to skip request and response bodies provide cleaner output. The collection runner now includes history logging, and gRPC testing expands with Unix Socket and Named Pipes support.

Impact for QA Teams

Bruno v3.2.0 significantly streamlines API testing and collaboration. The open-sourcing of Git and API spec imports fosters better version control and team sharing. Improved debugging tools and expanded API protocol support mean faster test development and more comprehensive coverage, directly impacting the efficiency of QA workflows. For more on Bruno’s capabilities, explore our article on bruno-api-client.

FAQ

  • Q: What’s the biggest change for open-source users?
    • A: The ability to import collections directly from Git URLs and API Spec URLs, previously an enterprise feature, is now available in the open-source version.
  • Q: How does this update help with debugging scripts?
    • A: A new red status indicator highlights script errors, and stack traces for failures are improved, making it easier to pinpoint and resolve issues.
  • Q: Can I import Postman collections more easily now?
    • A: Yes, translation capabilities for Bruno to Postman conversion have been enhanced, improving the migration process.