Introduction to automated tests

Transcript

1. Introduction to Automated Tests Gabriel Sobrinho
2. GABRIEL SOBRINHO gabrielsobrinho.com github.com/sobrinho speakerdeck.com/sobrinho
3. hite.com.br
4. Concepts
5. TDD BDD Unit Tests Integrated Tests Acceptance Tests Coverage Test Ratio Human Tester Test Automation
7. Human Tester
8. Human Tester Normally done by the QA department, a person who exercises the software
11. Automated Tests
12. Automated Tests In software testing, a software that compares actual outcomes with predicted outcomes
13. Automated Tests • Ensure code quality • Avoid regressions • Reduce maintenance cost • Code and behavior documentation
14. Automated Tests def sum(a, b) a + b end
15. Automated Tests if sum(1, 2) == 3 puts 'okay' else puts 'error' end
16. Automated Tests $ ruby calc.rb okay
17. Automated Tests if sum(0.1, 0.2) == 0.3 puts 'okay' else puts 'error' end
18. Automated Tests $ ruby calc.rb error
20. Test-Driven Development
21. Test-Driven Development Write tests before the code itself to get fast feedback
22. Test-Driven Development Red-Green-Refactor Cycle
23. Test-Driven Development Recommended by XP community
24. https://bitbucket.org/spooning/
25. Test-Driven Development if sum_all([1, 2, 3]) == 6 puts 'okay' else puts 'error' end
26. Test-Driven Development $ ruby calc.rb calc.rb:1:in `<main>': undefined method `sum_all’ for main:Object (NoMethodError)
27. Test-Driven Development def sum_all end
28. Test-Driven Development $ ruby calc.rb calc.rb:1:in `sum_all’: wrong number of arguments (given 1, expected 0) (ArgumentError) from calc.rb:4:in `<main>'
29. Test-Driven Development def sum_all(numbers) end
30. Test-Driven Development $ ruby calc.rb error
31. Test-Driven Development def sum_all(numbers) total = 0 numbers.each do |number| total += number end total end
32. Test-Driven Development $ ruby calc.rb okay
33. Test-Driven Development def sum_all(numbers) total = 0 numbers.each do |number| total += number end total end
34. Test-Driven Development def sum_all(numbers) numbers.reduce(:+) end
35. Test-Driven Development $ ruby calc.rb okay
36. Test-Driven Development Red-Green-Refactor Cycle
38. Behavior-Driven Development
39. Behavior-Driven Development BDD is a subset of TDD that enforces the story telling format to be clear about the expectations
40. Behavior-Driven Development TDD focuses on each and every unit test for every function, doesn't matter what it does https://softwareengineering.stackexchange.com/a/224102
41. Behavior-Driven Development BDD focuses on software that matters https://softwareengineering.stackexchange.com/a/224102
42. Behavior-Driven Development class TestCalculator < Test::Unit::TestCase def test_sum_all assert sum_all([1, 2, 3]) == 6 end end
43. Behavior-Driven Development describe '#sum_all' do it 'sums the given numbers' do expect(sum_all([1, 2, 3])).to eq 6 end end
44. Behavior-Driven Development Failures: 1) #sum_all sums the given numbers Failure/Error: expect(sum_all([1, 2, 3])).to eq 6 NoMethodError: undefined method `sum_all’ for #<RSpec::ExampleGroups::SumAll:0x007f8d5fa49270> # calc.rb:5:in `block (2 levels) in <main>' Finished in 0.00052 seconds (files took 0.09426 seconds to load) 1 example, 1 failure
45. Behavior-Driven Development def sum_all(numbers) total = 0 numbers.each do |number| total += number end total end
46. Behavior-Driven Development $ rspec calc.rb . Finished in 0.00207 seconds (files took 0.09914 seconds to load) 1 example, 0 failures
47. Behavior-Driven Development def sum_all(numbers) numbers.reduce(:+) end
48. Behavior-Driven Development $ rspec calc.rb . Finished in 0.00085 seconds (files took 0.09119 seconds to load) 1 example, 0 failures
50. Unit Testing
51. Unit Testing Tests about the smallest piece of the software
52. Unit Testing - TDD class TestCalculator < Test::Unit::TestCase def test_sum_all assert sum_all([1, 2, 3]) == 6 end end
53. Unit Testing - BDD describe '#sum_all' do it 'sums the given numbers' do expect(sum_all([1, 2, 3])).to eq 6 end end
55. Integrated Testing
56. Integrated Testing Tests the connected pieces of the software like databases or APIs
57. Integrated Testing describe ZipCode do it 'returns the street information' do # Hits an API call zip_code = ZipCode.find('21510-140') expect(zip_code.number).to eq '21510-140' expect(zip_code.street).to eq 'Some Avenue' end end
59. Acceptance Testing
60. Acceptance Testing Tests if the software really works as the final customer or stakeholder expects it to work
61. Acceptance Testing Feature: Buy a product Scenario: Using a discount code Given I have a discount code When I buy a product using that code Then the total must include that discount
63. Artefacts
64. Ratio Artefact about how many line of tests there are for how many lines of code you have
65. Coverage Artefact about if the line of code was run or wasn’t run during the test suite
67. FAQ
68. What to test? Everything, from isolated code, to integrated pieces and to the entire system connected
69. How to test? By the collacteral effects that the application causes, not by the implementation itself
70. Write the tests before or after? Doesn’t matter after all, use the best for your project and team
71. Which methodology? Doesn’t matter after all, use the best for your project and team
72. Which test runner? Doesn’t matter after all, use the best for your project and team
74. Questions?
75. Thanks!
76. • http://www.devmedia.com.br/artigo-engenharia-de-software-3-a-importancia-dos-testes- automatizados/9532 • http://www.eduardopires.net.br/2012/06/ddd-tdd-bdd/ • http://tdd.caelum.com.br • https://cbabhusal.wordpress.com/2016/02/26/tdd-why-red-green-refactor-is-important-in-tdd/ • https://ciclosw.wordpress.com/2014/09/04/diferenca-entre-tdd-e-bdd/ • http://blog.locaweb.com.br/artigos/metodologias-ageis/diferenca-entre-bdd-tdd/ • https://www.infoq.com/news/2015/02/bdd-ddd • http://www.princiweb.com.br/blog/programacao/tdd/tdd-ddd-e-bdd-praticas-de- desenvolvimento.html • http://www.agileandart.com/2010/07/16/ddd-introducao-a-domain-driven-design/ References