The document discusses agile testing quadrants and provides clarification. It introduces four quadrants - business-facing tests that support the team and critique the product from the customer perspective, and technology-facing tests that also support the team and critique from a technical perspective such as performance testing. Examples of different types of tests that fall into each quadrant are given. The importance of early testing, keeping automation, and gathering customer feedback are emphasized.

1. Agile Testing Quadrants Discussion
Mary Jiang
Dec, 6

2. Mary Jiang
• Sr. Project Manager
• PMP, CSM, CSD, CSPO and CSP
• 12+ years industry experience
• 6+ Agile experience
• Joined Perficient China GDC in 2008
• Focusing on QA & Testing
• Previously worked for UTstarcom, Siemens and
Alipay.com
About me

4. Is it agile testing?

5. Is it agile testing?

6. Is it agile testing?

7. Several questions regarding Agile Testing
• All agile testing must be automated?
• UAT is most important testing?
• When will we need to start to do testing?
• Do we still need tester in agile projects?
• Will we get enough test coverage in agile projects?
• …

8. Agile Testing Quadrants
12/8/2014 8
Q2 Q3
Q1 Q4
Application
Under Test
Business-Facing
Technology-Facing
Supportingtheteam
Critiqueproduct

9. Some Clarification
• Examples
• Simulations
• Exploratory Testing
• “ility” testing
• Critique product
12/8/2014 9

10. Agile Testing Quadrants
12/8/2014 10
Functional Tests
Examples
Story Tests
Prototype
Simulations
Exploratory Testing
Scenarios
Usability testing
User Acceptance Testing
Alpha/Beta
Unit Tests
Component Tests
Performance & Load testing
Security Testing
“ility” testing
Application
Under Test
Business-Facing
Technology-Facing
Supportingtheteam
Critiqueproduct

11. Business supporting test
• Support Team
– Right tools to elicit requirements
– From big picture to details
– Driving development with business – facing testing
• Critique product
– Demonstrate applications to stakeholders to get early feedback
– Use scenarios and workflow to test from end to end

12. Technical Supporting Test
• Support Team
– Unit tests
– Component Tests
– Continuous build
• Critique product
– Performance/load testing
– Security testing
– “ility” testing

13. “ Nothing is done until it is tested ”
Famous saying in Agile
12/8/2014 13

14. Where do we start?
• Test earlier
• Test driven requirement
• Test driven development
• Keep testing pass
• Big picture
• Pair Testing
• “Show me”
12/8/2014 14

15. Checklist
• Do we have clear acceptance criteria?
• Do we show prototypes to users before we start coding?
• Do we have specific test data?
• Do we have an automated build process and get quick feedback?
• Are we capture the right examples? Do we need more? Are we
basing our tests on these examples?
• Do we consider technological requirements early enough in the
development cycle?
• Do our business-facing tests help us to deliver a product that
matches customers’ expectation?
• …
12/8/2014 15

16. Automation
12/8/2014 16

17. Summary
• A software testing practice that follows the principles of agile
software development
• Involves all members of a cross-functional agile team, with
special expertise contributed by testers
• Testing from the customer perspective as early as possible
• Includes everything beyond unit and component level testing
• Does not just mean testing on agile project
12/8/2014 17

18. 12/8/2014 18

19. 12/8/2014 19