[WEJBHTTP-147] CI Add integration testing to CI script

[marekkopecky]

Jira tracker: https://issues.redhat.com/browse/WEJBHTTP-147

This PR is blocked by wildfly/ejb-client-testsuite#80

Add integration tests to upstream CI for https://github.com/wildfly/ejb-client-testsuite

Similar like:

• EJBCLIENT-505
• [EJBCLIENT-505] CI Add integration testing to CI script jboss-ejb-client#644

[ropalka]

The CI failed with:

---

2024-09-10T11:59:16.2730528Z [INFO] Results:
2024-09-10T11:59:16.2730982Z [INFO]
2024-09-10T11:59:16.2731303Z [ERROR] Errors:
2024-09-10T11:59:16.2737009Z [ERROR] FailoverViaWildflyConfigXmlStatefulBeanTestCase.testSessionCreationWhenOneNodeIsDown:284 » Communication EJBCLIENT000062: Failed to look up "/basic-failover-stateful/CounterBeanStateful!org.wildfly.ejbclient.testsuite.integration.multinode.failover.beans.CounterBean?stateful"
2024-09-10T11:59:16.2742265Z [ERROR] FailoverViaWildflyConfigXmlStatefulBeanTestCase.testSimpleFailover_shutdown_invocationTimeout:316 » Communication EJBCLIENT000062: Failed to look up "/basic-failover-stateful/CounterBeanStateful!org.wildfly.ejbclient.testsuite.integration.multinode.failover.beans.CounterBean?stateful"
2024-09-10T11:59:16.2744183Z [INFO]
2024-09-10T11:59:16.2744673Z [ERROR] Tests run: 71, Failures: 0, Errors: 2, Skipped: 3

[marekkopecky]

@ropalka Original CI failure should be fixed by wildfly/ejb-client-testsuite#80

Can you please trigger the CI here on PR again?

[ropalka]

/retest this please

[marekkopecky]

@ropalka Looking to the github CI and it seems that new CI run hasn't been triggered, there is still a run from 10th September: https://github.com/wildfly/wildfly-http-client/actions/runs/10716725782/job/29928393345?pr=235

Let me rebase this PR, hopefully it helps ...

[marekkopecky]

@ropalka Now it seems that CI is awaiting approval, can you please check it and consider to approve it?

[fl4via]

@marekkopecky the CI is failing and we cannot see why because of the very long output of the tests. Can this be tweaked in a way that we see only tests that are being run without seeing all the log output?