El video de la charla: https://www.youtube.com/watch?v=f8Qaqbxu0J0
Mi experiencia sobre testing, continous integration y continous delivery en diferentes proyectos y empresas. Si tenéis alguna pregunta, no dudéis en escribirme a roc@fewlaps.com
9. we started with unitary tests to
develop regular expressions
given
when
then
given
when
then
10. we started with unitary tests to
parse deeplink URL’s
this happens at
11. we started with unitary tests to
parse deeplink URL’s
this happens at
12. we started with unitary tests to
parse deeplink URL’s
this happens at
13. we started with unitary tests to
improve an invoice generator
Customer can have a insurance… or not
The insurance can have a coverage limit… or not
The insurance can have a franchise deductible… or not
The insurance company can pay the VAT of the amount… or not
14. we started with unitary tests to
improve an invoice generator
15. we started with unitary tests to
improve an invoice generator
16. we started with unitary tests to
refactor legacy code
this happens at
17. we started with unitary tests to
refactor legacy code
Sandro Mancuso
craftedws.blogspot.com
Testing and Refactoring Legacy Code
youtu.be/_NnElPO5BU0
Legacy Code Rules
• You cannot change production code if not covered by tests
… just automated refactorings (via IDE) are allowed, if needed to write the test
this happens at
18. we started with unitary tests to
refactor legacy code
Sandro Mancuso
craftedws.blogspot.com
Testing and Refactoring Legacy Code
youtu.be/_NnElPO5BU0
this happens at
19. last tips about unitary tests
follow the given-when-then style
test one thing at a time
test the domain: is easy and valuable
frustration is the first step towards improvement
know the tools: JUnit + AssertJ + Mockito
24. we started with instrumentation test to
test an app end to end
this happens at
25. we started with instrumentation test to
test an app end to end
this happens at
26. we started with instrumentation test to
test an app end to end
this happens at
27. tips about instrumentation tests
simple way to do «defensive testing»
fast way to develop «deep screens»
Espresso has been a game changer
They use to fail at CI tools
39. we started with continous delivery to
launch releases from SourceTree
Group of Betatesters 0,5% of users
this happens at
quit smoking with your phone
40. we started with continous delivery to
update stakeholders
the product owners have
the last developed feature
in their phones
this happens at
41. we started with continous delivery to
launch releases from Terminal
Group of Betatesters Alpha Release
this happens at