Create independent copies for injection

Curerntly, the same instance is injected at all injection points. I.e., this fails:

@Test
private foo(@BlueInstance one, @BlueInstance another) {
    assertNotSame(one, another);
}

This can be dangerous if the test modifies the content of the injected instance, as this change will be visible through all other injected blue instances, thus violating the expectations in the other (concurrently executed) tests or later in the same test.

Suggested solution:

Before injection, create a deep copy of the "etalon instance", and inject that copy instead.

Once the objective achieved, this should pass (pseudocode):

@Test
private foo(@BlueInstance one, @BlueInstance another) {
    assertDeepNotSame(one, another);
    assertDeepReflectionEqueals(one, another);
}

Default - deep or shallow?

Deep copy is best for the test isolation but comes at performance price. The latter should be profiled, and if found insignificant then the default should be set to deep copy.

A way of configuration must be provided to control this behavior. For example, class-level annotation @RedAndBlueSettings with field createCopies would work nicely.

Confusing error message when a prefab is needed

When object factory fails to construct a prefab automatically (e.g. because the type is abstract or non-instantiable), an exception is thrown which explains very little about the problem and difficult to enterpret.

Receiver class nl.jqno.equalsverifier.internal.reflection.PublicKey$$DynamicSubclass$41294f8$ does not define or inherit an implementation of the resolved method 'abstract byte[] getEncoded()' of interface java.security.Key.
java.lang.AbstractMethodError: Receiver class nl.jqno.equalsverifier.internal.reflection.PublicKey$$DynamicSubclass$41294f8$ does not define or inherit an implementation of the resolved method 'abstract byte[] getEncoded()' of interface java.security.Key.
	at core.security.PublicKeyEncoding.encodeX509(PublicKeyEncoding.java:47)
	at core.state.EncryptionKeysMapper.encodePublicKey(EncryptionKeysMapper.java:34)
	at core.state.EncryptionKeysMapperImpl.encryptionKeysToPublicKeyEntity(EncryptionKeysMapperImpl.java:52)
	at core.state.EncryptionKeysMapperImpl.toEntity(EncryptionKeysMapperImpl.java:25)
	at core.state.EndpointAppKeysMapperImpl.toEntity(EndpointAppKeysMapperImpl.java:29)
	at state.EndpointAppKeysMapperTest.testTransitive(EndpointAppKeysMapperTest.java:33)

Such exception should be wrapped into a higher-level exception explaining the problem and possible solution (i.e., Consider introducing a prefab for PublicKey)

Minimal reproducible example

public class EndpointAppKeys {
  private CipherSuite cipherSuite;
  private EncryptionKeys clientKeys;
}

public class EncryptionKeys {
  private PublicKey publicKey;  // <-- PublicKey is interface. It declares but never defines `public byte[] getEncoded()`, hence the failure to instantiate the mock
}

@ExtendWith(RedAndBlueExtension.class)
public class EndpointAppKeysMapperTest {

    @Test
    void testTransitive(@RedInstance EndpointAppKeys red, @BlueInstance EndpointAppKeys blue) {
       ...
    }
}

Support Java 11

Currently supported min version is 17

Abnormal behavior was reported by @nextincrement

The issue I encountered is that. when defining an instance of JsonNode as a prefab value, some error is raised because the abstract class JsonNode does not meet some requirements - while it's concrete implementation (so, not the declared class but the actuall class) should be fine. I know this because, when using equals-verifier, I can succesfully define two prefab values for an instance of JsonNode.
...
However, this [instantiating builders] does unfortunately not apply to the JsonNode as this type is also used in any builder (JsonNode in -> JsonNode out). I think that a very simple minimal test case: creating a red/blue instance for a class using just a JsonNode field (or maby two fields, including a simple string) may reveil the bug. If my recollection is right, it should fail immediately but can't test it right now due to some compiler errors I need to fix first.

Needs investigation

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update gradle/gradle-build-action digest to 093dfe9

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Improve recognition of generic prefabs

The following example fails with exception "java.lang.IllegalStateException: Missing RED prefab of type null":

public class Entity {
    private final EntityColor color;
}

public class EntityBuilder {
    private Supplier<EntityColor> colorSupplier;

    public Entity build() {
        return new Entity(colorSupplier.get());
    }
}

@ExtendWith(RedAndBlueExtension.class)
public class EndpointConnectionMapperTest {

    @PrefabRed
    private Supplier<EntityColor> prefabRed = () -> new EntityColor("red");
    @PrefabBlue
    private Supplier<EntityColor> prefabBlue = () -> new EntityColor("blue");

    @Test
    void testTransitive(@RedInstance EntityBuilder redBuilder, @BlueInstance EntityBuilder blueBuilder) {
        // GIVEN
        Entity red = redBuilder.build();
        Entity blue = blueBuilder.build();
        ...
    }
}

The exception trace attached as file exception_trace.txt

Currently, at Maven Central it shows up as production dependency:

// https://mvnrepository.com/artifact/io.github.neboskreb/red-and-blue
implementation 'io.github.neboskreb:red-and-blue:1.1.0'

Update the Maven metadata so the scope is shown as test:

// https://mvnrepository.com/artifact/io.github.neboskreb/red-and-blue
testImplementation 'io.github.neboskreb:red-and-blue:1.1.0'