One of the most effective things you can do in your SAP Commerce project is to build up a profound integration tests suite. I want to emphasise that by integration tests, I specifically mean the tests extending from ServiceLayerTransactionalTest and hitting your full spring config as well as the junit tenant database. Doing it the right way is a separate topic.
I am not a fan of massively mocked unit tests and specifically not in a hybris environment. I have many reasons for that and will discuss it in a separate post.
Back to the topic, yes you heard that right, you can compile and rerun your integration tests without restarting the SAP Commerce platform. This works with two things combined. …
In the following series of articles I want to tell about my experience and the best practices I discovered and/or introduced in react.js projects.
Everything I will present is based on at least 3 mid size completed projects. Its bullet proof by countless code reviews and on boarding of many colleagues, who were productive in the code base right away.
Its known react is just a library. If we would map it to the most known design pattern MVC then it would be the V(iew) + some ability to trigger controller actions, who can exist on the view itself.
If we add redux to the stack we usually follow the official flux architecture.
So framework wise we cover the MVC functionality and unfortunately this is still not the complete picture. To make an example this are the parts of the logic that are not mentioned in the flux architecture. The structure for the rest of logic is open for the team to decide. …