Download to read offline
Uploaded byRachid Calazans
TDD with RSpec
This document provides an overview of test driven development (TDD) and the RSpec testing framework in Ruby. It defines TDD as a software development process that was created in the 1990s to practice test-first design. RSpec is introduced as a popular testing framework for Ruby that supports behavior driven development (BDD). The basics of RSpec are explained, including the describe, context, and it methods for organizing tests and defining examples. Hooks and expectations are also summarized.
TDD with RSpec
- 1. Test Driven Development- TDD with RSpec
- 2. About me • RachidCalazans de Viveiros • Working at Piggo • Graduated in Systems Analysis - CESMAC - 2011 • Post-Graduated in Mobile Application Development for Technology (CESAR.edu - PE) • Addicted to Tests • Facebook: rachid.calazans • E-mail: rachidcalazans@gmail.com
- 3. TDD, What isit?
- 4. • It's asoftware development process; • Began in the 90s by Kent Beck; • It’s the practise of test and design;
- 5.
- 6. Advantages • Your projectis covered by a suite of automated tests; • Loss of fear of changing the code; • Improvement in your code design;
- 7. How does itwork?
- 10.
- 11. • Was bornin 2005 by Steven Baker, Dave Astels and Aslak Hellesoy; • It’s a popular test framework in Ruby world; • Behaviour Driven Development - BDD;
- 12. How does itwork?
- 14.
- 15. Some Methods toHelp • describe(); • context(); • it();
- 16. describe() • As thename says, describe the behaviour; • Can receive any kind of object; • Can pass a second parameter;
- 17.
- 18. context() • Does thesame thing as describe(); • But is used to describe the context;
- 19.
- 20. it() • Specifies anexample of code; • Can or cannot define the expectations from the object or the behaviour;
- 21.
- 22.
- 23. before() | after() •Both accept the same parameters: • - :all; • - :each; • - :suite;
- 24.
- 25. Expectations Has a lotof types: • be / be_nil; • be_true / be_false; • be_instance_of / be_an_instance_of; • be_a / be_an / be_kind_of; • eq / eql / equal / ==; • change; • …
- 26. Nice, I enjoyedit! What else?
- 27. A lot ofthings… :)
- 28. Advantages • Could useUser stories; • Build a nice documentation even when running the tests; • Easy to understand and implement the tests;
- 29. Example of thedocumentation When will run the tests just add: - -format documentation Voila
- 30.
- 31. References • http://tableless.com.br/tdd-por-que-usar/ • http://agiledata.org/essays/tdd.html •http://searchsoftwarequality.techtarget.com/definition/test-driven-development • http://en.wikipedia.org/wiki/Test-driven_development • http://betterspecs.org/br/ • http://rspec.info/ • http://blog.teamtreehouse.com/an-introduction-to-rspec • http://pivotallabs.com/testing-strategies-with-rspec/ • rspec-quickguide • Cucumber e Rspec - Construa aplicações Ruby com testes e especificações
Editor's Notes
- #5 TDD é o desenvolvimento de software orientado a testes; Kent Beck escreve em Smalltalk sua primeira biblioteca de testes, o SUnit; A ideia inicial dele era facilitar a execução de testes de software, automatizando essa tarefa que muitas das vezes era feita manualmente; TDD não é considerado apenas uma prática de teste, mas sim uma prática de design.
- #6 - O fluxo do TDD se dá o nome de Red-Green-Refactor;
- #12 BDD é uma extensão do TDD; - Em BDD, um desenvolvedor, algum profissional do setor de qualidade ou até mesmo o cliente podem esclarecer os requisitos quebrando-os em exemplos específicos.