Automatisation in development and testing - within budget [IronCamp Prague 2016-11]

Working on client projects with very strict budget and resource restrictions, tight deadlines and pressure, many times does not allow for full blown Test Driven Development, Continuous Delivery and other software engineering goodness we would love to have. We will show you easily accessible and quickly implementable options, that allow you to automate your development and testing process, or at least the most painful parts, without blowing the budget. Finally you can relax during deployments of the code to production! :-)

Transcript

1. AUTOMATIZATION IN  DEVELOPMENT  AND  QUALITY  PROCESS (WITHIN  BUDGET) David  Lukac Senior  Technical  Consultant Inviqa UK  Ltd. @davidlukac
5. David  Lukac Senior  Technical  Consultant Inviqa UK  Ltd. @davidlukac
6. http://inviqa.com
7. BACKGROUND • Software  Engineer  @  Siemens • Java  Consultant  @  T-­‐Mobile  Austria • CTO  @  Mogdesign.eu • Head  of  Project  Operations  @  I-­‐KOS  Ltd. • Senior  Technical  Consultant  @  Inviqa UK
8. Questions 1. F 2. G/V 3. DR/DC 4. AQA 5. C*
9. WHY  AUTOMATE? • Saves  time • Streamline  process • Efficiency • Quality  /  Error  rate
11. WHAT  IS  CI? • Best  practice  … • Merging  … • Immediate  testing  and  reporting  … • G:  Rapid  feedback  … • O:  Defects  identified  and  corrected  ASAP
12. WHAT  IS  CD? • Short  cycles  … • Releasibility … • G:  Build,  test,  release  … • O:  …  fast,  frequently.
13. WHY  CI/CD? • Business  Critical  Functionality • Regression • DRY • Ease  of  Mind • Confidence • Trust
14. BUT  HOW?!  …  WHAT  ABOUT  THE  BUDGET!?
15. PREPARATION  – UNIFIED  ENVIRONMENT • Drush aliases • Local  Stack • DevDesktop • DrupalVM /  Virtualbox • Docker
16. PREPARATION  – UNIFIED  ENVIRONMENT $  <project  root>/drush/mysite.aliases.drushrc.php <?php $aliases['mysite.local']  =  array(  ....  );   $aliases['mysite.stage']  =  array(  ....  );   $aliases['mysite.uat']  =  array(  ....  );   $aliases['mysite.prod']  =  array(  ....  );   ...   $  ln  -­‐s  ${DIR}/mysite.aliases.drushrc.php ~/.drush/mysite.aliases.drushrc.php
17. Credit: http://joefleming.net/posts/git-­‐flow/
18. LOCAL  TASKS SHELL >_
19. SHELL  SCRIPTS #!/usr/bin/env bash   #  Basic  deployment  tasks.   drush @mysite.${1}  cc  all   drush @mysite.${1}  updatedb -­‐y   drush @mysite.${1}  cron
20. SHELL  SCRIPTS #!/usr/bin/env bash   #  Basic  deployment  tasks.   drush @mysite.${1}  cc  all   drush @mysite.${1}  updatedb -­‐y   drush @mysite.${1}  cron #  Purge  Varnish   curl  -­‐X  PURGE  -­‐H  "X-­‐Acquia-­‐Purge:[mysite.com]” -­‐H  "Accept-­‐Encoding:  gzip"  https://mysite.com/about
21. SHELL  SCRIPTS #!/usr/bin/env bash   #  Basic  deployment  tasks.   drush @mysite.${1}  cc  all   drush @mysite.${1}  updatedb -­‐y   drush @mysite.${1}  cron #  Purge  Varnish   curl  -­‐X  PURGE  -­‐H  "X-­‐Acquia-­‐Purge:[mysite.com]” -­‐H  "Accept-­‐Encoding:  gzip"  https://mysite.com/about #  Features   #  Hidden  bonus(?!)   drush @mysite.${1}  fra -­‐y
22. SHELL  SCRIPTS #  Pull  everything   drush rsync ${source}:%files/  ${target}:%files/  -­‐-­‐mode=ahkvz -­‐-­‐progress  -­‐y   drush sql-­‐sync  ${source}  ${target}  –y
23. SHELL  SCRIPTS #  Pull  everything   drush rsync ${source}:%files/  ${target}:%files/  -­‐-­‐mode=ahkvz -­‐-­‐progress  -­‐y   drush sql-­‐sync  ${source}  ${target}  –y #  Tests   bin/behat features/
24. SHELL  SCRIPTS #  Pull  everything   drush rsync ${source}:%files/  ${target}:%files/  -­‐-­‐mode=ahkvz -­‐-­‐progress  -­‐y   drush sql-­‐sync  ${source}  ${target}  –y #  Tests   bin/behat features/ #  Migration   drush @mysite.${1}  en menu_migrate -­‐y   drush @mysite.${1}  mi  Menu  -­‐-­‐feedback="100  items"
25. SHELL  SCRIPTS #  Pull  everything   drush rsync ${source}:%files/  ${target}:%files/  -­‐-­‐mode=ahkvz -­‐-­‐progress  -­‐y   drush sql-­‐sync  ${source}  ${target}  –y #  Tests   bin/behat features/ #  Migration   drush @mysite.${1}  en menu_migrate -­‐y   drush @mysite.${1}  mi  Menu  -­‐-­‐feedback="100  items” #  Solr drush @mysite.${1}  solr-­‐delete-­‐index   drush @mysite.${1}  solr-­‐index
26. DEPLOYMENT  SHELL  SCRIPTS #!/usr/bin/env bash   #  Deployment  script   drush @mysite.$1  fr feature_article -­‐y   drush @mysite.$1  vset my_custom_var 1
27. DEPLOYMENT  SHELL  SCRIPTS #!/usr/bin/env bash   #  Deployment  script   drush @mysite.$1  fr feature_article -­‐y   drush @mysite.$1  vset my_custom_var 1 drush @mysite.$1  cc  css-­‐js drush @mysite.$1  cron
28. OTHER • Environment  setup • Dependency  management  – npm,  bundle,  compose • Assets  – gulp • Changelog,  release  notes • Toggle  modules
30. REMOTE  DEPLOYMENT Laravel Envoy  (PHP) • Server  side  (too) • SSH • Easy  to  setup • Servers • Tasks • Macros • Setup
31. Envoy.blade.php -­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐ @servers(['s1'  =>  'usr1@myserver.com  -­‐p  12345'])   @setup   $now  =  new  DateTime();   $environment  =  isset($env)  ?  $env :  "testing";   @endsetup @task('deploy-­‐prod',  ['on'  =>  's1'])   cd  /var/www;  echo  {{  $now  }};  echo  {{  $environment  }}   git checkout  master;  git pull   drush @mysite.prod updb drush @mysite.prod cc  all   drush @mysite.prod cron @endtask @macro('deploy')   deploy-­‐prod   clean-­‐up @endmacro
32. $  envoy  run  deploy-­‐prod
33. REMOTE  DEPLOYMENT Laravel Envoy  (PHP) • Server  side  (too) • SSH • Easy  to  setup • Servers • Tasks • Macros • Setup Fabric  (Python) • Server  side  (too) • SSH • Easy  to  setup • Inventory • Tasks • Parallel  execution • Strength  of  Python  ecosystem
34. Fabfile.py -­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐-­‐ from  fabric.api import  run,  local,  cd,  env,  task import  ConfigParser import  os env.hosts =  [’devops@tergetserver’] @task() def deploy():         local("git fetch") local("git checkout  master") local("git pull") local("git push  {r}  HEAD".format(r=git_remote_name)) prod_dir =  ’/var/www/project’ with  cd(prod_dir): run("git fetch") run("git checkout  master") run("git pull") run("composer  install  -­‐-­‐no-­‐dev  -­‐-­‐no-­‐progress  -­‐-­‐no-­‐suggest   -­‐-­‐optimize-­‐autoloader  -­‐-­‐no-­‐interaction")
35. REMOTE  DEPLOYMENT Others • Laravel Envoy  (PHP) • Rocketeer  (PHP) • Fabric  (Python) • Invoke  (Python) • Ansible (YAML,  Python) • Capistrano  (Ruby)
36. CI/CD  CLOUD  TOOLS Credit:  http://galilsoftware.com/our-­‐2015-­‐ci-­‐survey-­‐the-­‐results/
37. CI/CD  CLOUD  TOOLS Credit:  http://galilsoftware.com/our-­‐2015-­‐ci-­‐survey-­‐the-­‐results/ GITHUB.COM/RIPIENAAR/FREE-­‐FOR-­‐DEV
38. QA  AUTOMATION
39. http://inviqa.com
40. QA  AUTOMATION • TDD • Unit  Tests • … • Pricy? • Time  consuming? • ROI?
41. DDD  &  BDD
42. BEHAT • Behavioral  testing • Gather  and  describe   business  requirements • Test  business  requirements • User  stories • Gherkin
43. BEHAT • Behavioral  testing • Gather  and  describe   business  requirements • Test  business  requirements • User  stories • Gherkin • Describe  and  test  critical   functionality: • Login • Purchase • Editorial • … • Drupal  support
44. Feature:  Homepage   I  want  to  see  a  home  page As  a  user   So  I  can  see  the  latest  featured  content  on  the  site.   Background:   Given  I  am  not  logged  in   When  I  visit  "/"   Scenario:  User  can  see  Main  header   Then  I  should  see  the  text  "welcome  to  our  site” And  I  should  see  the  subheading   Scenario:  User  can  see  Latest  Articles   Then  I  should  see  11  latest  homepage  articles
45. <?php class  FeatureContext extends  RawDrupalContext implements  SnippetAcceptingContext {   ...   /**   *  @Then  I  should  see  the  subheading   */   public  function  iShouldSeeSubHeading()  {   $this-­‐>countElements('.taxonomy-­‐term.vocabulary-­‐sections   .field-­‐name-­‐field-­‐body  .field-­‐item',  1,  'Homepage  subheading');   }   ...
48. GHOST  INSPECTOR • Automated  UI  testing • Automated  monitoring • Screenshots • Comparison • Browser  actions,  forms
49. GHOST  INSPECTOR • Automated  UI  testing • Automated  monitoring • Screenshots • Comparison • Browser  actions,  forms • Step  by  Step • Selectors • Recorder • API
53. RECAP • Effectiveness  &  Quality • Confidence  &  Trust • Unified  environment • Automated  tasks • Automated  QA • Time  for  coffee  +  $$$
54. THANK  YOU! QUESTIONS?