Getting started with Rest APIs
summary
A consultancy loses a bank contract after treating REST as just HTTP, so the claim is clear: REST is an architectural guideline not a protocol, and missing hypermedia and state constraints causes production defects. The talk shows concrete tools and examples: Postman for hands‑on calls, RandomUser.me as a test data API, contrasts Selenium UI checks with API tests, and promotes contract testing and the San Francisco Depot template as a working approach to verify behavioral, contractual, and solution levels.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:37Andreis background
- 1:43Story behind the presentation
- 3:37Google Trends
- 4:02The Future of Programming
- 6:36Guidelines
- 8:38Architecture
- 9:12What Rest is not
- 10:17Hypermedia
- 11:01Quality attributes
- 11:50HTTP vs REST
- 12:37Who uses REST
- 13:10Visibility
- 13:38String puppets
- 15:13Web developers
- 15:43REST API template
- 16:52CRUD operations
- 17:16Maslows Pyramid
- 18:37Testing Pyramid
- 19:31Testing Scales
- 21:58Example
- 25:38Solutionbased approach
- 26:10Visual approach
- 26:26Functions
- 27:14Mnemonics
- 28:18Tools
- 30:45Summary
related talks
37mContract testing with examples or Contract First
31mAPI testing journey through web protocols
41mREST Again? Oh, Come On!
23mThe Why & How of Testing APIs
57mGive it a REST - Tips for designing and consuming public API's
01h 01mAutomation Testing a REST API with Mocha
04mReal-World Enterprise REST API Design
19mReady to Bet on Your API Health?