This document provides an introduction to using PhpSpec for test-driven development (TDD). It explains what TDD is, the benefits of TDD, and why PhpSpec is a good choice for TDD in PHP projects. It then walks through setting up a PhpSpec project, describing a sample Blog class, writing examples to test the Blog class, running the tests, refactoring code, and using PhpSpec matchers. The document concludes with tips on using PhpSpec to design object interactions and collaboration.

1. Practical intro to using PhpSpec
Dave Hulbert
@dave1010

2. Hello
O/

3. Dave Hulbert
@dave1010 @wearebase @phpdorset

4. Contents
● Part 1: TDD in 60 seconds
● Part 2: PhpSpec setup
● Part 3: Using PhpSpec

5. What is TDD?
1) Write a failing test (red)
2) Write the minimum amount of code to pass the test
(green)
3) Refactor (restructure code, without changing its
behaviour)

6. Why TDD?
● Don't write code that isn't needed
● Write fewer bugs
● Write more maintainable code
● Be more productive

7. PhpSpec!

8. Why PhpSpec?
● Modern
● Nicer API than PHPUnit
● More helpful
● Encourages better code

9. PhpSpec is not
● For legacy code
● For acceptance tests
● For functional / UI / integration tests

10. $ mkdir phpspec-demo
$ cd phpspec-demo
$ composer require --dev phpspec/phpspec
$ alias spec=./vendor/bin/phpspec
Setup

11. $ vim composer.json
$ cat composer.json
{
"require-dev": {
"phpspec/phpspec": "^2.3"
},
"autoload": {
"psr-0": {"": "src"}
}
}
$ mkdir src
$ composer update --lock
Setup

12. $ spec list
...
Available commands:
describe Creates a specification for a
class
help Displays help for a command
list Lists commands
run Runs specifications
Features

13. Blog example

14. $ spec desc Blog
Specification for Blog created in
/home/dave/phpspec-demo/spec/BlogSpec.php.
Write a spec

15. Empty spec

16. Run the spec

17. Code generation

18. Code generation

19. Write 1st example in BlogSpec

20. Run it

21. Failing test (red)

22. 100% generated code

23. Passing example

24. Green

25. Refactor
● Rename method/variable
● Extract/inline method/variable
● Replace loop with collection
● Replace conditional with polymorphism
● Replace inheritance with delegation

26. Blogs need some Posts

27. Give the blog some posts

31. Tell Blog about PostRepository

32. Make it pass

33. PhpSpec Matchers
shouldReturn('hello')
shouldThrow(Exception::class)
->duringSetCount(-1)
shouldHaveType(User::class)
shouldHaveCount(3)
shouldBeString()
shouldBeInt()
shouldBePublished() → isPublished()
shouldHaveContent() → hasContent()

34. Stub
Used to provide data
Messages coming into the
system under specification (SUS)

35. Stubs vs Mocks / Spies

36. Mock / Spy
Used to match behaviour
Messages coming out of the SUS

37. Talking to other objects

38. Talking to other objects

39. Stubs vs Mocks / Spies

40. Pro tips
●
Use interfaces if you want to talk to collaborators
● Refactor the SUS and the specs
●
Don't be afraid to delete specs when they're not helpful
● Painful to spec means you have a bad design
●
Use PhpSpec to design how objects talk to each other (internal
behaviour)
●
Use PHPUnit to write tests (eg integration)
●
Use Behat to specify external behaviour

41. Thanks!
Questions / comments
@dave1010