API Testing (Duration: 30 hrs.) APIs or Application Programming Interfaces, are allowing software applications to communicate with each other. When you use an app on your phone, APIs work in the background just to fetch the data you see on your screen. APIs Types: 1- RESTful APIs: These are easy to work with and use HTTP methods to perform tasks. RESTful APIs are used to communicate with a server. When user ask for data, the server responds with the requested data. It’s like asking a shopkeeper for the item and the shopkeeper brings you the right item you requested. 2- SOAP APIs: These are protocol-based and use XML for sending and receiving messages. They’re highly secure and provide robust error checking. SOAP APIs are secure, reliable and more complex to work with. API Testing Types 1. Functional Testing This is the most basic type of API testing, which involves checking whether the API functions as expected. For example, if you have an API endpoint that retrieves user information based on a user ID, a functional test would involve sending a request with a valid user ID and checking if the response correctly includes the expected user information. 2. Load Testing This type of testing checks how the API handles many requests. In Load Testing user send hundreds or thousands of requests to the API quickly and monitor its performance and response times. 3. Security Testing Security testing involves checking the API’s security mechanisms, such as authentication and authorization. Ex: - User can access protected endpoints without providing valid authentication credentials and verify that the API correctly denies access. 4. Integration Testing Integration testing verifies that the API works correctly when integrated with other services. Ex: - When API integrated with Database, user can retrieve and store data correctly by using APIs. 5. Reliability Testing This testing ensures that the API consistently performs under the proposed conditions. For example, you might run a series of functional tests in a loop for an extended period to check the API’s reliability. 6. Performance Testing Performance testing checks the API’s response time and speed. It is similar to load testing but focuses on how quickly the API can process requests and return responses. 7. Negative Testing Negative testing involves providing invalid or unexpected input to the API to see how it handles such situations. Ex:- User might send a request with an invalid user ID and check that the API correctly returns an error in the response. 8. Compatibility Testing This testing checks whether the API works as expected across different platforms, devices, and environments. For example, you might run our tests on different operating systems or using different versions of the programming language to ensure compatibility. API Functionalities to be tested • Endpoint Responses: Each API endpoint should return the expected response for a given request. This includes checking the status code, the data returned, and the response format. Bugs in this area could include incorrect input parameters, output format, response code, and data type. • Error Handling: APIs should properly handle errors and return appropriate error messages. This includes testing with invalid inputs or when a resource is not available. Bugs in this area could include incorrect error messages or missing error codes. • Security: APIs should be secure and protect against unauthorized access. This includes testing authentication mechanisms and checking for weak encryption, SQL injection, or insufficient authentication mechanisms. Bugs in this area could include unauthorized access to sensitive data or functions. • Performance: APIs should respond quickly and handle a high volume of requests. This includes load testing to ensure the API can handle many concurrent users and requests. Bugs in this area could include slow response times or system crashes under high load. • Functionality: APIs should fulfill all the requirements and functions they are designed for. This includes testing all the API endpoints and methods. Bugs in this area could include missing functionality or duplicate functionality. • Compatibility: APIs should work well with the platforms, frameworks, or languages they are designed to interact with. This includes testing the API in different environments and configurations. Bugs in this area could include integration issues or incompatibility with certain platforms or languages. • Reliability: APIs should be available at all times and provide consistent results. This includes testing for downtime and latency issues. Bugs in this area could include frequent downtime or inconsistent results. • Documentation: The documentation for APIs should be clear, concise, and easy to understand. Bugs in this area could include incomplete or confusing documentation. What is API Automation Testing? API test automation, or “api automation testing”, is like a health check for your software. It’s all about ensuring the APIs, your software’s building blocks, are working as they should. • The main objectives are to ensure the APIs function correctly, validate their features, and improve the efficiency of the testing process. It’s like having a mechanic who checks all car parts to ensure they’re working properly. • The benefits of API test automation are numerous. It provides faster feedback, reduces manual effort, increases test coverage, and can be integrated into your CI/CD pipeline. Plus, it can lead to significant cost savings in the long run. So, it’s about finding problems and making the development process more efficient and cost-effective. What is webservices Type of webservices • REST • SOAP What is REST Type of HTTP Request • GET • PUT • POST • DELETE • OPTIONS • PATCH • Etc. JSON Basics • Json navigation • API for Json Processing Parameter Annotations • @PathParam • @QueryParam • @cookieParam • @HeaderParam • @FormParam • Etc. REST Client API • Get • Put • Post • Delete • Path Param • Query Param • Cookie Param