New Participant

Solved

AEM as a cloud service - production build fails in step custom functional testing - PublishPageValidationIT

Forum|Forum|4 years ago
February 17, 2022
3 replies
4093 views

Hi community, production build fails in the last step, custom functional testing, in com.xxxxxx.it.tests.PublishPageValidationIT

the publish url is pointing to localhost:4503 which is the same problem described here https://github.com/adobe/aem-project-archetype/issues/794

i created a new vhosts file and set serveralias per instructions but issue persists, how/where do i change the publish url so it is not pointing to localhost but to the actual publish url?

here´s a log excerpt, removed identifiers

[main] INFO org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement - InstanceConfiguration (URL: https://author-pxxxxxx-xxxxx.adobeaemcloud.net, runmode: author) found for test com.xxxxxxxx.it.tests.PublishPageValidationIT
[main] INFO org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement - Using default InstanceConfiguration provided (URL: http://localhost:4503, runmode: publish) for test com.xxxxxx.it.tests.PublishPageValidationIT
[main] INFO com.xxxxxx.it.tests.PublishPageValidationIT - Using http://localhost:4503/ as baseURL
2022/02/17 16:43:36:246 GMT [DEBUG] MainClientExec - Opening connection {}->http://localhost:4503
2022/02/17 16:43:36:261 GMT [DEBUG] MainClientExec - Connection discarded
2022/02/17 16:43:36:334 GMT [DEBUG] MainClientExec - Opening connection {}->http://localhost:4503
2022/02/17 16:43:36:335 GMT [DEBUG] MainClientExec - Connection discarded
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.506 s <<< FAILURE! - in com.xxxxxx.it.tests.PublishPageValidationIT
[ERROR] validateHomepage(com.xxxxxxx.it.tests.PublishPageValidationIT) Time elapsed: 0.203 s <<< ERROR!
org.apache.http.conn.HttpHostConnectException: Connect to localhost:4503 [localhost/127.0.0.1] failed: Connection refused (Connection refused)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:156)

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by Sebastiane_Edberg_

hi, i actually put an @ignore in the PublishPageValidationIT module for now to get the pipeline to finish successfully, waiting for feedback from support as well, thanks for your reply!

S

s_kumar

Employee

Increment the version of ‘aem-cloud-testing-clients’ dependency to ‘1.1.12’. This should fix the issue of functional test failure.

joerghoh

Employee

The problem is that "localhost:4503" is picked as remote side, which is wrong. On the other hand side I see it picked up properly for author:

[main] INFO org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement - InstanceConfiguration (URL: https://author-pxxxxxx-xxxxx.adobeaemcloud.net, runmode: author) found for test com.xxxxxxxx.it.tests.PublishPageValidationIT
[main] INFO org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement - Using default InstanceConfiguration provided (URL: http://localhost:4503, runmode: publish) for test com.xxxxxx.it.tests.PublishPageValidationIT

Unless you heavily customize the it.test pom.xml file (and that should never be necessary), this can/should not happen.

Sebastiane_Edberg_Author

New Participant

@joerghoh thanks for your reply, we have made minimal configuration to the instance, i had a look in the it.test pom xml and it looks like this for local id which is ok i guess:

<id>local</id>

<it.author.url>http://localhost:4502</it.author.url>

<it.author.user>admin</it.author.user>

<it.author.password>admin</it.author.password>

<it.publish.url>http://localhost:4503</it.publish.url>

<it.publish.user>admin</it.publish.user>

<it.publish.password>admin</it.publish.password>

</properties>

further down in that file we have:

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-failsafe-plugin</artifactId>

<testSourceDirectory>${basedir}/src/main/java/</testSourceDirectory>

<testClassesDirectory>${project.build.directory}/classes/</testClassesDirectory>

<sling.it.configure.default.replication.agents>false</sling.it.configure.default.replication.agents>

<com.sun.security.enableAIAcaIssuers>true</com.sun.security.enableAIAcaIssuers>

<it.logintokenauth>true</it.logintokenauth>

<sling.it.instances>2</sling.it.instances>

<sling.it.instance.url.1>${it.author.url}</sling.it.instance.url.1>

<sling.it.instance.runmode.1>author</sling.it.instance.runmode.1>

<sling.it.instance.adminUser.1>${it.author.user}</sling.it.instance.adminUser.1>

<sling.it.instance.adminPassword.1>${it.author.password}

</sling.it.instance.adminPassword.1>

<sling.it.instance.url.2>${it.publish.url}</sling.it.instance.url.2>

<sling.it.instance.runmode.2>publish</sling.it.instance.runmode.2>

<sling.it.instance.adminUser.2>${it.publish.user}</sling.it.instance.adminUser.2>

<sling.it.instance.adminPassword.2>${it.publish.password}

</sling.it.instance.adminPassword.2>

</systemPropertyVariables>

</configuration>

Asutosh_Jena_

New Participant

Hi @sebastiane_edberg_

Please raise a request with Adobe Support. This seems to be an issue with Product and needs to be fixed by product team.

Thanks!

Sebastiane_Edberg_AuthorAccepted solution

New Participant

hi, i actually put an @ignore in the PublishPageValidationIT module for now to get the pipeline to finish successfully, waiting for feedback from support as well, thanks for your reply!

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded