FYI <@SteliosFran> will be speaking about Konsist ...

# konsist

[igor.wojda]

FYI @SteliosFran will be speaking about Konsist at Droidcon SF 🥳 I am eager to see this talk as he and his team have already created an impressive Konsist test suite containing 100+ tests to improve code base quality 😁😁

[stelios]

Thank you for all the hard work you have put so far! We’ll be very happy to spread the word and support the project!

[PoisonedYouth]

Is it an intention to provide predefined rulesets that can be used by others instead of Copy and Paste them?

[PoisonedYouth]

Something like (in case of Spring JPA)

// Rule
fun KoScope.verifyRepositoryNamingConvention() {
   this.interfaces()
       .withAnnotationOf(Repository::class)
       .assertTrue {
           it.name.endsWith("Repository")
       }
}

// Usage
Konsist.scopeFromProduction().verifyRepositoryNamingConvention()

[igor.wojda]

I have this in the backlog and I think this would be helpful, however we need time to focus on other priorities ATM

[PoisonedYouth]

It's enough for me at the moment that it is already planned for the future. Until then I can experiment with my solution

[igor.wojda]

What direction do you have in mind?

[PoisonedYouth]

Because I want the same basic ruleset for all of my projects using the same application framework (SpringBoot) I want to share them between the projects as test library instead of copy them and maintain them in multiple places.

[igor.wojda]

I was thinking about heaving a way to override a project root - this way all of these tests could be extracted to a separate project - WDYT?

[PoisonedYouth]

That means you want to import the whole test suite to be executed in the project, that imports it?

I currently only put the rules (as shown in the example above) to an own Gradle project and include it as test scoped dependency in all the Spring Boot projects on test scope.

[igor.wojda]

Yes, exactly - although I see this is not ideal

[PoisonedYouth]

That works as long as all the rules are relevant by all projects. As soon as there are exceptions this is leading to problems.

My goal is a bit different. I create a ruleset that contains rules relevant for SpringBoot projects but depending on the concrete project only a subset of rules can be used. This makes it flexible. Especially when working with multiple teams that have slightly different requirements/opionions.

[igor.wojda]

I agree - I will make a note to think how this cna be achieved

[PoisonedYouth]

I will experiment further and show the results as soon as I reach a stable stage.