Testing, Build Automation & Auto Deployment

An indepth journey into software testing principles, build automation with jenkins and auto deployment with capistrano. All with a focus on PHP.

Transcript

1. Testing, Build Automation & Deployment GlasgowPHP - November 2014
2. About Me Paul Dragoonis - @dr4goonis - dragoonis@php.net Work on PHP core/extensions/documentation Make php.net pretty & modern PHPFIG maintainer / member PPI Framework Project Lead CTO / Lead Developer at Opinurate
3. Make php.net pretty & modern php.net + joind.in integration (unreleased)
4. PPI Framework Project Lead PPI is the PHP Interoperability Framework. It provides an equal and open platform allowing PHP developers to pick the best tools from the best PHP frameworks PPI bootstraps framework components for you from the top frameworks such as ZendFramework2, Symfony2, Laravel4, Doctrine2
5. Architecture of PHP
6. PPI Framework Architecture
7. Why did I make PPI Framework? What PHP was like (framework wars)
8. How I wanted PHP to be like (framework co-op)
9. Outline Testing Benefits, Guidelines, Mocking, Practical Examples Setting up Build Automation Benefits, Jenkins, Ant Tasks, Jenkins Plugins, PHP QA Tools Auto Deployment to any remote server
10. Types of Testing Unit Testing Integration Testing Acceptance Testing
11. Unit Testing Tests a single unit of code (otherwise it’s integration testing) A unit is the smallest testable part of an application, i.e: as class or a method Tests contain assertions that are either true or false. The tests pass when the behaviour of the code is correct.
12. Reasons Testing Matters Even the best programmers can and do make mistakes! Allows a project to move in baby-steps from one completely tested working version to the next with complete confidence. The amount of confidence is proportional to the quality of the automated testing.
13. Who doesn’t have tests setup?
14. Some Testing Fears Won’t writing tests slow me down? A project using TDD can take up to 30% longer to build, but results in up to 90% fewer bugs in production Bugs are test cases you have not written yet.
15. Tips For Writing Testable Code Test one class at a time Make each test independant Mock external state and services
16. ROI Benefits of Unit Testing > Identifies tight code coupling and behavioural changes > Facilitate refactoring (check if you broke something?) > Find problems early > Encourages use of Dependency Injection > Encourages Single Responsibility Principle (S of SOLID) > Increases the quality of OOD/OOP > Changes how you think when developing
17. Dependency Injection Providing the objects that an object needs (its dependencies) instead of having it construct them itself. It's a very useful technique for testing, since it allows dependencies to be mocked.
18. Dependency Injection Example: FROM
19. Dependency Injection Example: TO
20. Dependency Injection Example: TO
21. Example PHPUnit Test
22. PHPUnit With Data Provider
23. Mocking Dependencies
24. Things to mock Objects that you’re not directly testing, isolate all the things! External services > database calls > api calls > filesystem calls > environment state
25. Things that are hard to mock Global variables statics variables and methods singletons private methods Magic methods (__call, __get, __set)
26. Mocking Example Code
27. PHPUnit Mocking Example
28. Mockery Example
29. Integration Testing Check out dbUnit XML files which become SQL inserts so you can run database queries and check the results. Good for SQL-level logic and checking that your queries or stored procedures work properly.
30. DBUnit Integration - Example Setup
31. DBUnit Integration - XML Example
32. DBUnit Integration - Code Example
33. Running PHPUnit - Custom Output Printers
34. Running PHPUnit - Custom Output Printers
35. Acceptance Testing No time today, but look at the following technologies: Selenium, Behat, phpspec, Mink, PhantomJS BDD Test cases: Useful customer communication because they’re human readable. Focuses on business requirements and their behaviour
36. Pause, Breathe, Questions?
37. Build Automation What is a build? A build acts as the process for putting source code together and verifying that the source works as a cohesive unit -- “Paul M. Duvall” What is build automation? “Build automation is the act of scripting a wide variety of tasks that developers do in their day-to-day activities. Such as: Compiling, Running Tests, Deployment to Production -- Wikipedia
38. What’s in a build? Code generation > Autoloader optimisations > Object-Relational Mapper (php or sql code) > Framework Scaffolding (cache warming)
39. Getting the most out of CI Keep changesets as small as possible. Merge early, merge often > less conflicts the better Write tests that run fast > don’t want to be waiting 10 minutes for a hotfix to build Automate the entire QA process (one click action)
40. Build Automation
41. Build Process
42. Continous Integration Software CruiseControl / phpUnderControl Travis-CI Thoughtworks Go SonarQube Jenkins
43. Jenkins Extensible with lots of plugins and integrates with PHP QA Tools Tasks using Apache Ant Automated Test suite Code Analysis / Coding Standards Documentation Generation Software metrics in one central place Packaging / Deployment
44. QA Tools For PHP PHP_CodeSniffer (PSR Compliance) > Checks for coding style violations > Best Practises: Comes with PSR-1 and PSR-2 PHP-CPD (Copy Paste Detector) PHPMD (Mess detector) > Warns you on complex code Clover PHP (code coverage output)
45. Jenkins - Jobs for different environments
46. When Setting Jenkins Up Configure security Configure mail settings Install additional plugins > Github > IRC
47. Jenkins Github Plugin
48. Jenkins IRC Plugin
49. Jenkins - Job Index Page
50. Jenkins - Shell Commands & Ant Tasks
51. Jenkins build.xml file - Ant Jobs
52. Jenkins - Composer & PHPUnit
53. Jenkins - Composer & PHPUnit
54. Jenkins - Code Analysis
55. Jenkins - Parallel Jobs
56. Jenkins - Code Analysis API Docs (phpdox)
57. Jenkins - Code Analysis Code Coverage - Files
58. Jenkins - Code Analysis Code Coverage - Individual Methods
59. Jenkins - Code Analysis Code Coverage - Individual Lines of Code
60. Jenkins - Deploy Time!
61. Pause, Breathe, Questions?
62. Auto Deployment
63. Auto Deployment - Benefits One click deploys, no manual intervention Anyone on your team can deploy You can deploy from Jenkins or IRC ! Release Management, you can roll back!
64. Capistrano - How does it work ? Pulls down your VCS (git) contents Performs tasks on the codebase > db migrations > asset minification 1) SSH into your target server 2) rsync’s the code to the target dir 3) updates the ‘current’ symlink to the latest release 4) if errors, runs cap:rollback
65. Using Capistrano - Configuration Capfile Default file outlining basic setup and including a deploy.rb file config/deploy.rb This file contains your application’s deployment config config/deploy/environment_name.rb Specific configurations for the specific environment.
66. Capistrano Commands cap deploy:setup cap deploy <environment> cap deploy:rollback
67. Using Capistrano - Capfile
68. Using Capistrano - config.rb
69. Capistrano - app/config/deploy/<env>.rb
70. Remote Deployment Structure /deploy/path/ /deploy/path/releases/ /deploy/path/releases/20140819001122 /deploy/path/shared/ /deploy/path/current -> ../releases/20140819001122
71. Capifony - Capistrano Ext for Symfony2 When not using a Symfony2 - I’ve been using PPI Framework 2.1
72. Thanks