[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile

CONTEXT-DRIVEN TESTING IN AGILE

31 JAN 2015

Nhat Do (DD) [email protected]

Vu Duong (EM) [email protected]

mailto:[email protected]



AGENDA

Introduction

Context-Driven Testing in Agile

Q & A

2 Context-Driven Testing in Agile

GAME WORKSHOP


Context-Driven Testing in

Agile


CHECKING VS TESTING

Checking

Is confirmation Is the system working like this?


CHECKING VS TESTING

Checking



Give a binary result Pass or Failed.

CHECKING VS TESTING

Checking




Is machine decidable It’s passed, ready for release

CHECKING VS TESTING

Checking





Is focused on making sure

the program does not fail I try to find bugs as much as

possible

CHECKING VS TESTING

Checking







possible

Proves bugs exist, not their

absence

CHECKING VS TESTING

Checking







possible


absence

Is Exploration and learning I’m not sure why system has to

perform like this, not like that

Testing

CHECKING VS TESTING

Checking







possible


absence

Testing



Has an open-ended result What if system shutdown suddenly

CHECKING VS TESTING

Checking







possible


absence

Testing




Requires sapience System would be better if…..

CHECKING VS TESTING

Checking







possible


absence

Testing





Is a question that we want

to ask of the program Hey, do we want to see where his

package in US?

CHECKING VS TESTING

Checking







possible


absence

Testing





Is a question that we want

to ask of the program Hey, do we want to see where his

package in US?

Is a challenging. Intellectual

process

CASE STUDY


Case Study from VietNam Post Tracking System

WHAT’S CONTEXT-DRIVEN TESTING?


Context-driven testing is a model for developing and debugging computer software that takes into

account the ways in which the programs will be used or are expected to be used in the real world.

Tech Target

Context-driven testing is a certain type of software testing that considers the product’s use in the

field, or a performance or production environment. It is one way that developers assess software as it

is built, looking for flaws and otherwise optimizing its design before its eventual final release

Techopedia

CONTEXT-DRIVEN TESTING PRINCIPLES


The value of any practice depends on its context.




There are good practices in context, but there are no best practices.





People, working together, are the most important part of any project’s

context.






context.

Projects unfold over time in ways that are often not predictable.






context.


The product is a solution. If the problem isn’t solved, the product

doesn’t work.






context.



doesn’t work.

Good software testing is a challenging intellectual process.






context.



doesn’t work.


Only through judgment and skill, exercised cooperatively throughout

the entire project, are we able to do the right things at the right times to

effectively test our products.






context.



doesn’t work.





Practices






context.



doesn’t work.





Practices

Projects






context.



doesn’t work.





Practices

Projects

Testing

A Nice Marriage of Agile and Context-Driven Testing?


A NICE MARRIAGE OF AGILE AND CONTEXT-DRIVEN TESTING?


People

Focus

People, working together, are the

most important part of any project’s

context.

CDT Belief



Individuals & Interactions

over process and tools People

Focus

Agile Spirit People, working together, are the


context.

CDT Belief



Agile Spirit CDT Belief Individuals & Interactions


Focus

Project

Uncertainty



context.

Projects unfold over time in ways

that are often not predictable.





Focus

Responding to Change

over following plan

Project

Uncertainty



context.







Focus


over following plan

Project

Uncertainty

Product

Focus



context.



The product is a solution. If the

problem isn’t solved, the product

doesn’t work.





Focus


over following plan

Working Software

over comprehensive documentation

Project

Uncertainty

Product

Focus



context.





doesn’t work.





Focus


over following plan

Working Software


Project

Uncertainty

Product

Focus

Client

Involvement



context.





doesn’t work.

Only through judgment and skill,

exercised cooperatively throughout

the entire project, are we able to do

the right things at the right times to

effectively test our products





Focus


over following plan

Working Software


Customer Collaboration

over contract negotiation

Project

Uncertainty

Product

Focus

Client

Involvement



context.





doesn’t work.

Only through judgment and skill,

exercised cooperatively throughout

the entire project, are we able to do

the right things at the right times to

effectively test our products

Your Turn – When it could go wrong?


WHEN IT COULD GO WRONG?


When ONLY developers do testing; when it is not matured enough (no

planning, no discipline, no documentation)





When thinking that everyone can test and all can be automated





When thinking that everyone can test and all can be automated

Key Question: Is your team “mature enough” for this marriage?



When ONLY developers do testing; when it

is not matured enough (no planning, no

discipline, no documentation)

When thinking that everyone can test and all

can be automated

Key Question: Is your team “mature enough”

for this marriage?

Q & A


APPENDIX


http://www.hcmc-stc.org/blog/marrigage-of-scrum-and-session-based-

testing

- http://www.mountaingoatsoftware.com/agile/scrum/overview

- http://www.satisfice.com/sbtm/

http://www.hcmc-stc.org/blog/marrigage-of-scrum-and-session-based-testing















http://www.mountaingoatsoftware.com/agile/scrum/overview



http://www.satisfice.com/sbtm/

http://www.satisfice.com/sbtm/

THANK YOU

© 2013 KMS Technology

http://www.kms-technology.com