In February 2025 I was looking for a book that I could give to my developers, so that they would know how to write tests. With that in mind I reviewed the draft of the first volume of Angry Tests, a book about tests by Yegor Bugayenko. I did not agree with everything in it, and while reading it I got the idea to write a book of my own. I did not know how much I had to say, and I worried that it would end at 20 pages, too thin even for a small handbook. So I hoped for at least 100 pages, and I planned about three months of work. The work started in Claude Code on 29 November 2025, so by that plan the book would be done around the end of February. Instead Laminar Software Design became 277 pages and went live on 31 August 2026, after nine months of work instead of three. So where did those nine months go?
OCC controllers in SAP Commerce are rarely covered by tests that run them with their real configuration. For that reason a misconfigured data mapper or a broken controller mapping shows up only after the server is started and a real request is sent. SAP Commerce already ships test support, which runs this whole chain inside a JUnit test, and below is a recipe for using it.
Claude Code does not provide native support for switching between multiple accounts or profiles. Having a personal Claude account for side projects and a separate work account for professional tasks means constantly logging in and out to switch between them. This is annoying and error-prone as it is easy to forget which account is active and accidentally use the wrong one.
In SAP Commerce, frontend applications often retrieve the latest data by periodically requesting updates from the server. For instance, this could involve checking for new notifications every few seconds or refreshing a page every 30 seconds to display the most recent content. While straightforward to implement, this approach has notable drawbacks, including increased server load, unnecessary network traffic, and a suboptimal user experience due to update delays.
Over the past few weeks, Iβve found myself answering the same questions about my IntelliJ IDEA plugins repeatedly. Instead of explaining individually, Iβve put together this article as a comprehensive reference for anyone interested in it.
In some cases, it is more practical to use an indirect reference between itemtypes by utilizing a string attribute, which stores code/uid/etc. This approach is especially useful in situations where regular relation between itemtypes are not possible or efficient.
SAP Commerce automatically creates Swagger documentation for all endpoints, including both OOTB and custom ones, as well as those from OOTB extensions like βb2boccβ. The extensive number of OOTB endpoints can lead to a crowded Swagger interface, making it hard to navigate and find particular endpoint.
Many SAP Commerce projects are still using regular storefront approach, often incorporating modern frameworks like Vue.js and using default SAP Commerce build. Implementing parallel execution of FE and BE builds can lead to significant reductions in overall build time. Even for projects utilizing the OOTB Grunt build, parallelization can result in significant time savings. Furthermore, parallelization provides the valuable advantage of decoupling FE and BE builds, enabling developers to skip FE builds when focusing on BE development.
In some SAP Commerce setups, there is an unusual problem where web unit tests occasionally fail when run with a suppressed tenant. These tests encounter random failures while creating mock classes, resulting in exceptions like java.lang.NoClassDefFoundError: Could not initialize class org.mockito.codegen.
With Solr 8βs support ending in June 2024, itβs crucial for local environments to transition to Solr 9. Unlike cloud installations of SAP Commerce (where you can easily switch Solr versions via manifest.json), local setups encounter difficulties in switching between Solr versions.