DOCSLIB.ORG

Sebastian Bergmann Phpunit Manual Sebastian Bergmann

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Sebastian Bergmann Phpunit Manual Sebastian Bergmann PHPUnit Manual Sebastian Bergmann PHPUnit Manual Sebastian Bergmann Publication date Edition for PHPUnit 6.5. Updated on 2017-12-07. Copyright © 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015 Sebastian Bergmann This work is licensed under the Creative Commons Attribution 3.0 Unported License. Table of Contents 1. Installing PHPUnit ..................................................................................................... 1 Requirements ........................................................................................................ 1 PHP Archive (PHAR) ............................................................................................ 1 Windows ..................................................................................................... 1 Verifying PHPUnit PHAR Releases ................................................................. 2 Composer ............................................................................................................. 4 Optional packages ................................................................................................. 4 2. Writing Tests for PHPUnit .......................................................................................... 5 Test Dependencies ................................................................................................. 5 Data Providers ...................................................................................................... 8 Testing Exceptions ............................................................................................... 12 Testing PHP Errors .............................................................................................. 14 Testing Output .................................................................................................... 15 Error output ........................................................................................................ 16 Edge cases ................................................................................................. 18 3. The Command-Line Test Runner ................................................................................ 20 Command-Line Options ........................................................................................ 20 4. Fixtures .................................................................................................................. 27 More setUp() than tearDown() ............................................................................... 29 Variations ........................................................................................................... 29 Sharing Fixture ................................................................................................... 29 Global State ........................................................................................................ 30 5. Organizing Tests ...................................................................................................... 33 Composing a Test Suite Using the Filesystem .......................................................... 33 Composing a Test Suite Using XML Configuration ................................................... 34 6. Risky Tests ............................................................................................................. 35 Useless Tests ...................................................................................................... 35 Unintentionally Covered Code ............................................................................... 35 Output During Test Execution ............................................................................... 35 Test Execution Timeout ........................................................................................ 35 Global State Manipulation ..................................................................................... 35 7. Incomplete and Skipped Tests .................................................................................... 36 Incomplete Tests ................................................................................................. 36 Skipping Tests .................................................................................................... 37 Skipping Tests using @requires ............................................................................. 38 8. Database Testing ...................................................................................................... 40 Supported Vendors for Database Testing ................................................................. 40 Difficulties in Database Testing ............................................................................. 40 The four stages of a database test ........................................................................... 41 1. Clean-Up Database ................................................................................... 41 2. Set up fixture .......................................................................................... 41 3–5. Run Test, Verify outcome and Teardown .................................................. 41 Configuration of a PHPUnit Database TestCase ........................................................ 42 Implementing getConnection() ....................................................................... 42 Implementing getDataSet() ............................................................................ 43 What about the Database Schema (DDL)? ....................................................... 43 Tip: Use your own Abstract Database TestCase ................................................ 43 Understanding DataSets and DataTables .................................................................. 45 Available Implementations ............................................................................ 45 Beware of Foreign Keys ............................................................................... 54 Implementing your own DataSets/DataTables ................................................... 54 The Connection API ............................................................................................ 55 Database Assertions API ....................................................................................... 56 Asserting the Row-Count of a Table ............................................................... 56 Asserting the State of a Table ........................................................................ 56 iii PHPUnit Manual Asserting the Result of a Query ..................................................................... 57 Asserting the State of Multiple Tables ............................................................. 58 Frequently Asked Questions .................................................................................. 59 Will PHPUnit (re-)create the database schema for each test? ............................... 59 Am I required to use PDO in my application for the Database Extension to work? .... 59 What can I do, when I get a “Too much Connections” Error? .............................. 59 How to handle NULL with Flat XML / CSV Datasets? ...................................... 59 9. Test Doubles ........................................................................................................... 60 Stubs ................................................................................................................. 60 Mock Objects ..................................................................................................... 65 Prophecy ............................................................................................................ 71 Mocking Traits and Abstract Classes ...................................................................... 71 Stubbing and Mocking Web Services ...................................................................... 72 Mocking the Filesystem ........................................................................................ 74 10. Testing Practices .................................................................................................... 77 During Development ............................................................................................ 77 During Debugging ............................................................................................... 77 11. Code Coverage Analysis .......................................................................................... 79 Software Metrics for Code Coverage ...................................................................... 79 Whitelisting Files ................................................................................................ 80 Ignoring Code Blocks ........................................................................................... 80 Specifying Covered Methods ................................................................................. 81 Edge Cases ......................................................................................................... 83 12. Other Uses for Tests ............................................................................................... 84 Agile Documentation ........................................................................................... 84 Cross-Team Tests ................................................................................................ 84 13. Logging ...............................................................................................................
Load more

Recommended publications
  • Codeigniter-Testing-Guide-Sample.Pdf
    CodeIgniter Testing Guide Beginners’ Guide to Automated Testing in PHP. Kenji Suzuki and Mat Whitney This book is for sale at http://leanpub.com/codeigniter-testing-guide This version was published on 2016-01-23 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. © 2015 - 2016 Kenji Suzuki and Mat Whitney Tweet This Book! Please help Kenji Suzuki and Mat Whitney by spreading the word about this book on Twitter! The suggested hashtag for this book is #CITestGuide. Find out what other people are saying about the book by clicking on this link to search for this hashtag on Twitter: https://twitter.com/search?q=#CITestGuide Contents Preface ............................................... i The Book at a Glance ..................................... i What You Need for This Book ................................. iii Who should read This Book? ................................. iii Why PHPUnit? ........................................ iv Is This a CodeIgniter Book? .................................. iv Is Testing PHP Applications Difficult? ............................ iv Is Testing CodeIgniter Applications Difficult? .................... v Testing is Fun and Easy ................................ v Conventions Used in This Book ................................ v Errata .............................................
    [Show full text]
  • Towards a Taxonomy of Sunit Tests *
    Towards a Taxonomy of SUnit Tests ? Markus G¨alli a Michele Lanza b Oscar Nierstrasz a aSoftware Composition Group Institut f¨urInformatik und angewandte Mathematik Universit¨atBern, Switzerland bFaculty of Informatics University of Lugano, Switzerland Abstract Although unit testing has gained popularity in recent years, the style and granularity of individual unit tests may vary wildly. This can make it difficult for a developer to understand which methods are tested by which tests, to what degree they are tested, what to take into account while refactoring code and tests, and to assess the value of an existing test. We have manually categorized the test base of an existing object-oriented system in order to derive a first taxonomy of unit tests. We have then developed some simple tools to semi-automatically categorize tests according to this taxonomy, and applied these tools to two case studies. As it turns out, the vast majority of unit tests focus on a single method, which should make it easier to associate tests more tightly to the methods under test. In this paper we motivate and present our taxonomy, we describe the results of our case studies, and we present our approach to semi-automatic unit test categorization. 1 Key words: unit testing, taxonomy, reverse engineering 1 13th International European Smalltalk Conference (ESUG 2005) http://www.esug.org/conferences/thirteenthinternationalconference2005 ? We thank St´ephane Ducasse for his helpful comments and gratefully acknowledge the financial support of the Swiss National Science Foundation for the project “Tools and Techniques for Decomposing and Composing Software” (SNF Project No.
    [Show full text]
  • YOSSEF BENHAROSH RESUME 972 (0) 544-308209 | [email protected] | Kiryat Gat, Israel
    YOSSEF BENHAROSH RESUME 972 (0) 544-308209 | [email protected] | Kiryat Gat, Israel PHP & Drupal developer, June 2011 – present Freelance web developer for 4 years who works with the following technologies: PHP, MySQL, Javascript, jQuery, Drupal, HTML/HTML5, CSS/CSS3. Specializes in PHP development. Including: Object-Oriented Programming, mySQL as a data base, and Laravel as a framework. Drupal developer, specializing in developing new modules and themes, and in taming existing modules. Good working knowledge of organic SEO. Chosen works freefax.co.il – PHP site that provides fax services. I worked as a PHP and mySQL programmer, as well as on the front end with jQuery, Ajax, html and CSS. I wrote the cart and invoice modules and the user class. puzzlemedia.co.il – Bilingual Drupal website for film producers. www.yaronlivne.co.il – Drupal based app that I wrote most of its modules and developed its’ theme. ZEZBRA – A startup that I themed its Drupal site, as well as developed its PHP based cellular version. reshetech.co.il – Hebrew tutorials website based on PHP. phpenthusiast.com – English tutorials website devoted to Object Oriented PHP. Github projects myAPI – I think it is the simplest way to provide API services for small businesses that want to provide data based services to their customers. csvtax – Drupal 7 module that transforms a CSV file into hierarchical taxonomy. cornerslider – A jQuery popup that slides the content in and out when the user scrolls down and up the page. Technologies Back end programming languages: PHP, mySQL. Front end programming languages: CSS/3, HTML/5, javascript.
    [Show full text]
  • 2.5 the Unit Test Framework (UTF)
    Masaryk University Faculty of Informatics C++ Unit Testing Frameworks Diploma Thesis Brno, January 2010 Miroslav Sedlák i Statement I declare that this thesis is my original work of authorship which I developed individually. I quote properly full reference to all sources I used while developing. ...…………..……… Miroslav Sedlák Acknowledgements I am grateful to RNDr. Jan Bouda, Ph.D. for his inspiration and productive discussion. I would like to thank my family and girlfriend for the encouragement they provided. Last, but not least, I would like to thank my friends Ing.Michal Bella who was very supportive in verifying the architecture of the extension of Unit Test Framework and Mgr. Irena Zigmanová who helped me with proofreading of this thesis. ii Abstract The aim of this work is to gather, clearly present and test the use of existing UTFs (CppUnit, CppUnitLite, CppUTest, CxxTest and other) and supporting tools for software project development in the programming language C++. We will compare the advantages and disadvantages of UTFs and theirs tools. Another challenge is to design effective solutions for testing by using one of the UTFs in dependence on the result of analysis. Keywords C++, Unit Test (UT), Test Framework (TF), Unit Test Framework (UTF), Test Driven Development (TDD), Refactoring, xUnit, Standard Template Library (STL), CppUnit, CppUnitLite, CppUTest Run-Time Type Information (RTTI), Graphical User Interface (GNU). iii Contents 1 Introduction ....................................................................................................................................
    [Show full text]
  • Enhancement in Nunit Testing Framework by Binding Logging with Unit Testing
    International Journal of Science and Research (IJSR), India Online ISSN: 2319-7064 Enhancement in Nunit Testing Framework by binding Logging with Unit testing Viraj Daxini1, D. A. Parikh2 1Gujarat Technological University, L. D. College of Engineering, Ahmedabad, Gujarat, India 2Associate Professor and Head, Department of Computer Engineering, L. D. College of Engineering, Ahmadabad, Gujarat, India Abstract: This paper describes the new testing library named log4nunit testing library which is enhanced version of nunit testing library as it is binded to logging functionality. NUnit is similar to xunit testing family in all that cases are built directly to the code of the project. Log4NUnit testing library provides the capability to log the results of tests along with testing classes. It also provides the capability to log the messages from within the testing methods. It supplies extension of NUnit’s Test class method in terms of logging the results. It has functionality to log the entity of test cases, based on the Logging framework, to document the test settings which is done at the time of testing, test case execution and it’s results. Attractive feature of new library is that it will redirect the log message to console at runtime if Log4net library is not present in the class path. It will make easy for those users who do not want to download Logging framework and put it in their class path. Log4NUnit also include a Log4net logger methods and implements utility of logging methods such as info, debug, warn, fatal etc. This work was prompted due to lack of published results concerning the implementation of Log4NUnit.
    [Show full text]
  • Cakephp Cookbook Documentation Release 4.X
    CakePHP Cookbook Documentation Release 4.x Cake Software Foundation Sep 25, 2021 Contents 1 CakePHP at a Glance 1 Conventions Over Configuration........................................1 The Model Layer................................................1 The View Layer.................................................2 The Controller Layer..............................................2 CakePHP Request Cycle............................................3 Just the Start...................................................4 Additional Reading...............................................4 2 Quick Start Guide 13 Content Management Tutorial......................................... 13 CMS Tutorial - Creating the Database..................................... 15 CMS Tutorial - Creating the Articles Controller................................ 19 3 4.0 Migration Guide 29 Deprecated Features Removed......................................... 29 Deprecations.................................................. 29 Breaking Changes................................................ 31 New Features.................................................. 37 4 Tutorials & Examples 41 Content Management Tutorial......................................... 41 CMS Tutorial - Creating the Database..................................... 43 CMS Tutorial - Creating the Articles Controller................................ 47 CMS Tutorial - Tags and Users......................................... 56 CMS Tutorial - Authentication......................................... 64 CMS Tutorial - Authorization.........................................
    [Show full text]
  • PHP 7 Y Laravel
    PHP 7 y Laravel © All rights reserved. www.keepcoding.io 1. Introducción Nada suele ser tan malo como lo pintan © All rights reserved. www.keepcoding.io When people tell me PHP is not a real programming language http://thecodinglove.com/post/114654680296 © All rights reserved. www.keepcoding.io Quién soy • Alicia Rodríguez • Ingeniera industrial ICAI • Backend developer • @buzkall • buzkall.com http://buzkall.com © All rights reserved. www.keepcoding.io ¿Qué vamos a ver? • Instalación y desarrollo en local • PHP 7 • Laravel • Test unitarios • Cómo utilizar una API externa © All rights reserved. www.keepcoding.io ¿Qué sabremos al terminar? • PHP mola • Crear un proyecto de cero • Depurar y hacer test a nuestro código • Un poco de análisis técnico y bolsa © All rights reserved. www.keepcoding.io Seguridad Security is not a characteristic of a language as much as it is a characteristic of a developer Essential PHP Security. Chris Shiflett. O’Reilly © All rights reserved. www.keepcoding.io Popularidad en Stackoverflow http://stackoverflow.com/research/developer-survey-2016 © All rights reserved. www.keepcoding.io Popularidad en Github http://redmonk.com/sogrady/2016/07/20/language-rankings-6-16/ © All rights reserved. www.keepcoding.io Frameworks por lenguaje https://hotframeworks.com/ © All rights reserved. www.keepcoding.io Su propia descripción • PHP is a popular general-purpose scripting language that is especially suited to web development. • Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. https://secure.php.net/ © All rights reserved. www.keepcoding.io Historia de PHP • Creado por Rasmus Lerdorf en 1995 como el conjunto de scripts "Personal Home Page Tools", referenciado como "PHP Tools”.
    [Show full text]
  • Introduction to Unit Testing
    INTRODUCTION TO UNIT TESTING In C#, you can think of a unit as a method. You thus write a unit test by writing something that tests a method. For example, let’s say that we had the aforementioned Calculator class and that it contained an Add(int, int) method. Let’s say that you want to write some code to test that method. public class CalculatorTester { public void TestAdd() { var calculator = new Calculator(); if (calculator.Add(2, 2) == 4) Console.WriteLine("Success"); else Console.WriteLine("Failure"); } } Let’s take a look now at what some code written for an actual unit test framework (MS Test) looks like. [TestClass] public class CalculatorTests { [TestMethod] public void TestMethod1() { var calculator = new Calculator(); Assert.AreEqual(4, calculator.Add(2, 2)); } } Notice the attributes, TestClass and TestMethod. Those exist simply to tell the unit test framework to pay attention to them when executing the unit test suite. When you want to get results, you invoke the unit test runner, and it executes all methods decorated like this, compiling the results into a visually pleasing report that you can view. Let’s take a look at your top 3 unit test framework options for C#. MSTest/Visual Studio MSTest was actually the name of a command line tool for executing tests, MSTest ships with Visual Studio, so you have it right out of the box, in your IDE, without doing anything. With MSTest, getting that setup is as easy as File->New Project. Then, when you write a test, you can right click on it and execute, having your result displayed in the IDE One of the most frequent knocks on MSTest is that of performance.
    [Show full text]
  • Phpunit Manual Release Latest
    PHPUnit Manual Release latest Sebastian Bergmann Aug 18, 2021 Contents 1 Installing PHPUnit 3 1.1 Requirements...............................................3 1.2 Recommended PHP configuration....................................3 1.3 PHP Archive (PHAR)..........................................3 1.3.1 PHAR Implementation Details.................................4 1.3.2 Verifying PHPUnit PHAR Releases..............................4 1.4 Composer.................................................5 1.5 Global Installation............................................5 1.6 Webserver................................................6 2 Writing Tests for PHPUnit 7 2.1 Test Dependencies............................................8 2.2 Data Providers.............................................. 11 2.3 Testing Exceptions............................................ 17 2.4 Testing PHP Errors, Warnings, and Notices............................... 17 2.5 Testing Output.............................................. 20 2.6 Error output............................................... 21 2.6.1 Edge Cases........................................... 23 3 The Command-Line Test Runner 25 3.1 Command-Line Options......................................... 26 3.2 TestDox.................................................. 32 4 Fixtures 35 4.1 More setUp() than tearDown()...................................... 38 4.2 Variations................................................. 38 4.3 Sharing Fixture.............................................. 38 4.4 Global State..............................................
    [Show full text]
  • Secure PHP Development Handbook PHP Security Community of Practice Revision V1.0
    Queen's Secure PHP Development Handbook PHP Security Community of Practice Revision v1.0 Table of Contents • Queen's Secure PHP Development Handbook • Table of Contents • Introduction o Document Scope o How To Contribute o About The Authors . Document Contributors • PHP Configuration o Prerequisites o Development Environment . Workspace Recommendations . Source Control . Subversion Client Setup o Code Commenting . Special Considerations . php.ini o Production Environment . Special Considerations . php.ini • University Standards o Authentication o Database Connectivity . Connecting to Student Data Warehouse . Connecting to Human Resources o Online Payments • Application Design . Definition . Model . View . Controller . Implementation • Application Testing o Security Auditing and Penetration Testing o Testing for New Applications o Testing for Existing Applications / Commercial Software • Security Vulnerabilities o CSRF (Cross Site Request Forgeries) Attacks . Description . Example . Prevention o Remote Code Execution . Description . Example . Prevention o SQL Injection Vulnerabilities . Description . Example . Prevention . References o Format String Vulnerabilities . Description . Example . Prevention . References o XSS (Cross Site Scripting) Vulnerabilities . Description . Example . Prevention • Conclusion • Appendices Introduction This document provides recommendations and security best practices for PHP development at Queen's University. The primary goal of this document is to provide a snap shot of current recommendations for PHP developers
    [Show full text]
  • Taming Functional Web Testing with Spock and Geb
    Taming Functional Web Testing with Spock and Geb Peter Niederwieser, Gradleware Creator, Spock Contributor, Geb The Actors Spock, Geb, Page Objects Spock “Spock is a testing and specification framework for Java and Groovy applications. What makes it stand out from the crowd is its beautiful and highly expressive specification language. Thanks to its JUnit runner, Spock is compatible with most IDEs, build tools, and continuous integration servers. Spock is inspired from JUnit, RSpec, jMock, Mockito, Groovy, Scala, Vulcans, and other fascinating life forms. Spock (ctd.) http://spockframework.org ASL2 licence Serving mankind since 2008 Latest releases: 0.7, 1.0-SNAPSHOT Java + Groovy JUnit compatible Loves Geb Geb “Geb is a browser automation solution. It brings together the power of WebDriver, the elegance of jQuery content selection, the robustness of Page Object modelling and the expressiveness of the Groovy language. It can be used for scripting, scraping and general automation — or equally as a functional/web/acceptance testing solution via integration with testing frameworks such as Spock, JUnit & TestNG. Geb (ctd.) http://gebish.org ASL2 license Serving mankind since 2009 Latest releases: 0.7.2, 1.0-SNAPSHOT Java + Groovy Use with any test framework Loves Spock First-class page objects Page Objects “The Page Object pattern represents the screens of your web app as a series of objects. Within your web app's UI, there are areas that your tests interact with. A Page Object simply models these as objects within the test code. This reduces the amount of duplicated code and means that if the UI changes, the fix need only be applied in one place.
    [Show full text]
  • Phpunit Manual Version Latest
    PHPUnit Manual Version latest Sebastian Bergmann sept. 07, 2021 Table des matières 1 Installer PHPUnit 3 1.1 Pré-requis.................................................3 1.2 PHP Archive (PHAR)..........................................3 1.2.1 Windows............................................4 1.2.2 Vérification des versions PHAR de PHPUnit.........................4 1.3 Composer.................................................6 1.4 Paquets optionnels............................................6 2 Écrire des tests pour PHPUnit9 2.1 Dépendances des tests.......................................... 10 2.2 Fournisseur de données......................................... 13 2.3 Tester des exceptions........................................... 18 2.4 Tester les erreurs PHP.......................................... 19 2.5 Tester la sortie écran........................................... 21 2.6 Sortie d’erreur.............................................. 22 2.6.1 Cas limite............................................ 24 3 Lanceur de tests en ligne de commandes 27 3.1 Options de la ligne de commandes.................................... 28 3.2 TestDox.................................................. 34 4 Fixtures 35 4.1 Plus de setUp() que de tearDown().................................... 38 4.2 Variantes................................................. 38 4.3 Partager les Fixtures........................................... 38 4.4 Etat global................................................ 39 5 Organiser les tests 41 5.1 Composer une suite de tests
    [Show full text]