The document discusses the evolution of testing in the context of Agile and DevOps, highlighting the integration of development, testing, and operations to enhance efficiency and reduce IT friction. It critiques traditional testing misconceptions and emphasizes the importance of continuous improvement, rapid feedback, and a culture of collaboration within project teams. Testing is framed as a shared responsibility, focusing on quality and timely delivery rather than as a separate phase in the development lifecycle.

1. Systems Thinker | Developer | Efficient | Tester
THE NEW AGE TESTING IN THE LAND OF AGILE
SDET

2. Once upon a time - There was place for everyone
Development
Test
IT Operations

3. Agile came…

4. Water Scrum Fall was born (Forrester Research)
IT Ops

5. Dev & Test
IT Ops

6. Ops had to work more…

7. IT-Ops - What going on?

8. Courtesy: Jez Humble

9. The business requires change!

10. Core Conflict of an IT organization

11. Respond more quickly to urgent business needs – deliver feature changes
&
Provide stable, secure & predictable IT service
Double edged Sword…

13. New Age IT
To handle business change quickly & to run the businesses
To reduce “IT friction” at Dev/Ops world
To improve velocity to build/deliver/deploy software
To care for Quality, Maintainability, Security, Scalability, Durability, Deployability
To reduce Technical Debts

14. Tools
Process
Culture

15. Perfect storm of 2009

16. Ops thinks like developers, Developers think like Ops
Courtesy: Flickr

18. Delivering Value
Test
DevOps Movement

20. Be a Nigel…he helped the fishes in the tank

21. Culture is the way you think, act and Interact

22. It is not for me syndrome

25. What has changed in Testing?

26. There is no such thing as “manual” or “automated” testing,
just as there isn’t “manual” or “automated” programming

27. Testing is contextual
SDLC
SDLC/Agile
Agile
Change
Business
Needs
IT Readiness Adoption

28. Unbalanced workload create severe bottlenecks
effort
time

29. Process Quadrant

30. Fallacies of testing
- Testing is after development
- I fail/break applications
- We find defects
- We work incremental
- More features, more test cases, more regression
- I wait for my big-batch, so that I get busy
- We know what went wrong – post mortem analysis
- We multi-task
- We love playing ping-pong
- Testing is a phase – we call it stabilization
- We are domain experts
- Our test environment is limited
- We love writing test-cases
- we plan enough
- We trade-off
- We love finding facts
- We have a weapon to expedite testing “Risk Based Testing”

31. Caveats of traditional testing
- Execution delays - Cycle time
- Lead-time to failure
- Integrate, build, deploy dependencies
- Environment Spec for running an app
- Silo culture
- Incremental in nature
- Cost of delay – High
- Queues & Congestion
- Missing Feedback loops
- Lack of continuous improvement
- Vanity metrics – After the facts
- Quality is not an outcome
- Lack of Systems thinking
- Response to change
- IT friction
- Technical debts

32. James Bach / Satisfice and Michael Bolton / DevelopSense
Rapid Software Testing

33. How do we do Agile development

38. experiment Develop &
Design
Build cleanly
& Simple
Foster
Testability

39. experiment
Develop & Design
Build cleanly
& Simple
Foster
Testability

43. Test This

51. Quality is not an outcome

52. Where to move…

54. Testing on the toilet

56. Testing is not a phase anymore,
it is a blended responsibility of the project teams to deliver
- Faster feedback loops
- Incremental value
- Business continuity
- Consistency & speed to deliver software on time.