The Why & How of Testing APIs
summary
Claim: APIs must be tested beyond ad hoc checks — include testers before design, write API-level tests before implementation, and treat tests as documentation customers can run. Uses SoapUI and LoadUI (open source, 1 million users, only two countries never downloaded) and recommends simulate external APIs and scenario-based, data-driven runs rather than single Postman calls. SoapUI 4.6 adds easier REST support; tests should run automatically and verify SLA, security, uptime and operation coverage.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:35About SmartBear
- 1:30Turkmenistan and Westerner
- 2:25The importance of APIs
- 3:18Audience
- 3:53Testers
- 4:48Why Test
- 5:53The New Economy
- 7:05What to Test
- 8:09Coverage Testing
- 9:01How to Test
- 9:44Usability
- 12:11Rest Services
- 12:43Testing Tools
- 13:25True Testers
- 13:53Scenario Based Testing
- 14:50DataDriven Testing
- 15:45Simulation
- 16:33Supply your tests
- 17:47Rest
- 18:08Feedback
- 18:39Takeaway
- 19:31Testdriven Development vs Unit Testing
- 21:00Testing REST APIs
related talks
54mShould You Be Doing More API Testing?
14mAPI First Mindset
16mAPI Platforms, Ready for Testing and Virtualization
31mAPI testing journey through web protocols
07m“API Testing in Startups using Postman”
25mRethinking Software Quality: Why API Testing Needs to Change
23mSolving Challenges in API Testing to Achieve More Agile Development
26mTips and tricks for writing API Tests