1. UNIT &
INTEGRATION
TESTING
David Berliner

2. Why Test
Types of Tests
PHPUnit
Writing Tests
Getting Stuck In

4. WHY TEST?

5. TESTS REDUCE BUGS

6. TESTS REDUCE BUGS
TESTS ARE GOOD DOCUMENTATION

7. TESTS REDUCE BUGS
TESTS ARE GOOD DOCUMENTATION
TESTS ALLOW SAFE REFACTORING

8. TESTS REDUCE BUGS
TESTS ARE GOOD DOCUMENTATION
TESTS ALLOW SAFE REFACTORING
TESTS REDUCE THE COST OF CHANGE

9. TESTS REDUCE BUGS
TESTS ARE GOOD DOCUMENTATION
TESTS ALLOW SAFE REFACTORING
TESTS REDUCE THE COST OF CHANGE
TESTING FORCES YOU TO THINK

10. TESTS REDUCE BUGS
TESTS ARE GOOD DOCUMENTATION
TESTS ALLOW SAFE REFACTORING
TESTS REDUCE THE COST OF CHANGE
TESTING FORCES YOU TO THINK
TESTS REDUCE FEAR

11. A study conducted by Microsoft and
IBM showed that writing tests can
add 15% – 35% to development time
but reduce the number of bugs by
40% – 90%.
http://research.microsoft.com/en-us/groups/ese/nagappan_tdd.pdf

12. TYPES OF TESTS

13. Black Box
White Box
Unit
Integration
Functional
System
Regression
Performance
Smoke
Canary
Usability
A/B
…

14. Black Box
White Box
Unit
Integration
Functional
System
Regression
Performance
Smoke
Canary
Usability
A/B
…

15. UNIT TESTS
The goal of unit testing is:
1. to isolate each part of the program, and

16. UNIT TESTS
The goal of unit testing is:
1. to isolate each part of the program, and
2. show that the individual parts are correct.

17. UNIT TESTS
The goal of unit testing is:
1. to isolate each part of the program, and
2. show that the individual parts are correct.
Unit tests have a very narrow and well-defined scope.

18. UNIT TESTS
Pro’s:
1. Fast

19. UNIT TESTS
Pro’s:
1. Fast
2. Simple to understand

20. UNIT TESTS
Pro’s:
1. Fast
2. Simple to understand
3. Reliable

21. UNIT TESTS
Pro’s:
1. Fast
2. Simple to understand
3. Reliable
Con’s:
1. Large time investment

22. UNIT TESTS
Pro’s:
1. Fast
2. Simple to understand
3. Reliable
Con’s:
1. Large time investment
2. Requires maintenance

23. UNIT TESTS
A unit test should NOT:
1. Access the network

24. UNIT TESTS
A unit test should NOT:
1. Access the network
2. Hit a database

25. UNIT TESTS
A unit test should NOT:
1. Access the network
2. Hit a database
3. Use the file system

26. UNIT TESTS
A unit test should NOT:
1. Access the network
2. Hit a database
3. Use the file system
4. Call other non-trivial components

27. INTEGRATION TESTS
Test the inter-operation of multiple subsystems.
Pro’s:
1. Make sure nuts and bolts
fit together

28. INTEGRATION TESTS
Test the inter-operation of multiple subsystems.
Pro’s:
1. Make sure nuts and bolts
fit together
2. Test behaviour
and infrastructure

29. INTEGRATION TESTS
Test the inter-operation of multiple subsystems.
Pro’s:
1. Make sure nuts and bolts
fit together
2. Test behaviour
and infrastructure
3. (tested code) / test % is high

30. INTEGRATION TESTS
Test the inter-operation of multiple subsystems.
Pro’s:
1. Make sure nuts and bolts
fit together
2. Test behaviour
and infrastructure
3. (tested code) / test % is high
Con’s:
1. Hard to test all critical paths

31. INTEGRATION TESTS
Test the inter-operation of multiple subsystems.
Pro’s:
1. Make sure nuts and bolts
fit together
2. Test behaviour
and infrastructure
3. (tested code) / test % is high
Con’s:
1. Hard to test all critical paths
2. Harder to localise source
of errors

32. TEST HIERARCHY

34. PHPUnit

35. 1. Unit Testing Framework written in PHP by Sebastian Bergmann
2. De facto standard
3. Major Frameworks use it (Zend, Cake, Laravel, Symphony etc.)

36. Installation:
https://phpunit.de/manual/current/en/installation.html
Be sure to install xDebug in order to generate code coverage.
Note: PECL no longer supported

37. WRITING TESTS

38. ORGANISING TESTS
- The tests for class Foo are placed in a class FooTest
- Most of the time you will inherit from
PHPUnit_Framework_TestCase
PHPUnit_Extensions_Database_TestCase
- Tests are public methods named test*
- Inside the test methods, assertion methods such as
assertEquals() are used.

39. ORGANISING TESTS
Tests should mirror the code being tested.
SRC
SomeFolder
Baz.php
Foo.php
Bar.php
TEST
SomeFolder
FooTest.php
BarTest.php
BazTest.php

40. PHPUNIT.XML

41. BOOTSTRAP.PHP

42. ASSERTIONS
assertArrayHasKey()
assertClassHasAttribute()
assertClassHasStaticAttribute()
assertContains()
assertContainsOnly()
assertContainsOnlyInstancesOf()
assertCount()
assertEmpty()
assertEqualXMLStructure()
assertEquals()
assertFalse()
assertFileEquals()
assertFileExists()
assertGreaterThan()
assertGreaterThanOrEqual()
assertInstanceOf()
assertInternalType()
assertJsonFileEqualsJsonFile()
assertJsonStringEqualsJsonFile()
assertJsonStringEqualsJsonString()
assertLessThan()
assertLessThanOrEqual()
assertNull ( )
assertObjectHasAttribute()
assertRegExp()
assertStringMatchesFormat()
assertStringMatchesFormatFile()
assertSame()
assertStringEndsWi th()
assertStringEqualsFile()
assertStringStartsWi th()
assertThat()
assertTrue()
assertXmlFileEqualsXmlFile()
assertXmlStringEqualsXmlFile()
assertXmlStringEqualsXmlString()

43. ASSERTIONS

44. ANNOTATIONS @DEPENDS

45. ANNOTATIONS @DATAPROVIDER

46. ANNOTATIONS @EXCEPTIONS

47. What do you do if the code you want to test
is dependent on other components that
cannot be used in the test environment?

48. MOCKS & STUBS

49. DATABASE TESTING
Four stages of a DB test
1. Set up fixture
2. Exercise System Under Test
3. Verify outcome
4. Teardown

50. DATABASE TESTING (CONT) Give it a connection

51. DATABASE TESTING (CONT) Flat XML DataSet

52. DATABASE TESTING (CONT)

53. DATABASE TESTING (CONT)

54. GETTING STUCK IN

55. Demo:
https://github.com/manatok/talk-demo-ci

56. • db - Database Skel file and patches
• src - Project Code
• test/Output - Code coverage
• test/SportsBet - Projects Tests
• test/TestingCore - Uti l i ties
• tools - CI tools including ANT build
file