Presentation on World Conference on Next Generation Testing 2015 conducted at Bangalore,India on ' Anti Patterns of Testing for Continuous Delivery adoption'. This presentation covered the anti patterns of testing during the continuous delivery adoption. It covered the details related to Collaboration, test automation architecture, test suite organization, lack of test strategy for parallel execution in the build pipeline, test code issues and some others.It also highlighted how it is difficult for any team to adopt continuous delivery in true sense and and further move into the continuous deployment and Devops practices due to such challenges.

1. Anti Patterns of Testing for Continuous Delivery Adoption
Prepared By Anish Cheriyan, Director, Huawei Technologies

2. Topics
• Code and Test Code
• TIER
• Anti Patterns

4. Photo by Mr.Thomas - Creative Commons Attribution-ShareAlike License https://www.flickr.com/photos/17813892@N00 Created with Haiku Deck

5. Photo by Naomi King - Creative Commons Attribution License https://www.flickr.com/photos/22141297@N06 Created with Haiku Deck
Continuous Integration
Continuous Delivery
Continuous Deployment
DevOps

6. Anti Patterns

7. Test Practices Mapped
Read at : http://www.thinkinginagile.com/2015/07/agile-testing-practices-mapped-to.html

8. Photo by fr1zz - Creative Commons Attribution-NonCommercial-ShareAlike License https://www.flickr.com/photos/39143000@N00 Created with Haiku Deck

9. • Test Code to Code Ratio is 1:1 or may be more
• Test to Developer Ratio is 1:3 or may be lesser
• Test Should be Everybody’s Responsibility
TIER

10. Photo by Paul Stevenson - Creative Commons Attribution License https://www.flickr.com/photos/53496815@N00 Created with Haiku Deck

11. Photo by Mark Fischer - Creative Commons Attribution-ShareAlike License https://www.flickr.com/photos/80854685@N08 Created with Haiku Deck

12. INVERTED TEST PYRAMID
Picture Courtesy: blogs.agilefaqs.com

13. Photo by Stéfan - Creative Commons Attribution-NonCommercial-ShareAlike License https://www.flickr.com/photos/49462908@N00 Created with Haiku Deck

14. Photo by Enzymlogic - Creative Commons Attribution-ShareAlike License https://www.flickr.com/photos/101755654@N08 Created with Haiku Deck

15. Com
mit
UT &
Inspe
ction
Functi
onal
Build
UAT …
DEPLOYMENT PIPELINE
ORCHESTRATION NOT WELL THOUGHT
OF..

16. Photo by tunnelarmr - Creative Commons Attribution-NonCommercial-ShareAlike License https://www.flickr.com/photos/27311060@N00 Created with Haiku Deck
FOCUS ONLY ON TOOLS/FRAMEWORKS
NOT ON AUTOMATION ARCHITECTURE

17. Test Automation Strategy
Picture Courtesy: Agile Testing-Lisa Crispin, Janet Gregory

18. Photo by nick farnhill - Creative Commons Attribution-ShareAlike License https://www.flickr.com/photos/57749032@N00 Created with Haiku Deck

19. INFRASTRUCTURE CODE
NOT TESTED

20. NO FOCUS ON HARDENING

21. Conclusion
• Continuous DXXX…= QUALITY OF TEST CODE
• Test Code will live as long as product live
• Invest on Test Code. Consider it as Safety Net.
• If (1:1 & 1:3) then 1:3
• Remember TIER

22. Photo by matt hutchinson - Creative Commons Attribution License https://www.flickr.com/photos/17524395@N00 Created with Haiku Deck

23. References
• Agile Testing- Lisa Crispin
• Pragmatic Software Testing- Rex Black
• www.thinkinginagile.com
• www. Countinuousdelivery.com
• Countinous Delivery- Jez Humble
• The Art of Agile Development-James Shore

24. Thank You
“If (1:1 & 1:3) then 1:3”
Speaker Name: Anish Cheriyan
Email ID: anishcheriyan@huawei.com,
“If Test Code to Code Ratio is 1:1 and Tester to Coder ratio is 1:3 then Test Responsibility should be 1:3 for Tester to Coder”