API Exploratory Testing
summary
Demonstration uses Postman and Chrome DevTools to interrogate a Star Trek search API and reports concrete surprises: queries return five results for many filters, partial matches often fail, mirror filtering treats truncated tokens as false, and a malformed space encoding triggers a 500 internal server error that leaks a Java stacktrace. Examples include header and Accept variations (JSON vs XML) and saved Postman examples; experiments reveal what works, what leaks implementation details, and which filters are actually applied.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 4:27Exploration vs known testing
- 8:01Session based testing
- 14:52API behavior with DevTools
- 21:29Live API exploration
- 38:52Key takeaways from API exploratory testing
related talks
22mAPI Security Testing with Postman: Best Practices and Techniques
49mTesting Your APIs: Postman, Newman & Beyond
14mMore than 200 OK: How to Do Negative Testing on APIs
15mAre Your APIs Performing Enough? Not Sure, Let’s Test It Then
18mBreaking the Mold Innovative Approaches to Testing GraphQL APIs
40mApisecure, 14 & 15 March 2023 - Ian Douglas, Senior Developer Advocate at Postman.
17mAPI Testing Unlocked
27mEffectively Testing Services