30 Days of Automation in Testing Day 3: Explore "The Club" and Contribute

[joaofarias (João Farias)]

Three threads

Where would you start with automation in a micro services environment?

I thought in suggesting this same document Russel. As Martin Fowler himself says, architecture is the shared understanding of how things work. Communication is necessary for good architecture understanding. If we are in a well-known context, we can even move further with bad communication. However, when in enter in uncharted/complex territory, this understanding is necessary. Therefore, before thinking in tool X or strategy Y, I would think if the communication is effective: “Do I understa…

Automating the comparison of text files

Unix itself has a diff command: https://www.networkworld.com/article/2696092/operating-systems/unix---having-fun-with-diff.html And, naturally, you can chain the output into other Unix commands and do all kind of magic.

When should acceptance criteria be converted into automated tests

I would be with Uncle Bob (in “The Programmer’s Oath”) on this one: “3 - I will produce, with each release, a quick, sure, and repeatable proof that every element of the code works as it should.”. If the changes are generally well cover by non-business tests (unit, integration and component) and few bugs escape, one could postpone the “repeatable proof of work” to after the production code. Otherwise, for any reason, I would suggest that programmers take care of delivering them together with t…