Automated testing with phpunit
This presentation is the property of its rightful owner.
Sponsored Links
1 / 32

Automated Testing with PHPUnit PowerPoint PPT Presentation


  • 187 Views
  • Uploaded on
  • Presentation posted in: General

Automated Testing with PHPUnit. How do you know your code works?. Manual Testing. Type in a value Submit the form Check by eye. Manual Testing. Tedious Time Consuming Error Prone Did you test everything? Consistently?. Automated Testing. Have the computer run your tests.

Download Presentation

Automated Testing with PHPUnit

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Automated Testing with PHPUnit


How do you know your code works?


Manual Testing

  • Type in a value

  • Submit the form

  • Check by eye


Manual Testing

  • Tedious

  • Time Consuming

  • Error Prone

    • Did you test everything?

    • Consistently?


Automated Testing

Have the computer run your tests


Pro: Confidence

Know that your code does what it needs to

Know that your code doesn’t break anything that used to work

Regression Testing


Con: Testing isn’t free

  • Writing tests takes time

    • Response: So does manual testing

  • Mo Code Mo Problems

    • Response: It’s a worthwhile investment


Unit Testing

Automated testing one unit at a time


What is a unit?

Module (procedural programming)

Class (OOP)


Breaking Down Unit Tests

  • Test Suite composed of

  • Test Case Classes each of which have

  • Test Methods which make 1 or more

  • Assertions


A Unit Test Asserts That A Unit Of Code Performs To A Specification


XUnit Frameworks

Help


XUnit Frameworks Provide

  • Assertions

  • Calls Test Methods

  • Help Setup

  • Test Cases

  • Test Runners


Assertions

  • Code to verify that expected and actual values match

  • Often methods starting with “assert…()” or “refute…()”

  • Used by the developer

  • $this->assertTrue()

  • $this-> assertFalse()

  • $this-> assertEquals()


Calls Test Methods

  • Knows to call your code which tests a particular condition, method, or other “sub unit”

  • Methods usually begin with “Test…()”

  • Written by the developer

  • class … {

    • public function test…()

    • {

    • }

  • }


Help setUp and tearDown

  • Offers special functions that get called before and after each test.

  • Written by the developer

  • class … {

  • public function

    • setUp() {…}

    • public function tearDown() {…}

  • }


Unit Test Life Cycle


Test Case

  • A class with test methods

  • Usually offers assert methods

  • Extended by the developer

  • class MyTestextends PHPUnit_Framework_ TestCase

  • {

  • }


Provide Test Runners

Code that makes executing tests simple

Often a command-line tool

(useable by IDE)


Test First or Test Last?


Test First

Test Driven Development (TDD)


Testing Cycle


Find Problems Early

How should your code work?

What do the requirements mean?


Manage Scope Creep

Do The Simplest Thing That Could Possibly Work

YAGNI

Know when you’re done: All tests are green.


Test Last

Problematic

Tests become biased for the code you already wrote


What don’t you test?


Don’t Test the Language/Framework

  • Don’t test session session initiaiton

  • Or $_POST/$_GET/etc.

  • Or anything provided by PHP (and/or your framework,

  • $_POST[“loggedIn”] = true;

  • $this-> assertTrue($_POST [“loggedIn”])

  • # Wrong!


Don’t Test Methods Without Logic

  • class … {

  • private $foo;

  • public get_foo() {

  • return $this->foo;

  • }

  • }


What to Test


Boundaries

  • function … {

    • if ($foo > 3) {

    • // test whether execution goes in here

    • }

    • else {

    • // test whether execution goes in here

    • }

  • }


Invalid values

  • 0

  • Negative values

  • Empty strings

  • Very long strings (>500chars)


What’s a good test?

  • Repeatable

    • Use setUp() to make sure everything is right for your test

  • Independent

    • UsetearDown() to clean up

  • Thorough

    • It’s ok to have more than one test method in your case… in fact it’s often necessary!


  • Login