Test Driven Development, Continuous Integration, Continuous Delivery, Continuous Test Automation

1. Agile, ATDD & CI/CD/CT
Pradeep Macharla
pradeep@seleniumframework.com

2. Agenda
▪ Background and Context
▪ Agile
▪ ATDD – AcceptanceTest Driven Development
▪ Continuous Delivery

3. Background
While most organizations realize that improving IT
performance is critical to long-term success, until now, it has
been unclear which investments truly move the needle. Our
findings suggest that high IT performance provides a real
competitive advantage, with hints that it plays a role in
boosting the value of publicly traded companies, as
measured by market capitalization

4. Puppet labs Survey(9200 people from 110 countries)

5. Puppet labs Survey(Diverse sample sets from population mix)

6. Data proves it

7. IT Performance
IT performance has real impact on the
business: Companies with high IT
performance are twice as likely to exceed
their profitability, market share and
productivity goals.

8. Practices Correlated with IT Performance

10. The original XP recipe is based on four simple values – simplicity, communication, feedback, and courage –
and twelve supporting practices:
Planning Game
Small Releases
Customer AcceptanceTests
Simple Design
Pair Programming
AcceptanceTest-Driven Development
Refactoring
Continuous Integration
Collective Code Ownership
Coding Standards
Metaphor
Sustainable Pace
Agile Types – Extreme Programming

11. • Industry practice in which whole team collaborates on Acceptance criteria and the
definition of done
• Automate acceptance tests while production code is being developed
• Automation completes before/side by side development
• Developer focuses on making acceptance tests pass
• Tests become part of build pipeline and are run throughout the sprint
• The acceptance automated tests will represent the true business value
ATDD is…
Run
Test
CodeWrite Test
Run
Test
Refactor

12. Gherkin
User Stories
PO Dev
TesterBSA
CucumberTests
version controlled
RunTests
Develop code
Version controlled
Collaborate
And Discuss
User Stories
0
1
2
3
4
ATDD - Process

13. Why ATDD

14. Unable to define what they want
don't know what they really want "now"
Misunderstood the requirements
wrong, incomplete or ambiguous
Misinterpret requirements
focus on implementation not behavior
That is not what
I want
Misinterpret
requirements
Incomplete tests
Before ATDD

15. Cost of Defects rise exponentially in later phases
64%
36%
Defect source
Requirement Analysis and Design
Phase
Coding/Implementation Phase

16. Issue # 1 - Requirement Ambiguity

17. 1
7
After ATDD - Collaboration, Discuss And Communication

18. Then, 3 Amigos write AC in BDD (Gherkin) format
Product Owner and
Business Analyst
Software Engineer
Quality Engineer

19. What you
think you
need
All you
actually
need
Issue # 2 - Over Engineering

20. What would give you
some value, right now
What you
think you
need
You
actually
need
20

21. Rework
Developers Testers
Deliberate Discovery skills
Issue # 3 Late Detection Of Defects

22. With ATDD
Less Rework
Developers Testers
Deliberate Discovery skills
Testers
22

26. ATDD is NOT a silver bullet
ATDD is suitable for programs or projects that are:
 Going through significant fast paced changes or complete re-writes
 Has relatively mature agile teams willing and able to adapt and learn as things change
 A strong product owner who is available to clarify requirements to tester and developer
 Availability of stable environment support
 Has CI/CD capabilities
Test Automation Expectations:
 Automation is coding - Requires good coding practices such as refactoring
 Not everything can or SHOULD be automated - Don’t automate if you won’t reuse
Challenges:
 Poor adoption
 Business users not collaborating
 Overstating expectations - scaling too fast
 Bandwidth/Velocity
 Learning Curve/Experience
 Infrastructure/Environment Availability

27. ATDD/BDD Tools..
Ruby – Cucumber
Python – Behave
All JVM languages – cucumber-jvm
Javascript – cucumberjs
.NET – SpecFlow
PHP – Behat
**Not an exhaustive list

28. CI/CD/CT
Continuous Integration is a software development
practice where members of a team integrate their
work frequently, usually each person integrates at
least daily - leading to multiple integrations per day.
Each integration is verified by an automated build
(including test) to detect integration errors as quickly
as possible.

29. CI/CD/CT

30. CI/CD/CT

31. CI/CD/CT Tools..
Jenkins, Travis, Cruise Control, Team City, Hudson,..
Nexus, Artifactory…
SonarQube…
Chef, Puppet, Ansible…
Docker, Kubernetes…
Selenium, Appium…
Never ends…
CI is NOT feasible without Automation

32. Thank you!
Email: pradeep@seleniumframework.com
Github: https://www.github.com/machzqcq
ContinuousTest Automation: www.seleniumframework.com