Sebuah pembahasan menarik tentang Agile Software Development dengan Test Driven Development (TDD) & Continuous Integration (CI). Materi ini disusun oleh Mas Disyam

1. TDD & CI in FRONTEND
disyam.adityana@gmail.com

2. AGILE SOFTWARE
DEVELOPMENT

3. COMPLEXITY

4. AGILE VS WATERFALL

5. TEST DRIVEN DEVELOPMENT
(TDD)

6. WHAT IS TDD?

7. WHY TDD?
● SAFETY NET
● REDUCE BUGS
● FAST FEEDBACK
● VALIDATE YOUR DESIGN
● KEEP FOCUS ON GETTING DONE
● FORCE DEVELOPER TO THINK ABOUT GOALS
● EASY MAINTENANCE
● EASY UPGRADE
● ETC...

8. GOOD TEST
● AUTOMATED AND REPEATABLE
● EASY TO IMPLEMENT
● ANYONE SHOULD ABLE TO RUN IT
● IT SHOULD RUN QUICKLY
● IT’S RESULT SHOULD BE CONSISTENT
● IT SHOULD FULLY ISOLATED
● WHEN TEST FAILS, IT MUST BE EASY TO DETECT WHAT WAS EXPECTED
AND HOW TO PINPOINT THE PROBLEM

9. TDD WORKFLOW

10. UNIT TESTING

11. FRONTEND UNIT TESTING
● KARMA - TASK RUNNER
● MOCHA - TESTING FRAMEWORK
● CHAI - ASSERTION LIBRARY

12. FRONTEND UNIT TESTING EXAMPLE

13. FRONTEND TESTING EXAMPLE

14. END TO END TESTING

15. FRONTEND E2E TESTING
● PROTRACTOR - TASK RUNNER
● MOCHA - TESTING FRAMEWORK
● CHAI - ASSERTION LIBRARY

16. FRONTEND E2E TESTING EXAMPLE

17. CODE COVERAGE
A TECHNIQUE TO DETERMINE HOW
MUCH CODE IS BEING TESTED

18. CODE COVERAGE TOOLS
● ISTANBUL
● BLANKET.JS
● COVERALLS.IO

19. CODE COVERAGE EXAMPLE

20. CLEAN CODING

21. CLEAN CODE METRIC

22. WAY TO CLEAN CODE
● ANGULAR JOHN PAPA’S STYLE GUIDE
● CODECLIMATE.COM

23. CONTINUOUS INTEGRATION (CI)

24. WHAT IS CI?

25. WHY CI?
● IF YOU’RE GOING TO FAIL, THEN FAIL EARLY
● ENABLE CONTINUOUS DELIVERY
● ENABLE AUTOMATED TESTING
● INCREASE CONFIDENCE IN OUR PRODUCT
● PREVENTION AND REDUCTION OF PRODUCTION AND STAGING ERRORS
● REDUCING RISK
● REDUCING OVERHEAD ACROSS THE DEVELOPMENT AND DEPLOYMENT
PROCESS

26. CI TOOLS
● JENKINS
● TEAMCITY
● TRAVIS-CI.ORG
● CODESHIP.COM

27. THANK YOU