Hari is a software engineer who needs to build tested APIs for a new product. The document provides guidance on how to start API testing, including testing the API response, data insertion, edge cases with wrong user inputs, security with unauthorized access, unit testing, integration testing, edge case testing, authentication, and achieving full code coverage does not guarantee full test coverage. Security testing to check who can access the API and what level of access they have is also recommended.

1. Sijan Bhandari
@sijanonly
Software Engineer
at
Leapfrog Technology

2. How to start API TESTING?

3. Hari is a Software Engineer at Fusemachines.

4. He needs to build Tested API
for a product.

5. API
Testing ?

6. Integration
Testing
Edge Cases
Testing
Security
Testing
Unit
Testing

7. Hari list out all possible
WHquestions.

8. Whether API gives right response ?

9. Is API inserting data
correctly ?

10. What if user inserts wrong inputs?

11. What if unauthorized user try to access
your API ?

12. Unit Testing

14. Integration Testing

16. Edge Test Cases

18. Authentication ?

19. Authentication Authorization
Who you are ? What access you have ?

20. Security Testing

22. 100% CODE coverage
doesn’t mean
100% TEST coverage

23. Thank you.