No video :(

Unit Test Your Spring Architecture With ArchUnit by Roland Weisleder @ Spring I/O 2024

Подписаться 35 тыс.

Просмотров 4,7 тыс.

50% 1

Spring I/O 2024 - 30-31 May, Barcelona
Slides: speakerdeck.co...
Repo: github.com/rwe...
Architecture and code are drifting more and more apart? The implementation of non-functional requirements and cross-cutting concerns is often forgotten? Too much spaghetti code due to circular dependencies? Sadly, such things happen far too often and will quickly lead to an unmaintainable code base.
In the Java ecosystem, the library ArchUnit is a possible solution for this situation. We will look at how we can use ArchUnit to test our architecture within unit tests and finally get structure back into the system. We will also look at archunit-spring, which simplifies writing ArchUnit tests for Spring applications.

Опубликовано:

5 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 3

@TechTalksWeekly Месяц назад

Roland's talk has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats!

@dezee2412 Месяц назад

a very interesting project. I will be using it in future.

@avalagum7957 Месяц назад

At 12:09, do `that()` and `should()` really do anything? Or are they just some noop to make code sound English-grammatically correct? At 13:15, `resideInAPackage("...owner...")`: if we refactor the package names (e.g. no package has the word "owner" in it), then this test always passes. Why do variables (e.g. ControllerNaming, OwnerDependencies ...) start with a capital letter? If ArchUnit is written and used in Scala, I guess that those ArchRule can be written like this: classes that areAnnotatedWith Controller.class should haveSimpleNameEndingWith "Controller". This reminds me of ScalaTest which was thought to be cool about 7-8 years ago because of its DSL, but now I wonder how many percentage of Scala developers can stand that syntax.