I offer a Workshop on Testrecorder at XP-Days 2017. Everyone that visits the session, will be presented a refactoring of selected “Legacy Code”-projects following the method:
- Record (Capture some Tests)
- Refactor (Simplify the Code)
- Replay (Execute the Tests)
After Presenting at Karlsruher Entwicklertag it is time to write a few words about the future of Testrecorder …
Testrecorder is a Java tool vor recording runtime situations. Recording means, that we intercept method invocation and capture the state before and after the invocation. From this captured state we generate JUnit-tests.
Which is your naming convention for implementation classes? Do your prefer
Intrinsically I should be pleased about this question – at least someone seems to care about naming conventions … but sorry, both conventions are little more than crap. Unfortunately these patterns are very popular, so my criticism will have little effect. Here you are: