PHPUnit from a developer's perspective

PHPUnit from a developer's perspective

• 1.
  PHPUnit A developer'sperspective By Tushar Joshi, Nagpur Presented at: 19 June 2010, 4pm, PHPMeet Nagpur #ngpphpmeet
• 2.
  Assumptions for thispresentation No earlier knowledge of PHPUnit
• 3.
  PHP Developers
• 4.
  Knowledge of ObjectOriented Programming
• 5.
  Things covered Conceptualintroduction to PHPUnit
• 6.
  Discussion about needof unit testing
• 7.
  Case for PHPUnit
• 8.
  Demonstration of workingof PHPUnit (not part of slides but done side by side while presenting)
• 9.
  Things not coveredHistory of PHPUnit, history of unit testing frameworks
• 10.
  Installation of PHP,PHPUnit, PEAR, Xdebug, NetBeans IDE
• 11.
  Configuration of thedevelopment environment
• 12.
  Detailed usage ofPHPUnit, all cases which can be tested
• 13.
  Are there anybugs? Developer says: I have checked the code many times
• 14.
  There cannot beany bugs now
• 15.
  Manager believes thefirst time Courtesy: Sam Fraser - Smith
• 16.
  Client sends issuesDeveloper says: Oops, I don't know how I slipped that one
• 17.
  Never thought thatvalue will be passed to this function
• 18.
  Next time managerwill be skeptical to believe easily Courtesy: cheerfulmonk
• 19.
  Introducing PHPUnit Toolto unit test your PHP code
• 20.
  To re-test thecode after any modifications
• 21.
  Tool to ensureyour code always work for given inputs Can be used for Object Oriented PHP code
• 22.
  Is PHPUnit Easy?You cannot use the tool unless you know it
• 23.
  Learning a toolis a skill building activity
• 24.
  Assuming you knowthe tool, it will save you always PHPUnit is written in PHP
• 25.
  You know PHP
• 26.
  PHPUnit Overhead? Developerstool to verify his code
• 27.
  No need toshow test classes if not needed
• 28.
  If tool isreadily available, it is a matter of habit Peace of mind
• 29.
  Way to proveyour code works in all situations
• 30.
  Opportunity to traphidden bugs before client finds them
• 31.
  Life Saver
• 32.
  Case for PHPUnitWhat will you choose between Text Editor
• 33.
  Syntax highlighting editorwith context help and intelli-sense (CTRL+SPACE) What will you choose between Testing methods by eyes
• 34.
  Testing by atool, with advanced facilities
• 35.
  Sample PHP classLet us test this class
• 36.
  Starting with getBalancemethod
• 37.
  Opportunity to thinkbehavior of getBalance
• 38.
  Test Class
• 39.
  Result Red orGreen Sample Test
• 40.
  Available Assertions
• 41.
  Using Constraints $this->lessThan(3000)
• 42.
  This creates aconstraint expectation
• 43.
  $this->assertThat checks whetherthe value is according to the expectation
• 44.
  Available Constraints
• 45.
  Testing Exceptions @expectedException
• 46.
  To check whetherexception was thrown
• 47.
  Data Providers Wayto create multiple data sets
• 48.
  Sets of parametersfor which the function must run correctly
• 49.
  Reduces effort forwriting multiple test methods
• 50.
  Mock Objects andExpectations Quickest way to test dependencies
• 51.
  $object = $this->getMock('NameOfClass');
• 52.
  $object ->expects( invocationExpectation ) ->method( methodExpectation ) [->with( parameterExpectation )] [->will( returnValue Expectation)]
• 53.
  Available Invocation Expectations$this->any() - example
• 54.
  Parameters and ReturnValues Used with the with and will methods of mock object
• 55.
  $this->equals(val) type ofconstraints
• 56.
  $this->onConsecutiveCalls(val, val2, val3,..)List of values which will be used for each consecutive next call
• 57.
  Advanced Features VirtualFile System
• 58.
  DB testing withDBUnit
• 59.
  Mocking Web services
• 60.
  Testing for consoleoutput
• 61.
  References PHPUnit sitehttp://www.phpunit.de PHPUnit Manual http://www.phpunit.de/manual/3.5/en/index.html NetBeans IDE Site http://www.netbeans.org