Skip to content

Expose internal host+port of microcks container for QuarkusIntegrationTest #146

@rquinio1A

Description

@rquinio1A

Reason/Context

Integration testing via containers, which is mostly useful for testing native applications compiled with Mandrel.

Description

When starting a Quarkus app as a container via QuarkusIntegrationTest, we'd need to configure the REST client with the microcks URL of our mocked APIs.
But there seeems to be no property exposed by Microcks DevService for that, the existing ones use localhost instead of the internal network alias.

Implementation ideas

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions