Hi Arnav, Welcome to the project!
I’ve had a look at this story, and while it doesn’t give us a ton of details, Fineract has some testing strategies we can use: - Unit testing: This is usually for checking out small bits of logic and calculations in the system. It might not be the best fit for this issue. - Integration testing: This helps make sure all the pieces work together and communicate properly. Writing an integration test that calls the right API and checks the validation logs and responses could be really helpful! However, this kind of test in Fineract needs some developer experience and knowledge of the existing helper methods for calling these APIs. - E2E testing: Gherkin-based cucumber testing was introduced recently, which is great because the test steps are written in plain English, making them easier to understand and work with. Here’s an example for each: - Integration test: `org.apache.fineract.integrationtests.CreditBureauConfigurationTest` - E2E test: `features/BusinessDate.feature:2` -> We don’t have any existing E2E test cases for Credit Bureau testing, so we’ll need to create the stepdefs, like `org.apache.fineract.test.stepdef.common.BusinessDateStepDef#setIncorrectBusinessDateFailure`. I hope this helps you get a better idea of the options available! Regards, Adam On Dec 19, 2025, at 6:26 AM, Arnav Patil <[email protected]> wrote: Hello everyone, My name is Arnav Patil, and I am a student preparing to contribute to Apache Fineract as part of my GSoC preparation. I came across FINERACT-2116 (Create credit bureau configuration validation tests) and wanted to check whether this issue is still relevant for the current Fineract codebase. If so, I would like to work on it. I would also appreciate guidance on: - Whether JUnit or Cucumber tests are preferred for this issue - Any existing test classes or references I should follow Thank you for your time and guidance. Best regards, Arnav Patil
