spring-cloud-contract: spring-cloud-contract-wiremock wrong dynamicPort assigned to wiremock.server.port

Hi, I’m using spring-cloud-contract-wiremock to make use of the functionality where the dynamically generated server port is assigned to a property to be used in endpoint definitions.

It seems that there’s a bug in the implementation where a different port number is assigned to the wiremock.server.port property.

Here’s a demo project which illustrates the bug. SpringCloudContractWiremockBugDemoApplicationTests fails where it should succeed, as per the documentation section 11.3. It speaks of a different property, wiremock.port, but I’m guessing this is due to a typo/outdated docs.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 18 (9 by maintainers)

Commits related to this issue

Most upvoted comments

That comment. I haven’t noticed that. I’ll fix it