E N D
What type of testing is good for me? Yuriy Gerasimov Lead Developer @ygerasimov, yuri.gerasimov@gmail.com
Quality • no bugs • easy to maintain • performance metrics • code metrics
Testing • automated testing • investment with no features • pays off if run often
Infrastructure • continuous integration • manual testing on pull requests • development culture • maintenance costs
Code Checks • immediate • code style • security checks • linters • complexity metrics
Unit Testing • fast • calculations • regular expressions • writing testable code is hard • Drupal8 is much better
Functional Testing • slow & expensive • maintenance • should have one button to run • behat, selenium, ghost inspector • critical user flows, budget
Frontend Testing • performance • javascript • Front-EndOps
Visual Regression Testing • slow • screenshot storage • making screenshots of big pages • false positives • baseline images • compare environments
Performance • slow • production environment • infrastructure • authenticated users
Preflight Checks • slow • scan all pages 404, images sizes
Tools CI: Jenkins, Bamboo, TravisCI, ProboCI, Tugboat Code Checks: PHPCodeSniffer, PHPMD Unit Testing: PHPUnit, Drupal’s own system Functional Testing: Behat, Selenium, Ghost Inspector FrontEnd Testing: SpeedCurve, Chris Ruppel presentations Visual: BackTrac.io, Shoov, Wraith Performance: JMeter, Flood.io, Blazemeter Preflight: github repo
What type of testing is good for me? We are hiring! Yuriy Gerasimov, Lead Developer @ygerasimov, yuri.gerasimov@gmail.com