agile testing experiments

MY EXPERIMENTS IN AGILE TESTING@YAHOO!

Baiju Joseph

Director QE & RE , Yahoo!

baiju@yahoo-inc.com

12 Jul 2013

UNICOM World Conference –

Next Generation Testing

08 – 12 July, Le-Meridien, Bangalore

AGENDA

• Why Experiments

• Agile Testing

• Thinning the boundary

• Automation Framework

• Mind Maps

• Test Huddles

• Group Tests

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

WHY EXPERIMENTS

Source : Crisp's Blog

WHY EXPERIMENTS

Source : Crisp's Blog

WHY EXPERIMENTS

• Continuous Improvement

• Prove your Predictions

• What would happen IF…?

• Toss out Failed results

• Propel successful ideas

AGILE TESTING

“The main reason that testing at the end of

a development cycle finds problems is not

that problems were put in near the end, it

is that testing was put off until then…”

-Ron Jeffries

AGILE TESTING

8

FACTORS HINDERING ACCELERATION

• Mass – QE process, tools,

methodologies, mindset etc…

• Horse Power – Skill shortage, non

availability of QE Architects

• Running track friction

• Team synergy

• Culture and practices

AGILE – BASIC SUCCESS MANTRAS

• Build quality In

• Why->How->What of (user stories)

• Test early Test Often

• Unit Tests (75%+ code coverage)

• ROI based automation (75%+)

• CI/CD aka Release Runways

AGILE – BASIC SUCCESS MANTRAS

Most important : agile mindset

E1. THINNING THE BOUNDARY

THINNING THE BOUNDARY

• Developer – Tester boundary

• Experiment

• Developers to do more Testing

• Unit , Smoke , Functional

• Automated Test

• Testers to do more Development

• Test Framework , Tooling

• Fix bugs…

THINNING THE BOUNDARY

• Results (Few Pass , Many Fails)

• Pass : backend scrum teams

• Fail : front end scrum teams

THINNING THE BOUNDARY

• Revised Experiment

• Dev – Unit , Smoke automation

• QE – Framework , Functional auto

TAKE AWAYS

• Developer – Tester boundary thinning

• Objective : Build Good Quality Code

first time

• Developers to understand the test

cases before coding

• Testers becoming more technical ,

understand Architecture , Unit Tests …

• Not just defect finding : can we also

show the way towards the fix

HOW TO EXPERIMENT

• Evangelize the “WHY” by leadership

• Cross Trainings

• Listen to the team on how its working

and fine tune

• Worked better on

• Brand New projects , Features

• Small Scrum teams

• Co located

E2: AUTOMATION FRAMEWORK

• Feature Coding & Test Coding using

different language

• Result : FAIL

• Automation framework change – all

coding including test in same

language

• Result : Good progress

AUTOMATION FRAMEWORK TAKE AWAYS

• Revised Experiment

• FE :

• Dev – javascript

• Unit Test , Functional Test – javascript

• BE :

• Dev – Java

• Unit Test , Functional Test - Java

• Dev writing smoke tests , good quality code

AUTOMATION FRAMEWORK

E3: MIND MAPS

• For test planning

• Test case brainstorming

• Test reviews

• RESULT :

• Quicker

• Easy to review especially for

distributed teams

MIND MAPS

MIND MAPS

MIND MAPS

MIND MAPS

MIND MAPS – TAKE AWAYS

S# Activity Project Savings/Returns

Without Mind Maps With Mind Maps

01 Test Plan Discussion 1 Hour 20 Minutes 65%

02 Test Case Designing 3 PD 0.5 PD 80%

03 Test Case

Review/Walkthrough

2 Hours 30 Minutes 75%

04 Incorporating review and

feedback Inputs

2 Hours NIL 100%

05 Test Case Review Inputs 1X 5X 5 Times Review Inputs

• Free Tools –

• FreeMind

• Xmind

• Paid Tools –

• MS Visio

• Mind Manager

• Xmind Pro

MIND MAPS

MIND MAPS

E4 : TEST HUDDLES

TEST HUDDLES

TEST HUDDLE – TAKE AWAYS

• Better Clarity of

• Features ,

• User Stories ,

• Aacceptance criteria ,

• Tests

• ATDD

TEST HUDDLES

E5 : GROUP TESTS

GROUP TESTS – TAKE AWAYS

• Early feedback

• Theme based (ex: browser ,3 screens…)

• Sev1 , Sev2s are resolved in same sprint

WHERE WE EXPERIMENTED

• Cloud

• Mobile

• Web applications with Millions of PVs

• Machine learned algorithms

• Back end

• Front end

IS THIS RELEVANT FOR YOU ?

Source : Crisp's Blog