How do you keep repeatable API checks with the app code?
In Bruno, a collection is a folder of saved requests. Current setup supports YAML or Bru text files. You can keep the folder beside your app and review its changes in Git, which records file history.
For a demo inventory app, save a request that reads sample stock levels. A teammate can see which address setting and expected result changed before using the collection.
Does saving a collection locally keep all its data on your computer?
The files can live locally, and the request still goes to whichever address you select. If you commit the folder or run it in a shared build service, check what settings, example data and reports become accessible there.
Keep addresses for disposable and real environments distinct. Use secret variables for credentials and inspect plain files before committing or exporting them. Bruno documents that its export omits secret variables. A value pasted into an ordinary field needs separate review.
What can you keep without a paid Bruno plan?
The open-source edition includes core request testing and unlimited collection runner use. Current paid tiers charge per user and add features such as deeper built-in Git actions or integrations. A normal local folder can still be managed with your own Git tools.
Keep the collection, expected results and safe example settings. Save the instructions for supplying credentials separately. The command-line runner can use the collection in an automated build, so check which app and environment that build can reach.
How can you review one stock check without connecting to a store?
On paper, draw a fictional item with seven in stock and one read-only request. Use no account, credentials, request or repository change.
- Write the expected responseMark which item and stock count the sample answer should contain. Draw how the check reports a missing item or wrong count.
- Mark the files you would sharePut the request definition and fictional sample value in the shared folder. Put any future test credentials outside it.
- Stop before connectingWrite which isolated test address a future run would use. Leave the request unsent if you cannot confirm that the address and every connected service are disposable.