FINERACT-2389: Fix the handling of nullable field overrides - E2E tests
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
@LoanOverrideFields
|
||||
Feature: LoanOverrideFields
|
||||
|
||||
@TestRailId:C4142
|
||||
Scenario: Verify that all nullable fields default to product when overrides not allowed and not provided
|
||||
When Admin sets the business date to the actual date
|
||||
When Admin creates a client with random data
|
||||
@@ -15,6 +16,7 @@ Feature: LoanOverrideFields
|
||||
Then LoanDetails has "graceOnInterestPayment" field with value: "1"
|
||||
Then LoanDetails has "graceOnArrearsAgeing" field with value: "3"
|
||||
|
||||
@TestRailId:C4143
|
||||
Scenario: Verify that all nullable fields ignore overrides when overrides not allowed
|
||||
When Admin sets the business date to the actual date
|
||||
When Admin creates a client with random data
|
||||
@@ -29,6 +31,7 @@ Feature: LoanOverrideFields
|
||||
Then LoanDetails has "graceOnInterestPayment" field with value: "1"
|
||||
Then LoanDetails has "graceOnArrearsAgeing" field with value: "3"
|
||||
|
||||
@TestRailId:C4144
|
||||
Scenario: Verify that nullable fields default to product when override is allowed but not provided
|
||||
When Admin sets the business date to the actual date
|
||||
When Admin creates a client with random data
|
||||
@@ -43,6 +46,7 @@ Feature: LoanOverrideFields
|
||||
Then LoanDetails has "graceOnInterestPayment" field with value: "1"
|
||||
Then LoanDetails has "graceOnArrearsAgeing" field with value: "3"
|
||||
|
||||
@TestRailId:C4145
|
||||
Scenario: Verify that nullable fields default to product when override is allowed and provided
|
||||
When Admin sets the business date to the actual date
|
||||
When Admin creates a client with random data
|
||||
|
||||
Reference in New Issue
Block a user