A WEBINAR

ON
Agile Testing Principle

21st October 2023

 ● What is Agile Methodology
● Types of Agile Methodology
● What is Agile Testing
● 8 Principles of Agile Testing
● Role of QA in Agile
● Agile Testing Mindset

AGENDA ● What skills should a Agile Tester Have

● 7 Testing challenges in Agile
● Conclusion
● Q&A
MEET THE SPEAKER
Seasoned Technically-skilled and accomplished software testing
professional with over 5 years of progressive expertise in delivering
quality testing services on projects across multiple industries like
fintech, educational, e-commerce, hospital, entertainment etc.
Possessing a good understanding of both Software Development Life
Cycle and Software Testing Life Cycle. Privilege to have worked with
companies like Netow Solutions, Summitech (NG), Pangaea (US),
Prospa, ABinBev, Pathian Partners & QaceTech

Name: Akinwale Funmilayo

Years of Experience: 5+
Current Role: Senior QA Engineer
Hobbies: Music, Cooking
Courses

Agile is about looking for the simplest path, and about

breaking a long road into shorter trips.

Simple is NOT QUICK & DIRTY

At the end of each short TRIP you neeed to stop to

analyse each steps and learn from it.

5
What is Agile Methodology?
Courses

As the complexity of software development process is

increasing continuously, the software testing approaches
needs to evolve to keep up with the development approaches.
Agile testing is a new age approach which focuses on testing
smarter rather than putting a lot of efforts yet it delivers
high-quality products.

7
What is Agile Methodology?

AGILE methodology is a practice that

promotes continuous iteration of
development and testing throughout the
software development life cycle of the
project. Both development and testing
activities are concurrent unlike the
Waterfall model.

8
Agile Model
By breaking the product into cycles, the Agile model
quickly delivers a working product and is considered a
very realistic development approach. The model produces
ongoing releases, each with small, incremental changes
from the previous release. At each iteration, the product is
tested.

This model emphasizes interaction, as the customers,

developers and testers work together throughout the
project. But since this model depends heavily on
customer interaction, the project can head the wrong way
if the customer is not clear on the direction he or she
wants to go.

www.netowsolutions.com
9
10
Testing in Agile

What Does it Mean to Test on an Agile

Team?

Agile principles are all about being

collaborative, flexible and adaptive. It’s
built on the premise that software teams no
longer have years to bring new products to
market. It does this by encouraging teams
to regularly show off their work and gather
feedback so that they can adapt to change
quickly.

1
1
Testing in Agile

Agile Methodologies Types

However, the most popular methodologies amongst all of them are:

❖ Scrum
❖ Kanban

1
2
Testing in Agile

Scrum

1
3
Testing in Agile

Scrum

14
Testing in Agile

Kanban

1
5
What is Agile Testing?
Testing in Agile

What is Agile Testing?

AGILE TESTING is a testing practice that follows the rules and

principles of agile software development. Unlike the Waterfall
method, Agile Testing can begin at the start of the project with
continuous integration between development and testing.

1
7
Testing in Agile

How to Align Testing with an Agile Delivery Process

Once you determine which testing methodology is right for your

organization, you’re not quite done yet. You still need to align
testing with the delivery. To achieve this goal we recommend a
three-pronged approach:

1) Get involved in the early stage of development

2) Test frequently
3) Hit the ground running with test creation
1
8
9 Principles of Agile Testing
 1. Early and Continuous Testing:
Testing in Agile

Principle: Testing activities should commence as early as possible and be performed

continuously throughout the development lifecycle.
Rationale: Early testing helps identify defects promptly, reducing the cost of fixing issues
later in the development process.

2. Embrace Changes:
Principle: Welcome changes in requirements, even late in the development process. Agile
processes harness change for the customer's competitive advantage.
Rationale: Agile testing should be adaptable to evolving requirements, ensuring the product
meets customer needs effectively.

3. Collaboration:
Principle: Promote collaboration between developers, testers, and other stakeholders
throughout the project.
Rationale: Open communication fosters a shared understanding of requirements, improving
the quality of the delivered product.
2
0
Testing in Agile
4. Business-Driven Testing:
Principle: Testing activities should align with business priorities and objectives.
Rationale: Ensuring that testing efforts are aligned with business goals enhances the
value of the testing process.

5. Risk-Based Testing:
Principle: Focus testing efforts on areas with the highest risk of failure.
Rationale: Efficiently allocate testing resources to mitigate potential risks, ensuring a
high-quality product.

6. Iterative and Incremental Testing:

Principle: Adopt an iterative approach to testing, building and testing small increments
of functionality.
Rationale: Frequent testing of small increments allows for early detection of defects
and supports continuous improvement.
2
1
Testing in Agile
7. Automate Regression Testing:
Principle: Automate repetitive and time-consuming regression tests.
Rationale: Automation allows teams to quickly verify existing functionality after
changes, reducing manual effort and enhancing efficiency.

8. Continuous Feedback:
Principle: Encourage a culture of continuous feedback, both within the development
team and from stakeholders.
Rationale: Regular feedback promotes transparency, identifies issues early, and
ensures the delivered product meets expectations.

9. Focus on Customer Satisfaction:

Principle: The ultimate measure of progress is delivering valuable software to the
customer.
Rationale: Customer satisfaction is the primary goal, and testing plays a vital role in
achieving a high-quality product that meets customer expectations. 2
2
Role of QA in agile?
Testing in Agile

But what exactly is the role

of QA in agile?

What can a tester do to help

initiate a cooperative working
relationship with the entire
team?

2
4
Testing in Agile

❖ 1. Attend sprint-planning sessions.

❖ 2. Attend daily stand ups.
❖ 3. Test throughout the sprint.
❖ 4. Meet with developers for short, hand-off demonstrations.
❖ 5. Attend sprint retrospectives.
❖ 6. Document test cases.

2
5
Agile Testing Mindset
Testing in Agile

Agile Testing Mindset

Agile Testers need to break away from the

principles and working methodologies of
traditional software development. In order to
succeed as an Agile Tester, the right mindset is
required.

2
7
Testing in Agile

❖ Quality Assistance over Quality Assurance

❖ Continuous Testing over Testing at the End
❖ Team Responsibility for Quality over Tester’s Responsibility
❖ Whole Team Approach over Testing Departments and Independent Testing
❖ Automated Checking over Manual Regression Testing
❖ Technical and API Testing over Just GUI Testing
❖ Exploratory Testing over Scripted Testing
❖ User Stories and Customer Needs over Requirement Specifications
❖ Building the Best Software over Breaking the Software
❖ Short Feedback Loop over Delayed Feedback
❖ Preventing Defects over Finding Defects
2
8
What Skills Should an Agile Tester
Have?
Testing in Agile

What Skills Should an Agile Tester Have?

In addition to the skills required for a tester working in a traditional waterfall

project, a tester in an Agile team should be competent in test automation,
test-driven development, acceptance test-driven development, white-box,
black-box, and experience-based testing.
As Agile methodologies depend heavily on collaboration, communication, and
interaction between the team members as well as stakeholders outside the
team.

3
0
Testing in Agile

❖ Be positive and solution-oriented with team members and stakeholders

❖ Display critical, quality-oriented, skeptical thinking about the product
❖ Actively acquire information from stakeholders (rather than relying entirely on
written specifications)
❖ Accurately evaluate and report test results, test progress, and product quality
❖ Work effectively to define testable user stories, especially acceptance criteria, with
customer representatives and stakeholders
❖ Collaborate within the team, working in pairs with programmers and other team
members
❖ Respond to change quickly, including changing, adding, or improving test cases

3
1
Testing Challenges in Agile
Testing in Agile

5 Testing Challenges in Agile

The continuous nature of agile development processes raises a few serious
testing challenges:
1. Changing Requirements
2. Not Enough Information
3. Technical Skills
4. Frequent Regression Cycles
5. Lack of Communication

3
3
Conclusion
Testing in Agile

Within an Agile team, each team member is responsible for

product quality and plays a role in performing test-related
tasks.

Agile testing not only facilitates the early detection of

defects but also reduces the cost of bugs by fixing them
early. This approach also yields a customer-centric
approach by delivering a high-quality product as early as
possible.

3
5
Q&A
 OUR ONBOARDING PROCESS

Follows
Twitter: https://twitter.com/qacetech
Facebook: https://web.facebook.com/qacetech
Instagram: https://www.instagram.com/qacetech
LinkedIn: https://www.linkedin.com/company/qacetech

Join our Communities

WhatsApp: https://chat.whatsapp.com/LNZLmh7iiwf8ZmkZWBnYmz
LinkedIn: https://www.linkedin.com/groups/9515132/
 THANK YOU.
We look forward to hearing from you

Contact Us www.qacetech.com hello@qacetech.com