Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IT HTTP tests fail when defined to run with random AEM Ports #1438

Closed
msagolj opened this issue Mar 10, 2021 · 0 comments
Closed

IT HTTP tests fail when defined to run with random AEM Ports #1438

msagolj opened this issue Mar 10, 2021 · 0 comments
Labels
bug Unexpected problem or unintended behavior that impairs normal functioning of the product.
Milestone
2.15.2

Comments

@msagolj
Copy link
Contributor

msagolj commented Mar 10, 2021 •
edited
Loading

Bug Report

Due to the change done here:

https://github.com/adobe/aem-core-wcm-components/blob/master/testing/it/http/pom.xml#L201-L204

if a user starts IT HTTP tests by using the sling.it.instances.* properties, using different ports than whats defined in granite.it.author.url/granite.it.publish.url, it ends up with some additional, wrong instance configurations. The IT HTTP Clients than can end up running against a non-existing configuration and tests will fail.

(CQ-4317392)
@msagolj msagolj modified the milestones: 2.16.0, 2.15.2 Mar 10, 2021
@msagolj msagolj added the bug Unexpected problem or unintended behavior that impairs normal functioning of the product. label Mar 10, 2021
@msagolj msagolj mentioned this issue Mar 10, 2021
Merged
vladbailescu pushed a commit that referenced this issue Mar 12, 2021
@msagolj
IT HTTP tests fail when defined to run with random AEM Ports (#1439)
aa6f750 
Remove systemPropertyVariables

Fixes  #1438
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Unexpected problem or unintended behavior that impairs normal functioning of the product.
Projects
None yet
Milestone
2.15.2
Development

No branches or pull requests
1 participant
@msagolj