Download as PDF, PPTX
Uploaded byBruno Pedro
How to Automate API Testing
The document discusses automating API testing, covering unit testing, functional testing, and API exploration. It outlines the processes, tools, and execution methods involved in each testing type while emphasizing the importance of automated tests and local testing. The conclusion highlights the significance of effective communication regarding API changes for providers.
More Related Content
Similar to How to Automate API Testing
How to Automate API Testing
- 1. Bruno Pedro January 2016 Howto Automate API Testing
- 2. Summary • types ofAPI testing • functional testing • API exploration • writing and running tests locally • automating test execution
- 3. 3 types ofAPI Testing • unit testing • functional testing • load testing increased complexity
- 4. Unit Testing • partof the development process • usually written by developers • tests how local code integrates with the API • focused on request and response handling • automated by a CI process
- 5. Unit Testing: mocking •actual API response is saved locally • test uses local copy of API response • several tools for different programming languages • VCR (Ruby) • nock (Node.js)
- 6. Functional Testing • partof the QA process • a kind of black-box testing • focused on response generation • often executed periodically • tests how the API behaves under a controlled input
- 7. Functional Testing: identification •which API calls should be tested • how are those calls used by the application • what should be tested • who should be notified if tests fail
- 8. Functional Testing: input •usually fake data • information that resembles real usage • often obtained by studying user input • updated often
- 9. Functional Testing: output •tests should be similar to unit tests • but performed on real API calls • additional output • response time • specific API responses during testing
- 10. Functional Testing: execution •manual crafting • manually triggered • potentially executed periodically • result flags CI process
- 11. API Exploration • startsin the product development phase • part of the product definition • confirmed in the development process • validated by QA
- 12. API Exploration: questions •why are you using the API • what API calls are used • how does the product integrate with the API • what happens if the API fails or is unresponsive
- 13. API Exploration: hands-on •getting a list of all the relevant API calls • obtaining authorization credentials if needed • preparing fake input data • exploring the API calls manually
- 14. API Exploration: hands-on swagger.iogetpostman.com
- 15.
- 16. API Exploration: hands-on collectionsare a way to group API calls
- 17. Local Tests • one-offtesting • batch testing • easy to validate • a way to discover unanticipated API responses
- 18. Local Tests: hands-on writtenin javascript and executed locally
- 19.
- 20.
- 21. Automated Tests • repeatableprocess • periodic execution • possibly flagging CI • dedicated or SaaS solutions
- 22.
- 23. Automated Tests: hands-on testscheduling using Runscope
- 24. Automated Tests: hands-on testmetrics provided by Runscope
- 25. Wrap up • unitand functional API testing • identification, input, output and execution • API exploration and introduction to Postman • local testing with Postman • automating tests with runscope
- 26.
- 27. + Sean O’Connor Lead Engineer It'sgreat to see a tool like API Changelog come along. (…) as an API provider, it's always a challenge to communicate to users when changes happen. [email protected] Get in touch! Bruno Pedro Thank you