Challenges with agile testing process and how to debug and troubleshoot these challenges

LOGO
www.unicomlearning.com
Chandan Lal Patary
India Testing Week 2013
Challenges with Agile testing process,
How to debug and troubleshoot the challenges?
12th December and
Bangalore
www.nextgentesting.org

 Agenda:
 “Challenges with measuring quality for Agile distributed
research type project” – a case study
 Testing skill
 Agile issue
 3C magic!
 Automation? How much and when?
 Debugging? Combination of multiple agile practices
 Lean approach
 ……
Challenges with Agile testing

 Agile:
 Agile – denotes “the quality of being agile; readiness for motion;
nimbleness, activity, dexterity in motion” according to the Oxford
Dictionary
 In agile software development testing and development of
software runs parallel in order to achieve higher level of quality.
 Find and fix bugs as soon as possible. Fixing bugs and errors
sooner, implies to save time, cost, resources and maximization
to quality.

 Agile:
 Agile placed a dramatic change in testing practices by shifting
the testing responsibility from QA tester to developer
 Merge development and testing
 The Agile Manifesto does not use the word “testing” even once.
Accept the changes as farmers accept both good and bad
weather.
 Test challenges arises due to rapid changes in the product and
its correct behavior. Test team has to part of change process
else it inject inefficiency.

Case study

 Testing patient under
critical condition
 Testing is the headlights
of the project .Where are
you now? Where do you
headed?
 A “bug” is anything that
could bug a user.
Testers don’t make the
final call.
Test display for Decision

Headlight of an project
 Poor testing can cause damage to the product

 Drug development process vs
software development process
 We don’t understand software
until we have used it.
Drug Development Process

 Testing to provide
feedback on an
ongoing basis about
how well the emerging
product is meeting the
business needs.
 This sounds like a
small shift, but it has
profound implications
 Agile testing is a
mindset change
 You build it , I break it
to you build it , you
break it
 Testing is headlight for
a project

Who is moving away my cheese?

 Agile moved development from process oriented to people oriented.
 Writing code, writing script
 Extreme collaboration
 Domain competency
 Act like customer, write acceptance test
 Don’t behave like test engineer, think from quality improvement point of
view.
 The role of QA is not „police“, and testing goes beyond „pass“ or „fail”.
 10,000 hour rule: the key to success in any field is to practice a specific
activity for 10,000 hours, an idea based on a study by Anders Ericsson
Skills require for future

 Blood Test result:
What it tells
compare to
baseline?
Test Result

Testing types
 Similar to blood test report?

 Do we have customer who
writes the acceptance
criteria ? Or customer
representative ?
 If this acceptance test
passes, then the feature is a
success
 Shortening Feedback Loops
Acceptance test driven
development

Metrics and Dashboard

How to be more Agile

 How much testing should be done?
 Risks based test strategy increased productivity , Quality and
flexibility
 Encourage Light weight testing so achieve execution speed and
reduce time to market.
Risks Based Test Strategy

 Agile automation is sometimes about researching solutions
 Automated testing helps us meet our regression and performance
testing objectives within the tight timeframes of a two-to four-week
sprint.
 Delay in automation causes schedule issue
 Complexity in automation increase the effort
 Not writing generic script, maintainability issue
 Integrated with daily build will speed up the process
 Stability of the features causes delay in automation
 Test automation is vulnerable to instant obsolescence
 Test automation progresses when supported by dedicated
programmers (toolsmiths).
Automation

Agile testing

 Sustainable test team structure
with product portfolio
 Testers identify with their
product and not their role
 Test specialists always provide
most value to our agile project
by looking for novel or
unexpected risk
 Encourage pair testing
 Team is building An “agile
testing mind-set” which is
 Customer-focused,
 Results-oriented,
 Craftsman-like,
 Collaborative,
 Creative,
 Eager to learn,
 and passionate about
delivering business value in a
timely manner
Team Warriors

Exploratory Test and Explorer
 Exploratory testing is the best way of
digging into the product and learning it
well.
 Every tester must be a expert user and
should know ins and outs of the product

Tools
 Consider creating a small team of test
toolsmiths.
 With Toolsmiths build or use tool for rapid
automation.

Testing is everybody’s job

Bugs life

Silver Bullet Solution
• Why Do Errors Happen in
Software Development?

 Smells are a good
way to diagnose
what is wrong with
the current way
things are done.
 Recognizing such
bad smells and
responding to them
at the right time is
essential to keeping
projects on track
Smells

 Lean principles, the right way to
tackle bugs is by preventing them
to appear altogether, and by
eliminating them as soon as
possible.
 insufficient testing, leading to
avoidable process repetition
 Use automation to identify most of
the waste
 Apply 3 E Principle – Value for
Money – “Efficiency, Economy and
Effectiveness” through Lean testing
 Just in time work
Lean
Toyota manufacturing process Shigeo Shingo suggests that we engineer our processes to prevent defects rather than
focusing on processes to find defects. This is a critical part of lean thinking that bears repeating: Use processes that
prevent defects rather than relying on those that try to find them.

Key success factor

Key success factor: Collaboration

Key success Factor: Communication

Key success Factor: Collocation

 Communication
between tester,
customer and designer
than to maintain
independence of the
test team
 Automated testing is at
the heart of agility
 Testing is not one
person’s job; it’s the
responsibility of the
whole team
 Run tests at multiple
levels
 Release often-
Continuous integration-
TDD-Continuous improve
 Cultural challenges
need to manage
efficiently
Take Away!
Quality is a Journey, not a Destination

Organized by
UNICOM Trainings & Seminars Pvt. Ltd.
contact@unicomlearning.com
Speaker name:Chandan Lal Patary
Email ID:patarychandan@gmail.com
Thank You

Challenges with agile testing process and how to debug and troubleshoot these challenges

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Challenges with agile testing process and how to debug and troubleshoot these challenges

Similar to Challenges with agile testing process and how to debug and troubleshoot these challenges (20)

More from Chandan Patary

More from Chandan Patary (20)

Recently uploaded

Recently uploaded (20)

Challenges with agile testing process and how to debug and troubleshoot these challenges