The document discusses reversing the traditional tests pyramid for legacy code. It proposes starting with end-to-end tests to give courage for refactoring code into testable units. This establishes a reversed tests pyramid to gradually introduce a new architecture. The goal is to keep technical debt low by refactoring and removing duplicated tests to improve software quality and the ability to change the system. Beware of refactoring just for its own sake and resist rewriting from scratch.
37. Few final thoughts...
●
●
●
●
●
Beware of refactoring just for refactoring!
Resist temptation to re-write from scratch – history is against you,
such projects usually fail.
Remember to always remove your (duplicated) tests!
Software quality in many cases could be understood as ability to
introduce changes into software!
Keep your technical debt as low as possible and try to pay it back
every time you can. For example use your slack time for that!
Resist temptation to re-write from scratch – history is
against you, such projects usually fail.
38. Few final thoughts...
●
●
●
●
Beware of refactoring just for refactoring!
Resist temptation to re-write from scratch – history is against you,
such projects usually fail.
Remember to always remove your (duplicated) tests!
Software quality always remove be understood as ability to
Remember to in many cases could your (duplicated) tests!
introduce changes into software!
●
Keep your technical debt as low as possible and try to pay it back
every time you can. For example use your slack time for that!
39. False positive or false negative safety
net is even worst than
lack of a safety net...
40. ●
Software quality in many cases could be understood as
ability to introduce changes into software!