Evolution of a RESTful Testing Framework
summary
A custom REST test framework evolves from single-line Ruby hashes into readable YAML scenarios and relational test references that let one call capture values and chain requests with captures for chaining calls. It runs in Jenkins CI integration and mock-stubbing switches, targets an API gateway with OAuth/API-key realms, handles multiple base paths, and reports against OAS specs; uploader cites 18K APIs and mentions 60+ possible response codes. Work-in-progress adds production monitoring (New Relic) and evaluation against Postman.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:34Kevins background
- 6:15API Definitions
- 8:40Testable Parts
- 9:44API Gateway
- 12:22API Overview
- 14:38The Evolution
- 17:19Limitations
- 19:30Best Practices
- 20:18Chain Requests
- 26:09Extensibility
- 29:10Monitoring
related talks
44mAPI Testing following the Test Pyramid
28mTesting HTTP APIs in Ruby
49mFabulous Tests with Spock and Groovy
38mWriting a Test Framework from Scratch
32mWriting a Test Framework from Scratch
45mFuzz Testing Web APIs: Overview of Existing Tools
38mPerformance Testing sucks! How to get started testing RESTful APIs and GraphQL
37mFrom Rigidity to Resiliency: An Evolutionary Tale of Selenium-Based Frameworks