Test Automation at FiNC

Presentation about software quality, testing and static code analysis.

Transcript

1. TEST AUTOMATION AT FiNC
2. DANIEL LOPEZ PRAT daniel.lopez@finc.com 6temes daniel.tokyo https://blog.6temes.cat
3. HOW DO YOU FEEL WHILE DEVELOPING?
5. WHY FEAR IS BAD? ▸ Fear will make you do overcomplicated things ▸ Fear will litter your code with `try()` ▸ Fear will kill your creativity ▸ Fear will make you slow ▸ Fear is really bad for a StartUp
6. FEAR ➞ CONFIDENCE ➞ SPEEDY ▸(Good) Tests ▸Static code analysis
7. TESTING
8. VALIDATOR - REGULAR EXPRESSION
9. VALIDATOR - MOCK AND HAPPY PATH
10. VALIDATOR - SAD PATH
11. MODEL - WHAT TO TEST
12. MODEL - TESTS
13. SERVICE
14. SERVICE - TEST
15. SERVICE - TEST
16. UNIT TESTS ▸ Models ▸ Validations ▸ Service classes ▸ Tests algorithms ▸ Write tests, don’t use the console! ▸ Exhaustive
17. CONTROLLER METHOD
18. CONTROLLER TEST - HAPPY PATH
19. CONTROLLER TEST - SAD PATH
20. FUNCTIONAL TESTS ▸ Controllers. ▸ Don't test too much! How many paths does your method have? Don't test by proxy. ▸ Use Factory Girl when necessary. Build instead of create. Use mocks. Create support methods! ▸ Main characteristic: Focus
21. SIMPLE INTEGRATION TEST
22. MORE COMPLEX INTEGRATION TEST
23. INTEGRATION TESTS ▸ Use Capybara with Rspec ▸ Make life of QA department easier. ▸ Strategy: ▸ Make a list with all the features of the application that need to be checked after each deploy. ▸ Automate as much as possible. ▸ Write declarative code using helpers
24. SMOKE TEST
25. SMOKE TEST
26. SMOKE TEST ▸ Loads all the routes and checks that they respond correctly ▸ Ideally, all the routes should be covered by an integration test ▸ In the real world, smoke tests can save your day.
27. STATIC CODE ANALYSIS
28. RUBOCOP
29. RUBOCOP ▸ Please, don't spend time in code reviews arguing about commas or indentations! ▸ Cyclomatic Complexity, Perceived Complexity, AbcSize make a lot of sense.... Most of the time. ▸ You are allowed to disable a cop for a method. But don’t do it! ▸ You don't want to use a custom configuration. Our application is not that special. Exception: Line length to 110 lines as a hard limit but try to stick to 80.
30. SIMPLECOV
31. SIMPLECOV
32. SIMPLECOV
33. SIMPLECOV ▸ Shows code coverage of the application ▸ Shows the number of times each line of code has been executed during tests. ▸ Helps to identify which path have not been covered by tests.
34. BRAKEMAN Image from Brakeman documentation
35. BRAKEMAN ▸ Rails security scanner ▸ Analyse code to find security flaws ▸ Sometimes will generate false positives. This false positives can be added to a ignore file… or the code can be rewritten in a way that does not offend brakeman.
36. RUBYCRITIC
37. RUBYCRITIC
38. RUBYCRITIC
39. RUBYCRITIC ▸ Uses different static code analysis tools in order to offer an objective(~ish) measure of code quality. ▸ Reek: detects code smells ▸ Flay: detects code duplication ▸ Flog: outputs an scalar value representing the complexity of the code. ▸ Useful to find candidates to refactor and to find out if a PR is improving or worsening the quality of the code.
40. EXECUTE ON PULL REQUESTS
41. SOME WORDS ABOUT BEAUTY
42. WHAT IS BEAUTY?
46. ▸ Composition ▸ Balance ▸ Leading Lines ▸ Framing ▸ Foreground and Background ▸ Patterns
47. ▸ Harmony ▸ Form ▸ Scales and progression ▸ Flow ▸ Foreground and Background ▸ Patterns
48. ▸ Structures ▸ Abstractions ▸ Separation of Concerns ▸ Background (Infrastructure Logic) vs Foreground (Business Logic) ▸ Patterns
49. TRUST THE BEAUTY
50. FIND THE BEAUTY
51. THANKS!
52. QUESTIONS?