Hello everyone, I hope this email finds you well. I am sharing my recent analysis of the API endpoints and integration tests for Fineract.
The entire process was performed in Excel due to the absence of a direct method to identify the core APIs being tested in a Testcase. Identified several APIs that are not currently the core focus of any existing test cases. These endpoints might require additional testing to ensure comprehensive coverage. I took the following steps :- - *API Endpoints Enumeration*: Reviewed the Swagger OpenAPI specification to compile a list of all available API endpoints for Fineract. - *Integration Tests Review* *: *Listed all integration tests present in the repository, noting the core APIs being tested in each scenario (outside what I considered in my imagination to be setup and teardown). - *Lists Comparison*: Standardised the format of both lists to facilitate a direct comparison, allowing for the identification of endpoints used in the existing tests. - *Identification of Untested APIs*: Determines which APIs are not the core focus of any current test cases by comparing the lists. - *Relevancy-Based Selection*: Based on functional relevance, I identified the main APIs for which new test cases need to be written to ensure these endpoints are adequately tested as primary targets. *Next Steps:* Please find attached *Fineract TODO Test Cases* <https://docs.google.com/spreadsheets/d/1VjKsXDAIPXeTqhnn89-R4Kj63zqN5xT-rWGI4AsFmKQ/edit?usp=sharing> for :- The API endpoints identified from the Swagger OpenAPI specification. The integration tests currently in place, along with the main APIs they cover. Labels for APIs not adequately covered in tests. Please let me know if you would like to discuss this further or need any specific details from my analysis. Thank you for your time and consideration. Best regards, Dhruv Sonagara
