The exersice here is about trying to identitfy code smells and then apply refactor techniques, if you run tests you will see some suggestions (as "statement method smells as long method (>20 lines), try extract method"). Agree it is not very clear, but you could use some refactor catalog as help (https://sourcemaking.com/refactoring/smells).

As 1st step you may try to reduce #of lines on statement method by using extract method (https://sourcemaking.com/refactoring/extract-method). Please let me know if you have any question.

regards,

Thanks for your feedbak, I really appreciate and takes in order to improve test cases, now they verify code doesn't have bad smells ;)

Thanks for your feedbak, I really appreciate and takes in order to improve test cases, now they verify code doesn't have bad smells ;)

Thanks for your feedbak, I really appreciate and takes in order to improve test cases, now they verify code doesn't have bad smells ;)

thanks for sharing this reference! I can't access to your example, do you have some documentation regarding how to retrieve code? I was looking for a while, but did't found how to do that

aha! I understood now what you are proposing!! Yes, there is no easy way to validate that code was changed and improved. Thanks for explain that, i just updated description.

Sorry, I don't understand your comment. But maybe I didn't exaplin well, this one is a refactoring exersice, you don't have to write test, just improve code by using refactoring catalog ;) so test are just passing.

Thanks for writting! I am new using this tool, not sure what is best for this kind of exercise (kata / kumite) or if I used it well.

Sorry, maybe I didn't exaplin well, this one is a refactoring exersice, you don't have to write test, just improve code by using refactoring catalog ;)