Skip to content

Blu Age L3 Workshop Automation Execute Online

0

Hi, I encounter the AssertionError in the Autmation 02-online/01-account.

All the online account test (02-online/01-account) results in success in loading the page and data, but fail in the last few steps Enter image description here

Error:

[exec] 1) Account tests cases [exec] Update account 00000000002 [exec] Check FICO Score error: [exec] AssertionError: Timed out retrying after 30000ms: expected '<input#acstfco.ng-untouched.ng-pristine.ng-valid.default.underline.single>' to have class 'red' [exec] at Context.eval (http://localhost:8080/__cypress/tests?p=support\index.js:1295:20) [exec] [exec] 2) Account tests cases [exec] Update account 00000000002 [exec] Check phone numbers error: [exec] AssertionError: Timed out retrying after 30000ms: expected '<input#acsstte.ng-untouched.ng-pristine.ng-valid.default.underline.single>' to have class 'red' [exec] at Context.eval (http://localhost:8080/__cypress/tests?p=support\index.js:1295:20)

Overview [exec] Account tests cases [exec] Access to application [exec] √ Launch application (6760ms) [exec] √ Check signon screen [exec] √ Sign with USER0001 [exec] √ Check menu screen [exec] View account 00000000002 [exec] √ Account View [exec] √ Check initial screen (5738ms) [exec] √ Search account 00000000002 [exec] √ Check account 00000000002 (5766ms) [exec] √ Back to main menu [exec] Update account 00000000002 [exec] √ Account Update [exec] √ Check initial screen (7997ms) [exec] √ Search account 00000000002 [exec] √ Check account 00000000002 (6932ms) [exec] √ Update first name [exec] 1) Check FICO Score error [exec] √ Update FICO Score [exec] 2) Check phone numbers error [exec] 3) Update phone numbers [exec] 4) Check ZIP code error [exec] 5) Update zip code [exec] 6) Check modifications ready to save [exec] 7) Save modifications [exec] 8) Checked modifications saved [exec] 9) Back to main menu [exec] [exec] [exec] 15 passing (7m) [exec] 9 failing

Environment: Using Tomcat 10 to run the carddemo-automation project No encoding in application-utility-pgm.yml

thank you very much

  • 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

AWS

asked 2 years ago353 views

3 Answers
1
Accepted Answer

answered 2 years ago

0

The assertion issue in online account:

Enter image description here

Similar assertion issue in online billing payment : Enter image description here

AWS

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

-1

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:

  1. Timing issues: The application might be taking longer than expected to apply the CSS changes after input validation.

  2. 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.

  3. Validation logic: There might be an issue with the validation logic in the application not triggering as expected.

  4. 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:

  1. Increase the timeout period in the Cypress tests to allow more time for the CSS changes to apply.

  2. Manually inspect the application during these steps to see if the visual changes are occurring as expected.

  3. Review the application code to ensure the validation logic is correct and the expected CSS classes are being applied.

  4. Check if there are any JavaScript errors in the browser console that might be preventing the validation from working correctly.

  5. 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

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.