FINERACT-2268: added test scenarios to cover repayment schedule with large charge amounts - #4342
Closed
MarianaDmytrivBinariks wants to merge 2 commits into
Conversation
MarianaDmytrivBinariks
force-pushed
the
features/PS-2268_repayment_schedule_incorrect_values_after_charge
branch
6 times, most recently
from
February 19, 2025 10:24
481df8d to
fee1f4d
Compare
ruzeynalov
reviewed
Feb 19, 2025
ruzeynalov
approved these changes
Feb 19, 2025
Contributor
|
@MarianaDmytrivBinariks 85 failed for some reason. |
MarianaDmytrivBinariks
force-pushed
the
features/PS-2268_repayment_schedule_incorrect_values_after_charge
branch
5 times, most recently
from
February 19, 2025 18:15
88164bc to
d4fbb97
Compare
…rge charge amounts
MarianaDmytrivBinariks
force-pushed
the
features/PS-2268_repayment_schedule_incorrect_values_after_charge
branch
from
February 19, 2025 19:13
d4fbb97 to
c2c6485
Compare
…rge charge amounts
ruzeynalov
force-pushed
the
features/PS-2268_repayment_schedule_incorrect_values_after_charge
branch
from
February 26, 2025 15:05
fd36db7 to
1402fb3
Compare
ruzeynalov
deleted the
features/PS-2268_repayment_schedule_incorrect_values_after_charge
branch
February 26, 2025 15:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!
Write the commit message as per https://github.com/apache/fineract/#pull-requests
Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
Create/update unit or integration tests for verifying the changes made.
Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.
Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the developer mailing list for guidance, if required.)
FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.