- Newest
- Most votes
- Most comments
The assertion issue in online account:
Similar assertion issue in online billing payment :
answered 2 years ago
AbstractRdbmsPersistenceSupport : Loaded 50 records from AWS_M2_CARDDEMO_CARDXREF_VSAM_KSDS JicsFileBuilder : [CXACAIX] - IMPLICIT OPEN RESULT : JicsResponseCodeHolder [responseCode=NORMAL, resp2=0] EhcacheManager : Cache 'AWS_M2_CARDDEMO_TRANSACT_VSAM_KSDS' created .AbstractRdbmsPersistenceSupport : Dataset AWS_M2_CARDDEMO_TRANSACT_VSAM_KSDS is empty. JicsFileBuilder : [TRANSACT] - IMPLICIT OPEN RESULT : JicsResponseCodeHolder [responseCode=NORMAL, resp2=0] Cobil00cProcessImpl : RESP:000000013REAS:000000080 : Triggering an ABEND(AEIP) from JicsFileBuilder due to response code INVREQ
The issue you're experiencing in the Blu Age L3 Workshop Automation Execute Online step appears to be related to assertion errors during the account update tests. These errors are occurring specifically when checking for changes in CSS classes that should indicate validation errors.
The test is expecting certain input fields to have a 'red' class applied after updates, but this class is not being added within the expected timeout period of 30 seconds. This could be due to several factors:
-
Timing issues: The application might be taking longer than expected to apply the CSS changes after input validation.
-
CSS class mismatch: The test might be looking for a 'red' class, but the application could be using a different class name for error states.
-
Validation logic: There might be an issue with the validation logic in the application not triggering as expected.
-
Browser compatibility: If you're using a different browser than what the tests were designed for, it could cause unexpected behavior.
To troubleshoot this issue, you could try the following:
-
Increase the timeout period in the Cypress tests to allow more time for the CSS changes to apply.
-
Manually inspect the application during these steps to see if the visual changes are occurring as expected.
-
Review the application code to ensure the validation logic is correct and the expected CSS classes are being applied.
-
Check if there are any JavaScript errors in the browser console that might be preventing the validation from working correctly.
-
Ensure you're using the correct versions of all dependencies, including Cypress and any related plugins.
If the issue persists after trying these steps, you may need to reach out to the Blu Age support team or workshop facilitators for more specific guidance tailored to your environment and workshop version.
Sources
BluAge L3 Workshop (Go Live --> Testing --> Test Online) Blank Screen when testing Online Transactions CC00 | AWS re:Post
BluAge L3 Workshop CEEDAYS Program not found Exception when adding new transaction online | AWS re:Post
answered 2 years ago
Relevant content
asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago

The billing payment issue was resolved with the following answer (add the batch run. and update the bill payment js with the new transaction ID). The customer one is resolved by some other coding review. Thanks