How to incrementally integrate QA in an Agile Development Process
37
-
Upload
myplanet-digital -
Category
Technology
-
view
1.814 -
download
4
description
As Drupal continues to grow to be a platform fit for large scale enterprise applications, integrating Quality Assurance (QA) into development processes will become more of a pressing concern. Well defined QA processes allow teams to release more features with less defects and less risk of regression than ad hoc development. Join us as we describe the journey our agile development teams have taken from the days of guess work and hopeful commits of code to a single master branch to static, visual, unit, functional, integration, and release testing. We will share the challenges we have faced, the solutions we have found, and the tools that we use. We’ll also give a glimpse into our future goals for continued incremental improvement, including test tracking and test automation. *This presentation was delivered at DrupalCamp Toronto 2013 by Shanly Suepaul, Everett Zufelt & Benjamin Woll*
Transcript of How to incrementally integrate QA in an Agile Development Process
Incremental Integration of QA
Agenda
Our incremental QA recipe•A dash of QA•A pinch of agile•A touch of automation•A good helping of open discussion
Background
I don’t always test my code
Incremental Evolution
1) Minimal to no testing2) Test cases written on feature level3) Workflow – peer review, code review, vdod4) End to end release testing
What we are tinkering with now
5) Pair Programming6) Automation 7) Test Driven & Behaviour Driven Development
Agile Approach
The Agile Manifesto (Abbreviated)
•Individuals and interactions over processes & tools•Working software over comprehensive documentation•Customer collaboration over contract negotiation•Responding to change over following a plan
A Really Reductive Explanation of Agile
Predictive: The WaterfallManifesto.
On Manifestos
A Really Reductive Explanation of Waterfall
On Interpretation
Creating digital products is an interdisciplinary undertaking. Equally, the process we use should also embrace diverse methods where they make sense.
Nunchuk skills, bow hunting skills.
Team Structure
Key Roles
Creative, Tech, & QA Reps
Key Roles
“We’re special”-ists.
Key Roles
Injecting The Agile Approach
Typical team plus embedded QA in the mix
Benefits –•cross pollination•right to the source•team ownership through full delivery cycle
•A Project Manager is the one who thinks 9 women can deliver a baby in 1 month.
•A Developer is the one who thinks it will take 18 months to deliver 1 baby.
•A Tester is the one who always tells his wife that this is not the right baby.
Context is King
•Truly knows acceptance criteria•Doesn’t just read and execute•Deeper understand of the product•Participates in scrums tenents
Cheesy Jokes
Developer: There is no I in TEAM•Tester: We cannot spell BUGS without U
Question: How many testers does it take to change a light bulb?•Answer: None. Testers do not fix problems; they just find them.
Value of X-Functionality
•Ability to learn and pick up other skills•Tester that moonlights in Drupal, CSS, content•Identify defects sooner, inline with development – $$$
Team Ownership
Outcomes
Whole Team QA Minded
Outcomes
Superior Product
Outcomes
Inspect and Adapt
What does tomorrow look like
•Automation options•selenium, behat
Test Driven Development•simple test, phpunit•Pair programming
collaboration tools
Benjamin WollEverett ZufeltShanly Suepal
Thank you!
Myplanet Digitalmyplanetdigital.com@myplanetdigital
On Bricolage
Ask why before what.
Process: Discovery
Wrapping Up
