Page:
Testing API with Bruno
Pages
API SMHI
API TimeEdit
Accessibility Testing
Api documentation
Bat/Ps
Branch Creation
C# Coding Convention
CSS Coding Convention
Coding Conventions
Creating new databases
Dapper
Documentation for service endpoints
Documentation of useTemperature and mock sensor
Energy endpoints
Environment
Evaluation react-grid-layout
Evaluation Localization
Evaluation Password hashing
Evaluation Testing framework
Evaluation of Logging Frameworks
Formatter
Frontend model
Generic Diagram for Sensor data flow
Home
How to- Creating Databases in Docker
Implementing different Styles
Implementing new Mockup sensors
Implementing new Views
Installation script documentation
Installation
Issues
JSON Coding Convention
Jest Testing
Layout endpoints
Linux
Localization
Login endpoints
Mac
Middleware model
Mock API Ceation Guidelines
Mockup models
Model Tools and Standards
Parking endpoints
React/JavaScript Coding Convention
React
Reviews
Room booking endpoints
SQL Coding Convention
Scheduled Database tasks
Scripting Coding Convention
Secrets and .env
Server Access
Server-Deployment
Service/API models
System models
System requirements
Temperature endpoints
Testing API with Bruno
Testing Architecture
Testing frontend for Mobile devices
Testing frontend with Playwright
Testing methodology
Västtrafik API
Webpage Design
Windows
pg_cron and scheduled database jobs
xUnit Testing
No results
2
Testing API with Bruno
Elinus Persson edited this page 2026-05-12 12:25:07 +00:00
Table of Contents
Testing API with Bruno
Introduction
Bruno is a git native API client which means it can store its results in folders and text files that can be sent along with git pulls and pushes. The text file will act as documentation of API calls/url endpoints and their results which can help develop different views by giving clear documentation of existing endpoints and what data they receive.
Prerequisites
- Git
- Optional: Node.js
How to use
- Install Bruno.
- Create a new "Collection".
- Add a "New request".
- Set the type to HTTP.
- Add a request name.
- Set the GET/POST method.
- Add the URL, for example:
http://172.18.0.14:8080/layout/getSpecificLayout. Note: The IP, if needed, can be found usingdocker inspect. But the service has been added in the endpoint config, then use that mapping instead. Example on that is:http://127.0.0.1/api/login/auth/login
- If there are parameters needed, you can:
- Add them to the "Params" tab (which auto-appends them to the URL).
- Set the "Body" to JSON format and add the payload there (for POST/PUT requests). Note: A body containt type need to be selected. That can be done on the defult "no body" button at the end of the header where the tabs are found.
- Manually type them at the end of the URL.
- Press the send button to send the request.
Here is a quick start guide provided by Bruno. It contains helpful screenshots and more in-depth explanations on how to configure specific methods and advanced features.
1. Setup
2. Standards
- Coding Conventions
- Issues
- Branch creation
- Reviews
- Implementation Standards
- [WIP] Creating new databases
- Localization
3. Models and Diagrams
4. Testing
5. Documentation
- Documentation for service endpoints
- API documentation
- Webpage Design
- Secrets and .env
- Evaluations
- Installation and Rebuild script documentation
6. Guides and How-to's
7. Micro Service Mockup Api
- Guidelines Mircro Service Mockup
- Documentation of useTemperature/useTemperatureTimeSeries mockup sensor