Role of QA and Testing in Agile

Agile Testing An Overview on QA and Testing  A Generalized Agile Process  Agile Values  Agile Synthesized  Agile Tester Principle  Traditional vs. Agile Approach Agile Testing practices Focus of Agile Testing Role of a Tester in an Agile Project Why does it fail? Challenges in Agile? Testers Concerns about Agile Testing

QAIT CONFIDENTIAL

What is a difference between QA and Testing?

 QA is oriented to defect preventions  Testing is oriented to defect detection

QAIT CONFIDENTIAL 3

 Agile testing is all about applying agile values and principles to testing.

 The value of agile testing lies in effective communication between developers, testers and the product owner

QAIT CONFIDENTIAL

 Individuals and interactions over processes and tools  Working software over documentation  Customer collaboration over contract negotiation 

esponding to change over following a plan

 + 12 more detailed principles

QAIT CONFIDENTIAL

Release
Iteration 1 Feature 1 Feature 2 Feature 3a Iteration 2 Feature 3b Feature 4a Iteration 3 Feature 4b Feature 5 Iteration Feature 4c Feature 6 Feature 7 Backlog Feature 8 Feature 9 .

QAIT CONFIDENTIAL

Increase the rate of delivery (usually with smaller increments)

QAIT CONFIDENTIAL

Increase the rate and quality of feedback

Reducing Waste
QAIT CONFIDENTIAL 8

QAIT CONFIDENTIAL

Reference Agile QA Testing by Elisabeth Hendrickson

QAIT CONFIDENTIAL 14

 Provide continuous feedback  Deliver value to the customer  Enable face-to-face communication  Have courage  Keep it simple  Practice continuous improvement  Respond to change  Self-organize  Focus on people  Enjoy
QAIT CONFIDENTIAL 11

 High Value features first

 Continuous Integration with pre/post release build automation

QAIT CONFIDENTIAL

12

Test Driven Development (TDD)

A software development technique which ensures that the software being developed is 100% covered by unit test cases

Write the Test

Fail

Execute the build

Pass

Coding
Fail

Execute the build

Pass

Refactor
QAIT CONFIDENTIAL 13

Automated Acceptance tests

 Define Done  Represent requirements

Automated Unit Tests Manual Exploratory testing

QAIT CONFIDENTIAL

 Derive Design  Represent Specifications

 Provide additional feedback

14

Testers are integral part of the team Participate in Release/Iteration planning Start Testing activities from the day 1 Collaborates with the customer to define the acceptance test criteria Validates that the system is doing exactly what it is supposed to do Tests Stories once they are complete Focuses on test automation Focuses more on exploratory testing Practices pair testing (similar to pair programming) Collaborates with Development team Provides continuous feedback to the team
QAIT CONFIDENTIAL 15

Agile
Better for small projects Moves automation near development (better use) Better when good contact with customer Require experience and trainings New experience

Waterfall
Big projects where requirement not change often Easier in management Easier when team is located in different localizations

QAIT CONFIDENTIAL

16

Waterfall model Ideal Case

QAIT CONFIDENTIAL

17

Much Encountered Reality

QAIT CONFIDENTIAL

18

Criteria
Understanding Requirements Planning Designing of Test Cases Manage Change Progress review Quality Responsibility
QAIT CONFIDENTIAL

Traditional
Upfront Plan one time delivery which has to happen way later All Upfront Prohibit Change Milestone document review Quality Engineer
19

Agile
Constant interaction within the team and with the Product Owner Continuous sprint by sprint planning, deliver important features first Evolving and Iteration Wise Adapt and adjust at every release and iteration boundary See working software every iteration and every release Entire team

Waterfall model

Agile models (XP)

QAIT CONFIDENTIAL

20

Agile
One project team Close communication with developers (cooperate) The same aim Together analyze requirements, planning Parrelal work with developers

Waterfall
Different team Mostly communication only by defect management tools Different aims Not involve in requirement analyzing, planning Time delay between coding and tests

QAIT CONFIDENTIAL

21

Starts by looking at prioritized personal work queue Identifying the work items for the day Attending the standup meeting Collaboration with Dev Team (seeking and offering support) Depending on the type of work item Writing acceptance Criteria Writing the test case Automating a test case Executing a test case (manually)

QAIT CONFIDENTIAL

22

Hard! Agile does not fix everything Are we ready for a change? Practicing TDD is not easy A move from Manual testing to Automated testing Agile Testing needs a coder-tester profile It makes products to be delivered faster Partial adoption?

QAIT CONFIDENTIAL

23

Few Tester Thoughts

QAIT CONFIDENTIAL

24

Tester manage by developer (project manager) Lost of identity No defined task (self-organize) No Agile training No carrier path Communication problem

QAIT CONFIDENTIAL

25

Q&A
http://www.qainfotech.com/blog/ | www.qainfotech.com

QAIT CONFIDENTIAL

26