Elytron module is always part of the build chain now. We use separate jobs to run unit tests, integration tests and mixed domain tests and Elytron integration tests are now run in all of them.
e.g. command we use to run just unit tests mvn test -DskipTests -Dts.noSmoke now starts also Elytron module (same goes to mixed domain, domain and others).
Elytron integration module should behave as other test suite modules - be part of all-modules.module.profile profile, have its own elytron.module.profile with ts.elytron activation property.