API Testing
- Acronym
- sig-devops-api-testing
- Belongs to
- SIG DevOps
- Responsible
- hbuhl
- History
- (v1) 2021-01-13 - created initially
- (v2) 2021-01-15 - filled out until evaluation
- (v3) 2021-02-02 - finalized decision
- (v4) 2021-02-04 - added sources
- (v5) 2021-02-05 - presented
- (v6) 2021-02-12 - state set back to 4
Why is there need for such a decision?
API calls must be tested like any other runnable code in a project.
Additional sources for better understanding the background
- Wikipedia - Rest
- Spring Testing - Testing Web
- Spring Boot Testing
- RESTful API Tutorial
- Entity to DTO conversion in Spring
- Rest Return Codes
Viable Options
- Unit (mocking) and integration tests
Alternatives not seriously considered
- None
How has this decision been evaluated?
The options will be scrutinized in regard to:
- Amount of resources/documentation
- Easy of usage
- Cost (must be free)
- How well they fit into existing parameters (automation, easier integration, less overhead)
Resolution Details
Reasons for the resolution
The given option was the only valid one.