agile testing

12

Upload: rainar-uett

Post on 22-Jan-2015

274 views

Category:

Technology


4 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Agile testing
Page 2: Agile testing

• Time, budget, functionality.

• But wait...

• What about customer value?

Page 3: Agile testing

• Individuals and interactions over processes and tools

• Working software over comprehensive documentation

• Customer collaboration over contract negotiation

• Responding to change over following a plan

Page 4: Agile testing

• Testing will be driven by what is important to a user, rather than to fulfill a process

• Where regulations are applied – the regulator will be the key customer to the product

• Communication between tester, customer, designer

Page 5: Agile testing

• Many test techniques require extensive documentation

• Work with software directly:

– Reading unit tests

– Exploring system

– Testing interfaces

• Interact with designers and developers to understand restrictions and imperatives of system

• Working code ≠ working software

• Development of the product is helped by a simple, shared set of stories that describethe system

Page 6: Agile testing

• Tester extending the role of a customer – becoming a „Bad Customer“

• Working closely with the customer vs become customers proxy

• Iterative collaboration

• What is out:

– Prioritising based on a fixed risk assessment

– Testing only what has been agreed in the contract

– Reporting bugs only against fixed requirements

Page 7: Agile testing

• No fixed requirements

• Test plan for the iteration

Page 8: Agile testing

• Comprehensive testing, but not by testers.

• The code is built into a working system very regularly, often daily, hourly or on each check-in. ‘Breaking the build’ with your newly checked-in code is a cardinal sin.

• The vast majority of tests are automated, and pass every time

• Agile testers know the scope of each test (unit, integration, confirmation tests)

• Test specialists can influence the scope of these unit tests, using their knowledge to help the coders

Page 9: Agile testing

• Everyone is responsible!

• Testers make the quality transparent

Page 10: Agile testing

AUTOMATED

Functional acceptance tests

MANUAL

Exploratory testing

Usability testing

Unit tests

Integration tests

System tests

AUTOMATED

Non-functional acceptance tests(Performance,

Scaling)

MANUAL/AUTOMATED

Business facing

Technology facing

Su

pp

ort

pro

gra

mm

ing P

roje

ct tran

spa

ren

cy

Page 11: Agile testing

Q&A

Page 12: Agile testing

Thank you!