[
https://issues.apache.org/jira/browse/FINERACT-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066579#comment-18066579
]
Awaneet Mishra commented on FINERACT-2533:
------------------------------------------
Based on feedback from Adam Saghy on GitHub, I have pivoted from unit tests to
E2E integration tests.
I have closed PR #5623 and opened a new PR that implements the
{{SavingsAccount}} insufficient balance withdrawal scenario using the existing
Cucumber BDD framework.
*New Pull Request:*
[https://github.com/apache/fineract/pull/5646|https://www.google.com/search?q=https://github.com/apache/fineract/pull/5646&authuser=2]
> [TEST] Add E2E test scenarios for SavingsAccount insufficient balance
> withdrawal
> --------------------------------------------------------------------------------
>
> Key: FINERACT-2533
> URL: https://issues.apache.org/jira/browse/FINERACT-2533
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Savings
> Reporter: Awaneet Mishra
> Priority: Major
>
> Currently, SavingsAccount E2E test coverage is incomplete.
> This issue tracks adding proper end-to-end test scenarios
> following the existing patterns in fineract-e2e-tests-runner
> and fineract-e2e-tests-core modules.
> The new E2E tests will cover:
> 1. Insufficient funds during withdrawal — verify system returns
> HTTP 403 with error code "insufficient.account.balance" when
> client attempts to withdraw more than available balance.
> 2. Transactions on blocked/inactive accounts — verify system
> correctly rejects transactions on non-active savings accounts.
> 3. Backdated transaction interest recalculation — verify interest
> is correctly recalculated when backdated transactions are applied.
> These tests make real API calls with no mocking, following the
> Cucumber BDD pattern already established in SavingsAccount.feature.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
