Please consult the test framework discussions on the list previously.  Do a
search on the archives for insights.

Then also see the work on client-feign and the gherkin tests.

We’ve deprecated some testing approaches in favor of cucumber (gherkin).
End2End



Sent from Gmail Mobile


On Fri, Apr 3, 2026 at 9:16 AM James Dailey <[email protected]> wrote:

> Excellent!
>
>
> On Fri, Apr 3, 2026 at 3:13 AM Tofunmi Oguntibeju <[email protected]>
> wrote:
>
>> Hi everyone,
>>
>> I hope you're doing well.
>>
>> As part of my ongoing contributions to Apache Fineract, I’ve been
>> reviewing the accounting module and noticed that it currently lacks a
>> dedicated test suite compared to other parts of the codebase.
>>
>> To improve reliability and maintainability, I plan to start introducing
>> test coverage for this module. The approach will focus on:
>>
>>    - Unit tests for core accounting domain logic
>>    - Validation and exception scenarios
>>    - Incremental improvements to overall coverage without disrupting
>>    existing functionality
>>
>> I’ll begin with small, self-contained tests and expand gradually to
>> ensure consistency with existing testing patterns in the project.
>>
>> Before proceeding further, I’d appreciate any guidance from the community
>> on:
>>
>>    - Whether there is any ongoing work or prior effort around adding
>>    tests to the accounting module
>>    - Areas where additional testing would provide the most value
>>
>> My goal is to strengthen confidence in the accounting module and
>> contribute to the long-term quality of the codebase.
>>
>> Looking forward to your feedback.
>>
>> Best regards,
>> Tofunmi Oguntibeju
>>
>

Reply via email to