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.

1. Test Driven Development - TDD
with RSpec

2. About me
• Rachid Calazans 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 is it?

4. • It's a software development process;
• Began in the 90s by Kent Beck;
• It’s the practise of test and design;

5. Is Simply That

6. Advantages
• Your project is covered by a suite of automated tests;
• Loss of fear of changing the code;
• Improvement in your code design;

7. How does it work?

10. RSpec, What’s it?

11. • Was born in 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 it work?

14. The Basics

15. Some Methods to Help
• describe();
• context();
• it();

16. describe()
• As the name says, describe the
behaviour;
• Can receive any kind of object;
• Can pass a second parameter;

17. Example

18. context()
• Does the same thing as describe();
• But is used to describe the context;

19. Example

20. it()
• Specifies an example of code;
• Can or cannot define the expectations
from the object or the behaviour;

21. Example

22. Hooks
• before();
• after();

23. before() | after()
• Both accept the same parameters:
• - :all;
• - :each;
• - :suite;

24. Example

25. Expectations
Has a lot of 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 enjoyed it! What else?

27. A lot of things… :)

28. Advantages
• Could use User stories;
• Build a nice documentation even when running the tests;
• Easy to understand and implement the tests;

29. Example of the documentation
When will run the tests just add:
- -format documentation
Voila

30. Thanks!

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