You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve just started exploring Bruno, and I’m working with several services that live in separate repositories. Each service has its own OpenSpec files and distinct endpoints.
For each endpoint, we expect to define both positive and negative test scenarios. Additionally, there will be cases where multiple API calls are needed to validate a complete workflow or business logic.
For those with experience using Bruno, I’d love to hear your suggestions on how to structure these tests so that:
Different scenario types are clearly visible and easy to navigate
Reporting remains meaningful and actionable across varied test flows
Bonus question:
If you’ve used tags to organize complex test suites, how do you approach tagging to keep things intuitive and maintainable?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I’ve just started exploring Bruno, and I’m working with several services that live in separate repositories. Each service has its own OpenSpec files and distinct endpoints.
For each endpoint, we expect to define both positive and negative test scenarios. Additionally, there will be cases where multiple API calls are needed to validate a complete workflow or business logic.
For those with experience using Bruno, I’d love to hear your suggestions on how to structure these tests so that:
Bonus question:
If you’ve used tags to organize complex test suites, how do you approach tagging to keep things intuitive and maintainable?
Beta Was this translation helpful? Give feedback.
All reactions