CI : the first_step: Auto Testing with CircleCI - (MOSG)
•
1 like•1,073 views
Continuous Integration The First stop : Auto Testing ( w/ Circle CI) Mulodo Open Study Group (MOSG) @HCMC, Vietnam http://www.meetup.com/Open-Study-Group-Saigon/events/232272580/
Report
Share
![Continuous Integration
In software engineering, continuous integration (CI) is the
practice of merging all developer working copies to a
shared mainline several times a day.
Grady Booch first named and proposed CI in his 1991
method,[1] although he did not advocate integrating
several times a day.
Extreme programming (XP) adopted the concept of CI and
did advocate integrating more than once per day - perhaps
as many as tens of times per day.
wikipedia](https://cdn.statically.io/img/www.slideshare.net/data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
CI : the first_step: Auto Testing with CircleCI - (MOSG)
- 1. Continuous Integration - The first step of Auto Testing- 2016/07/07 Mulodo Vietnam Co., Ltd.
- 2. Continuous Integration In software engineering, continuous integration (CI) is the practice of merging all developer working copies to a shared mainline several times a day. Grady Booch first named and proposed CI in his 1991 method,[1] although he did not advocate integrating several times a day. Extreme programming (XP) adopted the concept of CI and did advocate integrating more than once per day - perhaps as many as tens of times per day. wikipedia
- 3. Almost development works are ‘Enhancement of current system’. Why CI? * Rapid cycle : ‘Plan(Enlarge) - Dev - Measure(Enlarge)’ * Tests : not only for new code, but also ALL. (to avoid regression)
- 4. Almost development works are ‘Enhancement of current system’. Why CI? * Rapid cycle : ‘Plan(Enlarge) - Dev - Measure(Enlarge)’ * Tests : not only for new code, but also ALL. (to avoid regression) Tests are increasing || Dev cycle is going faster
- 5. Almost development works are ‘Enhancement of current system’. Why CI? * Rapid cycle : ‘Plan(Enlarge) - Dev - Measure(Enlarge)’ * Tests : not only for new code, but also ALL. (to avoid regression) Tests are increasing || Dev cycle is going faster No way out
- 6. dev cycle (engineer side) https://www.apicasystem.com/blog/top-5-tips-avoid- integration-hell-continuous-integration/
- 7. PLAN CODE BUILD TEST RELEASE DEPLOY legacy Engineering dev cycle (engineer side)
- 8. PLAN CODE BUILD TEST RELEASE DEPLOY Continuous Integration Continuous Delivery legacy Engineering dev cycle (engineer side)
- 9. PLAN CODE BUILD TEST RELEASE DEPLOY Continuous Integration Continuous Delivery legacy Engineering dev cycle (engineer side) Use Technology to solve the problem. Auto-Testing Auto-Deploy
- 10. dev cycle (from client side) Huh? Tests? That’s not my business. Please ask testers. No problem. We are testing our code in standard dev-flow
- 11. dev cycle (from client side) Huh? Tests? That’s not my business. Please ask testers. No problem. We are testing our code in standard dev-flow Which engineer do you think better?
- 12. Aut0-Testing (auto-deploy) So, “Testing” become a much important thing than you think. Let’s start Auto-testing
- 15. Today’s GOAL 1. push code to github 2. (AUTO) Testing on Circle CI 3. (AUTO) E-mail reporting very simple
- 16. Flow That’s ALL create repository on github.com create sample code and unit test code register to CircleCI
- 17. Flow create repository on github.com create sample code and unit test code register to CircleCI That’s ALL You can try auto-testing very easy !
- 19. sample code $ git clone git@github.com:nemo-mulodo-vn/test_circleci.git Cloning into 'test_circleci'... remote: Counting objects: 20, done. remote: Compressing objects: 100% (14/14), done. remote: Total 20 (delta 1), reused 17 (delta 1), pack-reused 0 Receiving objects: 100% (20/20), done. Resolving deltas: 100% (1/1), done. Checking connectivity... done. $ cd test_circleci $ composer install Loading composer repositories with package information Installing dependencies (including require-dev) from lock file Nothing to install or update Generating autoload files $ preparation - git clone - install required modules w/ composer
- 20. sample code $ ./vendor/bin/phpunit PHPUnit 4.8.26 by Sebastian Bergmann and contributors. Runtime: PHP 5.5.30 Configuration: /Users/nemo/git/tmp/test_circleci/phpunit.xml ...... Time: 189 ms, Memory: 4.00MB OK (6 tests, 6 assertions) $ test at local environment
- 21. register repository to CircleCI 1. Open CircleCI https://circleci.com/ Note) Please open github.com with your account on another tab.
- 22. register repository to CircleCI 2. Request authorization to your github
- 23. register repository to CircleCI 3. Confirm authorization
- 24. register repository to CircleCI 4. Select account (or Organization)
- 25. register repository to CircleCI 5. Select repository
- 26. register repository to CircleCI 6. Start build and testing !!!! environment closing testing
- 27. register repository to CircleCI 6. Start build and testing !!!! environment closing testing <- do noting This screenshot is on a case without any test code. NO TEST
- 28. That’s ALL Much easier than I thought
- 29. circle.yml A configuration file for CircleCI try to specify PHP version on CircleCI. machine: php: version: 5.6.14 circle.yml git add, commit, push
- 30. circle.yml Some more example machine: php: version: 5.6.14 dependencies: override: - composer install --prefer-source --no-interaction --dev test: override: - echo “Thanks for spending your time" circle.yml https://circleci.com/docs/configuration/ You can deploy code to specified EC2 server and test on the server. (if u need)
- 31. Thank you I am happy, If you become motivated to test.