Testing in Agile Team Environment by Sammy Kolluru

EXECUTIVE BOARD MEMBER, CSTB, 2010AGILE WORKING GROUP MEMBER, ISTQB, 2012

Sammy Kolluru

Connect with CSTB

LinkedIn: http://www.linkedin.com/groups?gid=1119087 Search for Canadian Software Testing Board (CSTB)

Facebook: https://www.facebook.com/cdnistqb

Email: [email protected] Request to be added to the CSTB’s mailing list.

Connect with me

LinkedIn: ca.linkedin.com/in/sammykolluru

Twitter: @sammykolluru

Blog: sammykolluru.blogspot.com

http://www.istqbcourses.ca/featured-blogs.html

Are you?

Why Certification?

Why ISTQB certification? Benefits to professionals Benefits to companies Benefits to Training Providers

Benefits to Professionals

International recognition of acquired competencies and skills

Possibility to use the logo “Certified Tester” (with identification of the specific level of certification)

Supports to the tester’s career path from foundation level to expert level

Benefits to Companies

The certification can be a competitive advantage for companies thanks to the increased level of reliability of the applications developed and the cost optimization of test activities, derived from the ISTQB® competencies.

The certification in consulting companies can offer high-level services to customers, increasing revenues and brand value.

Benefits to Training Providers

Accredited Training Providers can ensure a high standing in training services: ISTQB certified trainers Training material whose content, quality and syllabi

coverage is checked by ISTQB® Boards Early information and consultation on the evolution of

ISTQB® Glossary and Syllabi

Accredited Training Providers can benefit from specific logos and are listed on the ISTQB® Website.

Who is CSTB?

Created in January, 2007 as a not-for-profit organization

Creates and administers exams

Issues certificates

Accredits training providers

Participates in ISTQB meetings and ISTQB Working Parties

The CSTB (Canadian Software Testing Board) is the Canadian national branch of the ISTQB (International Software Testing Qualifications Board). As such, it advocates education and examination as a practical means to excel in the software testing field.

ISTQB’s Levels and Syllabi

ISTQB’s Global presence

ISTQB® can count on 45 Member Boards covering 69 Countries that represent over 90% of the world-wide GDP

Certified Testers

Today’s session

Testing in AGILE Team Environment

What is Agile team?

The core principle of the Agile team is to build quality in to the product.

On other hand, to develop with test based approach.

Agile team are highly cross functional, whole-team thinking approach and works in shorter sprint to build, test and integrate continuously.

ALWAYS keep Customer and Quality in mind.

What is Agile Testing, anyway?

Agile Testing does not mean testing in an Agile projects.

Testing an application in test, with a plan to learn and using that information to guide your testing.

Positively responding to changes.Highly cross-functionalWorking in a team to deliver quality product

in shorter sprint cycle

ISTQB’s presence in AGILE

ISTQB understands the significance of the Agile approach.

Agile working group is working towards implementing Agile Examination to certify as

Certified Agile Tester

Traditional Testing

Traditional Testing contd….

Testing is mostly passive during development.

Testing happens at the end, before the release.

There is not much time for testing. Testing gets squished. Ideally, coding may take longer than expected

Agile Testing

Iterative and IncrementalTesters can test each increment of finished

code. Iteration may be shorter, easier.

Team builds and test a small piece of code, ensuring it works before moving to next piece. and so on….

Developers are never ahead of testers as they are in-sync.

Story is never complete until it is TESTED.

Agile Testing contd…

Sprint 3

Epic A+B

Epic C

Agile Testing contd…

During each sprint, Epics are identified and groomed.

Each story is reviewed, acceptance criteria's are defined.

Each story is expanded, coded, tested.They may be a release after each sprint.

Whole-Team Approach

In Agile, Product quality is not the responsibility of just tester/ QA.

Whole team has the same responsibility for quality.

Do not think as a departments (Dev, QA…).Think as a skills and resources that is required to

deliver a top-notch quality product in shorter cycle.

Testing starts when the project is defined.Learn how application works as team drives up

the project.

Continuous Learning…

Testers need to practice continuously to develop skills.

Learn to adapt to changes.Perfect the skills by execution.Continuous Smoke Test to keep flaky builds

out of play.Testers need to reset the environment to

known state.

Continuous Learning contd…

Testers need to communicate to highlight critical skills and tactics to find bugs quickly.

Testers need to leverage the right tools to find the bugs quickly.

Testing role in Agile approach

Passive during Agile planning- important activities will be missed.

Testing late- diminish the advantages of the agile and becomes bottle neck.

Testers should advocate for customers concerns.

Testers should contribute for estimation, task definition, requirement clarification, scoping of work.

Testing role in Agile approach contd…

Testers should apply their skills to understand what user needs, collect live examples, error scenarios.

Stories should be broken into test related tasks- infrastructure, data, non-functional, privacy, security, robustness, business rules.

Testers should transform from passive participant to active advocate, address concerns and risks, leverage resources.

Requirement reviews in Agile

Majority of bugs have root cause in poor requirements

Testers should pro-actively help improve requirements quality

Testers should systematically validate requirements as they are developed

Scenario based reviews to ensure focus and scope

Ambiguity reviews- identify unclear areas Early defect detection, defect avoidance Identify Logical inconsistencies

Requirement reviews in Agile contd…

Requirements should be reviewed by domain experts, developers, QA to find additional defects.

Traditional Testing: Avg. bugs due to poor requirements: 55- 60%

Agile Testing: Avg. bugs due to poor requirements: Single digits

After you’ve finished Testing

Stake holders believe that testers revealed all bugs and fixed- wants to release

Testers should learn about a problem after code is live

Learn from A/ B Testing, Operational issues, customer sentiments.

Interact directly with customer support, learn from what is released to Production.

Audit, perform retrospective at the end of each sprint.

Lessons learned.

Principles of Agile Testers

Thank You

Q & A