[
https://issues.apache.org/jira/browse/FINERACT-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Saghy updated FINERACT-2443:
---------------------------------
Labels: beginner-friendly (was: )
> Add Integration Test for Report Execution
> -----------------------------------------
>
> Key: FINERACT-2443
> URL: https://issues.apache.org/jira/browse/FINERACT-2443
> Project: Apache Fineract
> Issue Type: Test
> Components: Reports, Test
> Reporter: Shiv Deshpande
> Priority: Major
> Labels: beginner-friendly
>
> *Problem:*
> Currently, the reporting module lacks comprehensive end-to-end integration
> tests that verify data integrity in the generated output.
> Existing tests (e.g., ReportsTest.java) primarily check for HTTP 200 OK
> status codes but do not verify that specific client, loan, or transaction
> data actually appears in the report body. They also rely on pre-existing
> database state rather than creating their own test data.
> *Test Scenario:*
> 1. *Setup:* Create a new Client via the API with a random, unique name
> (e.g., "ReportTestClient_123").
> 2. *Execution (JSON):* Execute the "Client Listing" report in JSON format
> and assert that the unique client name exists in the response data.
> 3. *Execution (CSV):* Execute the "Client Listing" report in CSV format and
> assert that the unique client name exists in the CSV content.
> *Impact:*
> This ensures that the reporting engine is correctly querying and formatting
> data from the database, protecting against future regressions during
> refactoring or optimization of the reporting module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
