Hello!

Recently listening to the podcast Agile for humans that I often listen to, as I like to understand different aspects of software development. In both hosts have a series in which they answer questions from the audience, usually the episodes are fast and to the point, without much details or talking through the subject. The episode “YDS: Should the Scrum Events Be Entertaining?” was a mix of bouncing ideas (in the short time both of them had) and trying to focus on an outcome for the audience and the conclusion was a straight: “they should be effective”. In that sense,...

As I navigate towards other approaches of testing software, I see that there are some arguments in favor of testability. For example, cucumber names ports and adapter as a testable architecture [1]. In the fourth edition of the book “software architecture in practice” the chapter 12 dedicated to tstability elaborates on what might be a testable architecture and list its attributes rather than name a single architectural style. The importance of listing attributes depicts a broader picture which leads to other architectures also being labeled as “testable” besides the ports and adapters. In short, what the book depicts is a...

The javascript ecosystem provides a variety of tools and frameworks that sometimes require some configuration dancing to work together. Jest has been the dominating player for running javascript tests, it provides a end-to-end experience in regards of features, for example, you don’t need to configure a test runner and also the assertion library. Even though, such thing is possible to do if needed. Jest works across libraries and frameworks, React packs Jest into automatically when creating a project using Create-React-App. Besides, Jest also works with applications that are run in the server side. Such popularity was questioned by vitest, an...