"you should not care what I call E2E test. You should have an agreement in your team what you call E2E tests" Aki Salmi at #dddeurope
Someone asked after the session "in your experience, when it should be one shape or another?" => It depends on the type of the responsibility of your domain. If it is process-heavy, going from one state to another, you want to make sure that all the pieces work well together and will have not too much domain logic to test. If the domain logic is heavy on calculations, you will want to have more classic unit tests, of course.
@yellowbrickc
“OR” is not the only available “Logic gate”.
“AND”, “XOR” and many others may also be appropriately and contextually applied.
@dahukanna yes. It is a contextual thing depending on different factors. Even if it is interesting to hear about the different experiences, the question itself "am I doing wrong if my test strategy has a different shape" is not important. The most important message I think, Aki wanted to tell was: don't constrain yourself by rules, test everything as it would be a unit.
It would be so nice to include Aki in this discussion, I haven't managed to find him after his talk. @sofiakat can you share the right handle 🙏?
@yellowbrickc thank you for asking. His handle is @rinkkasatiainen . Let me know if it doesn’t work out for some reason.
@sofiakat the only reason was that I could not manage to find it 😂.
Hello @rinkkasatiainen 👋
@yellowbrickc @sofiakat hello! 👋 And yes, I use the model in giving me guidance on how would I approach a given situation. In a way where I don’t couple tests with inplementation too tightly. And it has helped me, and my teams a lot during past years.
@rinkkasatiainen @sofiakat And I will use your model starting next week to explain why and how we should address this topic, instead of discussing about names and "why not"'s. "Draw your box in your ownership and apply this thinking model" 🙂