Recap of Dicoding Events : Continuous Quality and Test Automations

Michael Palotas, Francois Reynaud and Ben Hoskins shared their views about skillset, mindset and practices for successful test automation.

Transcript

1. Recap of 
 Continuous Quality & Test Automations Dicoding - Bandung, 16 April 2016
2. RELEASE FAST RELEASE CORRECT GOALS
3. THERE IS NO FIXED RECIPES IN AGILE. EVERY TEAM / COMPANIES SHOULD ADOPT WHATEVER BEST FOR HIM AND MIGHT NEED TO MODIFY IT TO SUIT THEIR NEEDS
4. ENGINEERING PRACTICES • CONTINUOUS INTEGRATION - DELIVERY - DEPLOYMENT • BUG PREVENTIONS VS BUG DETECTIONS • TEST AUTOMATIONS • PAIR PROGRAMMINGS
5. ENGINEERING PRACTICES (2) • CODE REVIEWS • STATIC CODE ANALYSIS • INTERNAL AND EXTERNAL QUALITY MINDSETS • METRICS AND KPIs
6. WHAT’S THE DIFFERENCE? • CONTINUOUS INTEGRATION • CONTINUOUS DELIVERY • CONTINUOUS DEPLOYMENT
7. CONTINUOUS INTEGRATION
8. Continuous Deployment - Delivery
9. VISION CI - CD • EVERYBODY SHOULD BE ABLE TO DEPLOY • THERE WILL BE NO DIFFERENCES BETWEEN DEPLOYING HOTFIX OR FEATURE. IT CAN BE RELEASED ANYTIME ANYWHERE.
10. INTERNAL AND EXTERNAL QUALITY MINDSETS • EXTERNAL MINDSET : CUSTOMER HAPPINESS, REVENUE, ETC • INTERNAL MINDSET : CODE QUALITY, ETC
11. METRICS AND KPIs • SET GOALS -> PEOPLE WILL BE ENCOURAGED TO REACH • BUT… THERE IS ANOTHER THING THAT ALSO IMPORTANT! • TRENDS OF INCREASED VALUE OF EACH METRICS / KPIs
12. BUG PREVENTIONS VS DETECTIONS • What to expect from automated tests? • Testers should be assisting developers to prevent bugs, not only hunting bugs • Developers should not believe QA will catch bugs
13. ROLES OF QA in ATLASSIAN • QA == Quality Assistance != Quality Assurances • Teach developers to tests • Assessing risks • Prevent problems • Ensure quality is everybody’s responsibility
14. TEST AUTOMATIONS • AVOID REPETITIVE TASKS • FASTER AND MORE FREQUENT FEEDBACK • SAFETY NET ( REDUCE RISKS OF RELEASING BUGS ) • IT SHOULD NEVER FIND ANY BUGS. IT MEANS OUR CODE HAS GOOD QUALITY.
15. TEST AUTOMATIONS (2) • REINVEST TIME. TESTERS / DEVELOPERS TIME CAN BE USED TO DO ANOTHER THINGS • NOT TO REPLACE HUMANS • BUY TOOLS IF NEEDED
16. TEST AUTOMATIONS (3)
17. TESTING FOR THE FUTURE • TDD
 TEST CONTINUOUSLY ALONGSIDE DEVELOPMENT • ALL TESTS ARE DONE WITHIN SPRINTS • TESTING IS EVERYBODY’S RESPONSIBILITY
18. MINDSET TO BE ACHIEVED • WE ARE NOT ONLY CREATING THINGS • WE TEST EVERYTHING • WE SHOULD BE ABLE TO DELIVER OUR CODE TO CUSTOMER AUTOMAGICALLY • TEST SHOULD BE PART OF OUR DNA • BIG MINDSET CHANGES REQUIRED
19. CHANGES? • DON’T BE AFRAID TO MAKE CHANGES • DEVELOPERS SHOULD THINK AS TESTERS • TESTERS HAVE MINIMUM KNOWLEDGE TO DISCUSS THINGS WITH DEVELOPERS
20. CHANGES (2) • CULTURE: • FREEDOM • OK TO FAIL • INNOVATIONS • OWNERSHIP (REDUCE IT’S NOT MY JOB IDIOMS) • PRODUCT OWNERS SHOULD BE INVOLVED FROM START TO FINISH
21. SOME NICE QUOTES (1) • IF YOU’RE NEW STARTUP, FOCUS ON WHAT MATTERS AND RELEASE FASTER. • BUT DON’T FORGET TO FILL THE GAPS IN TESTING BECAUSE IN THE FUTURE IT’S GOING TO BE NEEDED. • ESPECIALLY WHEN FEATURES ARE ADDED AND ADDED
22. SOME NICE QUOTES (2) • TDD GIVES US CONFIDENCE WHEN WE ADD NEW PEOPLE • IT WILL ENSURE HE CAN CHANGE ANYTHING WITHOUT AFRAID TO BROKE ANYTHING OR AT LEAST HE KNOWS WHAT’S BROKEN
23. SOME NICE QUOTES (3) • TDD MIGHT SLOW US DOWN WHEN WE IMPLEMENT IT IN THE MIDDLE • BUT IT WILL HELP US AVOID HARDER SITUATIONS WHEN FEATURES ADDED IN THE FUTURE
24. SOME NICE QUOTES (4) • IT’S IMPOSSIBLE TO MAKE HUMAN FOLLOW A LOT OF WRITTEN TEST SCENARIOS • IT SHOULD BE AUTOMATED, BUT NOT EVERYTHING COULD BE AUTOMATED • EXAMPLE: PEN TESTS / SECURITY TESTS
25. SOME NICE QUOTES (5) • CODE REVIEWS HELP DEVELOPERS LEARN ANOTHER PEOPLE CODES • INTERESTING PART IS WE SHALL ALLOW PEOPLE WHO’RE NOT WORKING WITH THE PARTICULAR FEATURES TO GIVE FEEDBACKS • IT’S HOW OPEN SOURCE WORKS
26. SOME NICE QUOTES (6) • IF ONLY SPECIFIC PEOPLE OWNS PARTICULAR CODES, IT MIGHT MAKES US TRAPPED TO FOLLOW SPECIFIC STYLES AND CANNOT FOLLOW OTHERS • IT MIGHT MAKE A SINGLE POINT OF FAILURE
27. HATUR NUHUN