microcks/microcks-testcontainers-go

Go lib for Testcontainers that enables embedding Microcks into your unit tests with lightweight, throwaway instance thanks to containers.

microcks-testcontainers-go's Issues

Update Test container go to v0.31

Reason/Context

Fixe bug in tests

Description

Just saying that Test container go have release v0.31: https://github.com/testcontainers/testcontainers-go/releases/tag/v0.31.0

It fixes bug you mention: https://github.com/microcks/microcks-testcontainers-go-demo/blob/60df21fe221e06c4adc8f1bef99d87c56db5cab9/internal/controller/order_controller_test.go#L50-L51

Implementation ideas

I guess you just need to update depedencies

Release 0.2.0 version of microcks-testcontainers-go

Tag on GitHub!

Allow adding container dependencies for Async minion container from ensemble

See microcks/microcks-testcontainers-java#30 which has the full context and explanations.

Please discuss here the specific issue of adapting and implementing this to Go.

Add contract-testing support

Reason/Context

We must have feature parity with microcks-testcontainers.java and microcks-testcontainers-go 😉

Description

Adding a TestEndpoint() functino

Implementation ideas

No response

Add Secret creation/import on Microcks container

See microcks/microcks-testcontainers-java#29 which has the full context and explanations.

Please discuss here the specific issue of adapting and implementing this to Go.

Release 0.1.0 version of microcks-testcontainers-go

Tag on GitHub!

Fix some missing headers

Some headers are missing within Go files.

Replace Zulip by Discord on README

Update the badges and use this one:

Allow AsyncAPI mocking and contract-testing support

See microcks/microcks-testcontainers-java#27 which has the full context and explanations.

Please discuss here the specific issue of adapting and implementing this to Go.

Update Test container go to v0.32.0

Reason/Context

• Related to: testcontainers/testcontainers-go#2551

Description

We're waiting for v0.32.0 of TC-Go.

Implementation ideas

No response

Allow Postman contract-testing support

See microcks/microcks-testcontainers-java#24 which has the full context and explanations.

Please discuss here the specific issue of adapting and implementing this to Go.

Allow specification of artifacts to load on MicrocksContainer creation

Reason/Context

As of today, loading artifacts into the Microcks container should be done after the container is started-up using 2 methods:

• importAsMainArtifact(ctx, artifact) or,
• importAsSecondaryArtifact(ctx, artifact)

However, this way of doing things doesn't really fit with existing modules' logic - all of them have WithSomething() fluent API style methods that allow config definition at creation. Moreover, our approach can sometimes be harder to achieve cause it means you have to retrieve the container once initialized (depending on the test framework, this can be tricky) to import artifacts.

Description

Ideally, we'd like to be able to have something like:

microcksContainer, err := microcks.RunContainer(ctx, 
   testcontainers.WithImage("quay.io/microcks/microcks-uber:nightly"),
   testcontainers.WithPrimaryArtifact("testdata/apipastries-openapi.yaml"))

Implementation ideas

See if implementation ideas from microcks/microcks-testcontainers-java#26 can be reused/adapted here to Go

Develop and end-to-end demo showcasing all the feature of 0.2.0

Describe the bug

We have no full end-to-end demonstration of our Microcks testcontainers module capabilities. We need a demo so that users can figure out how to use it.

It would be awesome to adapt the Java one (see https://github.com/microcks/microcks-testcontainers-java-spring-demo) to Go!

Attach any resources that can help us understand the issue.

No response

Fix a typo on GraphQLMockEndpoint()

It was typed GrapQLMockEndpoint()