kogito-examples contains tests with equal FQN, what is an issue for QE team during tracking tests results in polarion, as primary key is based on FQN there.

example of such tests:
./process-usertasks-custom-lifecycle-quarkus/src/test/java/org/acme/travels/ApprovalsProcessTest.java
./process-usertasks-custom-lifecycle-springboot/src/test/java/org/acme/travels/ApprovalsProcessTest.java
./process-usertasks-quarkus/src/test/java/org/acme/travels/ApprovalsProcessTest.java
./process-usertasks-springboot/src/test/java/org/acme/travels/ApprovalsProcessTest.java
./process-usertasks-with-security-oidc-springboot/src/test/java/org/acme/travels/ApprovalsProcessTest.java
./process-usertasks-with-security-quarkus/src/test/java/org/acme/travels/ApprovalsProcessTest.java
./process-usertasks-with-security-springboot/src/test/java/org/acme/travels/ApprovalsProcessTest.java

Complete list of potentially affected tests can be get as:

find -name *Test.java |sed 's#.*/##' | sort | uniq -cd

Where each number says how much tests with the same name we have.

Then if we run:

find -name TestName.java

For each entry for the earlier command, we need to asses if the package is unique for the set of classes returned by second command.