Package com.hazelcast.test.archunit

Class ArchUnitRules

java.lang.Object
com.hazelcast.test.archunit.ArchUnitRules
public final class ArchUnitRules extends Object

  • Field Details

    • SERIALIZABLE_SHOULD_HAVE_VALID_SERIAL_VERSION_UID

      public static final com.tngtech.archunit.lang.ArchRule SERIALIZABLE_SHOULD_HAVE_VALID_SERIAL_VERSION_UID
      ArchUnit rule checking that Serializable classes have a valid serialVersionUID

    • COMPLETABLE_FUTURE_USED_ONLY_WITH_EXPLICIT_EXECUTOR

      public static final com.tngtech.archunit.lang.ArchRule COMPLETABLE_FUTURE_USED_ONLY_WITH_EXPLICIT_EXECUTOR
      ArchUnit rule checking that only CompletableFuture async methods version with explicitly defined executor service is used.

    • MATCHERS_USAGE

      public static final com.tngtech.archunit.lang.ArchRule MATCHERS_USAGE
      ArchUnit rule checking that Hamcrest matchers are not mixed with AssertJ.

    • NO_JUNIT_MIXING

      public static final com.tngtech.archunit.lang.ArchRule NO_JUNIT_MIXING
      ArchUnit rule checking that JUnit4 and JUnit5 annotations are not mixed within the same tes

    • TESTS_HAVE_RUNNNERS

      public static final com.tngtech.archunit.lang.ArchRule TESTS_HAVE_RUNNNERS
      See Also:

    • OPERATIONS_SHOULD_NOTIMPL_BOTH_READONLY_AND_MUTATINGOPERATION

      public static final com.tngtech.archunit.lang.ArchRule OPERATIONS_SHOULD_NOTIMPL_BOTH_READONLY_AND_MUTATINGOPERATION
      Operations should not implement both ReadonlyOperation and MutatingOperation interfaces, otherwise split brain protection may not work as expected.

    • BACKUP_OPERATIONS_SHOULD_NOTIMPL_MUTATINGOPERATION

      public static final com.tngtech.archunit.lang.ArchRule BACKUP_OPERATIONS_SHOULD_NOTIMPL_MUTATINGOPERATION
      Backup operations should not implement MutatingOperation interface, otherwise there may be failures to apply backups.

    • PUBLIC_API_CLASSES_EXPOSING_INTERNAL_IMPLEMENTATION

      public static final com.tngtech.archunit.lang.ArchRule PUBLIC_API_CLASSES_EXPOSING_INTERNAL_IMPLEMENTATION
      See Also:

    • PARALLEL_JVM_TESTS_MUST_NOT_CREATE_HAZELCAST_INSTANCES_WITH_NETWORK

      public static final com.tngtech.archunit.lang.ArchRule PARALLEL_JVM_TESTS_MUST_NOT_CREATE_HAZELCAST_INSTANCES_WITH_NETWORK
      Creating Hazelcast instance with network in ParallelJVMTest test is risky as the instances from tests running in parallel may see each other. This can be mitigated to some degree by using unique/random cluster name, but it is not recommended to run such tests in parallel.