1.

Define Agile:
Agile is an iterative and incremental approach to software development that
emphasizes flexibility, collaboration, customer feedback, and continuous
improvement. It prioritizes delivering working software in small, manageable
increments rather than following a rigid plan.

2. Define Agile testing:

Agile testing refers to the testing practices and methodologies adopted
within an Agile software development framework. It focuses on integrating
testing activities throughout the development lifecycle, promoting
collaboration between developers and testers, and adapting to changing
requirements and priorities.

3. List any two Agile principles:

Two Agile principles are:
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.

4. Define Agile testing quadrants:

Agile testing quadrants categorize different types of testing activities based
on their purpose and level of automation. The quadrants are divided into four
sections:
- Quadrant 1: Technology-facing tests (e.g., unit tests, component tests).
- Quadrant 2: Business-facing tests (e.g., acceptance tests, exploratory
testing).
- Quadrant 3: Business-facing technical tests (e.g., performance testing,
security testing).
- Quadrant 4: Technology-facing tests with a focus on non-functional
requirements (e.g., load testing, usability testing).
5. What is Agile test automation?
Agile test automation involves using automated testing tools and frameworks
to accelerate testing activities within an Agile development environment. It
aims to increase efficiency, improve test coverage, and provide rapid feedback
to developers by automating repetitive and time-consuming test cases.

6. Define Agile values:

Agile values, as outlined in the Agile Manifesto, include:
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.

7. What is Agile methodology?

Agile methodology refers to a set of principles and practices for iterative and
incremental software development, emphasizing adaptability, customer
collaboration, and continuous improvement. It includes various frameworks
such as Scrum, Kanban, Extreme Programming (XP), and Lean Software
Development, which guide teams in implementing Agile principles effectively.

Q.2)Long Answer
1. What is Agile testing? List its features.
- Agile testing is a collaborative approach to testing within Agile software
development methodologies.
- Features of Agile testing include:
- Continuous testing throughout the development lifecycle.
- Early and frequent testing to provide rapid feedback.
- Emphasis on customer collaboration and feedback.
- Flexible and adaptive to changing requirements.
 - Close collaboration between testers and developers.
- Iterative and incremental approach to testing.

2. What are the methods used in Agile testing? Explain two of them in detail.
- Methods used in Agile testing include:
1. Test-Driven Development (TDD): Developers write tests before writing
the corresponding code. The code is then developed to pass the tests. It
promotes better code design, modularity, and test coverage.
2. Behavior-Driven Development (BDD): BDD focuses on defining the
behavior of the system from the perspective of end-users. Tests are written in
a natural language format (Given-When-Then) to describe expected behavior,
facilitating collaboration between stakeholders.

3. With the help of diagram describe Agile testing strategies.

Agile Testing Strategies:
• Agile testing has four different approaches (Iteration 0, Construction
Iteration, Release End Game or Transition Phase and Production) which help us
to en1. Iteration 0:
• The iteration 0 is the first strategy of agile testing in which we execute the
preliminary
setup tasks such as finding people for testing, establishing testing tools,
preparing
resources or usability testing lab, etc.
• In iteration 0 strategy of agile testing, the below steps are accomplished:
o Verifying a business case for the project and boundary situations, and the
project
scope. Summarize the important requirements and use cases that will
determine the strategic trade-offs. Plan the initial project and cost valuation.
o Detecting the risk. Outline one or more candidate designs.
2. Construction Iteration:
• In construction iteration agile testing strategy, the majority of the agile
testing is
performed.
• The construction iteration is performed as a set of iterations on software
product in
order to create an increment of the solution. hance our product quality.
4. Explain Agile testing life cycle diagrammatically.
Agile Testing Life cycle:
• Agile testing life cycle completed into five different phases as shown in Fig

Let understand all the phases in Agile testing life cycle detail:
Phase 1: Impact Assessment: In impact assessment phase, we collect the
inputs and responses from users and stakeholders to execute the impact
assessment phase. The impact assessment phase is also known as the feedback
phase, which supports the test engineers to set the purpose for the next life
cycle.
Phase 2: Agile Testing Planning: In agile testing planning phase, the developers,
test engineers, stakeholders, customers, and end-users team up to plan the
testing process schedules, regular meetings, and deliverables.
Phase 3: Release Readiness: In release readiness phase, where test engineers
have to review the features which have been created entirely and test if they
are ready to go live or not and which ones need to go back to the previous
development phase.
Phase 4: Daily Scrums: Daily scrums phase, involves the daily morning
meetings to check on testing and determine the objectives for the day. And in
order to help the test engineers to understand the status of testing, the goals
and targets of the day are set daily.
Phase 5: Test Agility Review: In test agility review phase, the test agility phase
encompasses the weekly meetings with the stakeholders to evaluate and
assess the progress against goals. In simple words, we can say that the
agility reviews are implemented regularly in the development process to
analyze the progress of the development.
5. What are the advantages and disadvantages of Agile testing?
- Advantages:
- Early and continuous feedback.
- Flexibility to adapt to changing requirements.
- Faster time-to-market.
- Increased collaboration between teams.
- Higher quality software due to continuous testing.
- Disadvantages:
- Requires skilled and experienced team members.
- Lack of comprehensive documentation.
- Potential for scope creep without proper control.
- Difficulty in estimating project timelines accurately.

6. Differentiate between traditional testing and Agile testing.

- Traditional Testing:
- Follows a sequential, phase-based approach.
- Emphasizes comprehensive documentation.
- Testing occurs at the end of development phases.
- Less adaptable to changing requirements.
- Agile Testing:
 - Follows an iterative and incremental approach.
- Emphasizes collaboration and flexibility.
- Testing occurs throughout the development lifecycle.
- Adaptable to changing requirements and priorities.

7. List Agile principles in detail.

- Customer satisfaction through early and continuous delivery of valuable
software.
- Welcome changing requirements, even late in development.
- Deliver working software frequently, with a preference for shorter
timescales.
- Collaboration between business stakeholders and developers throughout
the project.
- Build projects around motivated individuals and give them the environment
and support they need.
- Face-to-face conversation is the most efficient and effective method of
conveying information to and within a development team.
- Working software is the primary measure of progress.
- Sustainable development, where developers can maintain a constant pace
indefinitely.
- Continuous attention to technical excellence and good design enhances
agility.
- Simplicity—the art of maximizing the amount of work not done—is
essential.
- The best architectures, requirements, and designs emerge from self-
organizing teams.
- Regularly reflect on how to become more effective, then tune and adjust
behavior accordingly.
8. Describe Agile values in detail:
 Agile values prioritize:
- Individuals and interactions over processes and tools: Emphasizes the
importance of collaboration, communication, and teamwork within the
development team and with stakeholders.
- Working software over comprehensive documentation: Focuses on
delivering functional software that meets customer needs rather than
extensive documentation.
- Customer collaboration over contract negotiation: Encourages active
involvement and feedback from customers throughout the development
process to ensure the product meets their expectations.
- Responding to change over following a plan: Acknowledges that
requirements and priorities may change, and values flexibility and adaptability
in responding to these changes.

9. What is Agile quadrant? What are its types? Explain with diagram:
Agile testing quadrants categorize testing activities into four quadrants based
on their purpose and level of abstraction:
- Quadrant 1: Technology-facing tests (e.g., unit tests, component tests).
- Quadrant 2: Business-facing tests (e.g., acceptance tests, exploratory
testing).
- Quadrant 3: Business-facing technical tests (e.g., performance testing,
security testing).
- Quadrant 4: Technology-facing tests with a focus on non-functional
requirements (e.g., load testing, usability testing).

10. Write a short note on: Automated tests:

Automated tests are scripted test cases that are executed automatically
using testing tools and frameworks without manual intervention. They help
improve efficiency, consistency, and reliability of testing by reducing human
errors and accelerating the testing process. Automated tests are commonly
used for regression testing, repetitive tasks, and scenarios that require
frequent execution.

11. With the help of diagram lists reasons for test automation in Agile
testing:
![Reasons for Test Automation in Agile
Testing](https://i.imgur.com/hfgbf0r.png)
Reasons for test automation in Agile testing include:
- Faster feedback on code changes
- Increased test coverage
- Repeatability and consistency
- Early detection of defects
- Support for continuous integration and delivery

12. What is Agile Manifesto? Describe in detail:

The Agile Manifesto is a guiding document that outlines the core values and
principles of Agile software development. It was created by a group of
software developers in 2001 to promote a more flexible, collaborative, and
customer-centric approach to software development. The manifesto consists
of four key values and twelve principles that emphasize individuals and
interactions, working software, customer collaboration, and responding to
change. It serves as a foundation for various Agile methodologies and
frameworks, such as Scrum, Kanban, and Extreme Programming (XP), which
help teams implement Agile principles effectively in their projects.