Scribd
Upload
5 views

agile testing_intro & principles

Agile Testing is a software testing practice integrated with agile development, involving the entire project team and emphasizing continuous testing throughout the development life cycle. It features shorter iterations, updated test plans for each release, and promotes collaboration between testers and developers for immediate feedback. While Agile Testing offers advantages like improved quality and communication, it also presents challenges such as potential misunderstandings and the need for strong team coordination.

Uploaded by

abhijitsingh3rdtime
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
5 views

agile testing_intro & principles

Agile Testing is a software testing practice integrated with agile development, involving the entire project team and emphasizing continuous testing throughout the development life cycle. It features shorter iterations, updated test plans for each release, and promotes collaboration between testers and developers for immediate feedback. While Agile Testing offers advantages like improved quality and communication, it also presents challenges such as potential misunderstandings and the need for strong team coordination.

Uploaded by

abhijitsingh3rdtime
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Introduction to Agile Testing

Agile Testing is a software testing practice that follows the principles of agile software
development. Agile Testing involves all members of the project team, with special expertise
contributed by testers. Testing is not a separate phase and is interwoven with all the
development phases such as requirements, design and coding and test case generation.
Testing takes place simultaneously through the Development Life Cycle.

Unlike the WaterFall method, Agile Testing can begin at the start of the project with
continuous integration between development and testing. Agile Testing is not sequential (in
the sense it's executed only after coding phase) but continuous. An agile team works as a
single team towards a common objective of achieving Quality. Agile Testing has shorter time
frames called iterations (say from 1 to 4 weeks). This methodology is also called release, or
delivery driven approach since it gives a better prediction on the workable products in short
duration of time.

Test Plan for Agile

Unlike the waterfall model, in an agile model, a test plan is written and updated for every
release. The agile test plan includes types of testing done in that iteration like test data
requirements, infrastructure, test environments, and test results. Typical test plans in agile
includes

1. Testing Scope
2. New functionalities which are being tested
3. Level or Types of testing based on the features complexity
4. Load and Performance Testing
5. Infrastructure Consideration
6. Mitigation or Risks Plan
7. Resourcing
8. Deliverables and Milestones

ADVANTAGES OF AGILE TESTING


 Whole team responsible for the quality. Testing is done after the development is complete but
in Agile, the whole team is responsible for the quality of work. They also mix discipline
where you can find one tester working with co ordination with the other developers.
 Here communication also plays an important role as when testers and developers work
together in a team they can easily communicate with each other.
 As they are working together in a team, immediate feedbacks can be given where the
developer can fix the bug then and there when the code is still fresh in his mind.
 As the coding and testing time is so close to each other, the developer need not have to put in
new code to the project as he can fix up the bug problem without any difficulty.
 Agile locks the teams into short sprints letting each team focus on completing a small set of
features.
 Since testing is done throughout the software process, testing can’t be cut. It has to go on in
order to avoid the bug that arises.

DISADVANTAGES OF AGILE TESTING


 Agile requirements are barely sufficient. This eliminates wasted efforts on deliverables that
do not last which saves time and also money. If proper team work and communication is not
there between developers and testers, then there will be a clear misunderstanding and will be
difficult for team members that are used to do everything being defined as upfront.
 Flexibility to change ensures the right to delivery of the right product at the correct time.
Without the maturity of a strong and clear vision, and the discipline of fixing timescale and
trading scope, is potentially very dangerous.

Agile Testing Principles

The principles of Agile testing are −


 Testing moves the project forward − Continuous testing is the only way to ensure
continuous progress. Agile Testing provides feedback on an ongoing basis and the
final product meets the business demands.
 Testing is not a phase − Agile team tests alongside the development team to ensure
that the features implemented during a given iteration are actually done. Testing is
not kept for a later phase.
 Everyone tests − In agile testing, the entire team including analysts, developers, and
testers test the application. After every iteration, even the customer performs the
User Acceptance Testing.
 Shortening Feedback Loops − In Agile Testing, the business team get to know the
product development for each and every iteration. They are involved in every
iteration. Continuous feedback shortens the feedback response time and thus the cost
involved in fixing it is less.
 Keep the Code Clean − The defects are fixed as they are raised within the same
iteration. This ensures clean code at any milestone of development.
 Lightweight Documentation − Instead of comprehensive test documentation, Agile
testers −
o Use reusable checklists to suggest tests.
o Focus on the essence of the test rather than the incidental details.
o Use lightweight documentation styles/tools.
o Capture test ideas in charters for exploratory testing.
o Leverage documents for multiple purposes.
 Leveraging one test artifact for manual and automated tests − Same test script
artifact can be utilized for manual testing and as an input for automated tests. This
eliminates the requirement of Manual Test Documentation and then an equivalent
Automation Test Script.
 “Done Done,” not just done − In Agile, a feature is said to be done not after
development but after development and testing.
 Test-Last vs. Test Driven − Test Cases are written along with the requirements.
Hence, development can be driven by testing. This approach is called Test Driven
Development (TDD) and Acceptance Test Driven Development (ATDD). This is in
contrast to testing as a last phase in Waterfall Testing.

You might also like