Bruno 101 + Automation Deep Dive
Two sessions in one hour. We open with a Bruno 101: the basics refresher for anyone new to Bruno or anyone who wants to make sure they are getting the most out of the fundamentals. Then we go deep on automation, from scripting and testing inside the app to running your collections headlessly in CI.
Part 1, Bruno 101:
- collections, requests, and how Bruno stores everything as files
- environments, variables, and secrets
- your first scripts, assertions, and the collection runner
Part 2, automation deep dive:
- pre- and post-request scripting patterns that scale
- Bruno CLI: running collections from the terminal
- wiring Bruno into CI/CD so every commit runs your API tests
Come for one half or stay for both. We'll close with live Q&A.
Your Hosts
James helps teams streamline their API development workflows and get the most out of Bruno. With extensive experience in developer tools and API ecosystems, he brings practical insights to every session.
Ganesh works with the Bruno community to turn real-world API workflows into practical demos and guides. As a DevRel Engineer, he focuses on helping developers get productive with Bruno quickly, from first request to fully automated pipelines.
What we'll cover
A basics refresher in the first half, then an automation deep dive in the second.
Collections and requests
Build your first collection, organize requests into folders, and see how Bruno stores all of it as plain files you can commit to Git.
Environments and variables
Switch between dev, staging, and prod without editing requests. Variable scopes, secrets, and the .env patterns that keep credentials out of your repo.
First scripts and tests
Write a pre-request script, add assertions on a response, and run a whole collection with the runner. The foundation Part 2 builds on.
Scripting patterns
Chain requests, pass data between them, handle auth flows, and keep scripts maintainable as collections grow.
Bruno CLI
Run any collection headlessly from the terminal, pick an environment, and emit reports your tooling can consume.
CI/CD pipelines
Wire Bruno into GitHub Actions, GitLab, or Jenkins so your API tests run on every commit and fail the build when a contract breaks.