BluAge - L3 Workshop - Automation - Execute - Online Testcase - Assertion Error

The problem occurs in this method from class aws.bluage.l3.workshop.cobil00c.service.impl.Cobil00cProcessImpl.java

Here we are trying to locale last record for file using record id Recod.HIGH_VALUES according to this piece of code:

But when file is empty, we got these 2 error codes:

• Eibresp-> 13
• Eibresp2-> 80

When file is not empty, we got these 2 codes:

• Eibresp-> 0
• Eibresp2-> 0

So, we can patch this problem modifying Cobil00cProcessImpl.java

1. Update these methods:

• startbrTransactFile

if ((ctx.getWsVariables().getWsRespCd() == ResponseCode.NORMAL.getIntValue()) ||
	(ctx.getWsVariables().getWsRespCd() == 13 && ctx.getWsVariables().getWsReasCd() == 80))  { //Empty file

• readprevTransactFile

} else if ((ctx.getWsVariables().getWsRespCd() == ResponseCode.ENDFILE.getIntValue())||
	        (ctx.getWsVariables().getWsRespCd() == 13 && ctx.getWsVariables().getWsReasCd() == 80))  { //Empty file

• endbrTransactFile

//.handleException(); Commented to avoid error handler for empty file

2. Delete directory /carddemo-pom/carddemo-service/target/carddemo-service-1.0.0 and file /carddemo-pom/carddemo-service/target/carddemo-service-1.0.0.war
3. Execute step 3.5 and 3.6 from Automation-> Setup
4. Delete directory /carddemo-automation/tomcat/webapps/carddemo-web-1.0.0 and file /carddemo-automation/tomcat/webapps/carddemo-web-1.0.0.war
5. Copy file carddemo-web-1.0.0.war from /carddemo-pom/carddemo-service/target to /carddemo-automation/tomcat/webapps
6. Execute test case again

Hi All, Whoever is facing issue in bill payment. I have came up with a solution which worked for me. Please try this and comment if worked.

Issue:- Checks failing due to unable to lookup transaction, assertions etc.

Reason: Transact table is being emptied before bill payment testcase(don't know how this is happening) I have seen that in bluesam some datasets were empty.

Solution: I figured out while only testing 04-bill payment that if I ran all jobs before testing, I am able to do bill payment. Hence I have added the following in (carddemo-automation\tests-cases\02-online\04-bill-payment\execute.xml)

<project basedir="." name="Execute test case 02-online/04-bill-payment" default="execute">

	<target name="execute">
				<execute-batch job="TRANBKP" />
				<execute-batch job="POSTTRAN" />
				<execute-batch job="INTCALC" />
				<execute-batch job="TRANBKP" />
				<execute-batch job="COMBTRAN" />
				<execute-batch job="CREASTMT" />
				<execute-cypress testCase="${test.case}" spec="04-bill-payment.spec.js" />
	</target>
	
</project>

After this I got another error which is transaction id and amount was not matching.

Reason:- After all jobs are executed the amount is updated so is the transaction id.

Solution:- We can see in Execute->Test->Online->User features->Bill payment video in workshop that the trans id and amount is different from the automation cypress code which is used to compare the screens.

Hence I have modified the code here (carddemo-automation\tests-cases\02-online\cypress\tests\04-bill-payment.spec.js) I have done a lot of changes here :) Please keep a copy of original file before modifying, so you can revert back when things go wrong

Line no 134

//cy.get('#curbal').hasSize(14).hasValue('+000001764.21').isDisabled().isBlue()
cy.get('#curbal').should(($el) => {
    const value = $el.val(); // Get the actual value
    expect(value).to.include('1764.21'); // Check for the dynamic part
    expect(value.length).to.be.greaterThan(0); // Ensure it has a valid length
  }).isDisabled().isBlue()

Line no: 152

specify('Check confirmation transaction 2022071800000051', function() {

Line no: 173

cy.get('#errmsg').hasSize(78).hasValue('Payment successful.  Your Transaction ID is 2022071800000051.                 ').isDisabled().isHigh().isGreen()

Line no: 236

specify('View transaction 2022071800000051', function() {
cy.get('#trnidin').type('2022071800000051').type('{enter}')
cy.wait('@runTransaction')
})
specify('Check transaction 2022071800000051', function() {

Line no: 254

cy.get('#trnidin').hasSize(16).hasValue('2022071800000051').isEnabled().isGreen().isUnderline()

Line no: 269

//cy.get('#trnamt').hasSize(14).hasValue('+000001764.21').isDisabled().isBlue()
cy.get('#trnamt').should(($el) => {
    const value = $el.val(); // Get the actual value
    expect(value).to.include('1764.21'); // Check for the dynamic part
    expect(value.length).to.be.greaterThan(0); // Ensure it has a valid length

After these modifications I am able to execute the bill payment testcase and all screens are passing.

Note: if your transaction id is still not matching check the trans id in results and update the code.

Also for assertion error having msg <p> 2023 like this update the year in application.json file

The issue you're experiencing with the online test cases in the BluAge L3 Workshop automation step appears to be related to assertion errors in the Cypress tests. While the batch test cases passed successfully, the online test cases, specifically those related to bill payment and viewing transactions, are failing.

These failures could be due to several reasons:

1. Timing issues: The application might not be loading or responding as quickly as expected during the automated tests, causing assertions to fail.

2. Data inconsistencies: The test data used in the automated tests might not match what's expected, leading to assertion failures.

3. UI changes: If there have been any recent changes to the user interface, the Cypress tests might be looking for elements that have changed or no longer exist.

4. Environment differences: The automated test environment might differ from the manual testing environment, causing discrepancies in behavior.

To address these issues, you could try the following:

1. Review the Cypress test scripts and ensure they include appropriate wait times or use Cypress's built-in waiting mechanisms to account for potential timing issues.

2. Double-check that the test data used in the automated tests matches what's expected in the application.

3. Verify that the UI elements being tested haven't changed and that the selectors used in the Cypress tests are still valid.

4. Compare the automated test environment with the manual testing environment to ensure they are consistent.

5. Consider adding more detailed logging or debugging information to the Cypress tests to get a better understanding of where exactly the failures are occurring.

6. If possible, try running the failing tests in isolation to see if they pass when not part of the full test suite.

If the issue persists after trying these steps, you may need to consult with the BluAge support team or workshop facilitators for more specific guidance, as they would have more detailed knowledge about the expected behavior and common issues in the L3 Workshop environment.
Sources
L3 Workshop - Automation - Execute - Unloading of Bluesam KSDS file for compare is failing. | AWS re:Post
BluAge L3 Workshop (Go Live --> Testing --> Test Online) Blank Screen when testing Online Transactions CC00 | AWS re:Post