SONALI. PARAB.

SOFTWARE TESTING. - AGILE TESTING.

OVERVIEW:
INTRODUCTION.
AGILE SOFTWARE DEVELOPMENT. AGILE VALUES APPLIED TO SOFTWARE TESTING.

TESTING ON AN AGILE PROJECT.

AVOIDING ERRORS. SOFTWARE DEVELOPMENT METHODOLOGIES IN AGILE. CONCLUSION

INTRODUCTION:
Agile is an evolutionary approach to software development.
Here the software is delivered to the customer very quickly; customer checks it for errors and sends some new changes and requirements to include before the last iteration. Agile development approach believes in the involvement and frequent communication between the developer team and stakeholders.

According to Agile development, people are more important than processes and tools.

AGILE SOFTWARE DEVELOPMENT:

In response to conventional and rigid methodologies, iterative development processes were born which are called as Agile. Agile is a flexible development. approach to

Agile gives preferences to the individuals and the interactions among them over processes and tools.

No huge documentation.
Project is divided into small iterations.

AGILE VALUES APPLIED TO SOFTWARE TESTING:

Value working software over comprehensive documentation.

Value individuals and interactions over processes and tools.

Value customer negotiation. collaboration over contract

Value responding to change over following a plan.

TESTING ON AN AGILE PROJECT:

None of the practices of Agile methodologies are unique, or novel. Various combinations are used.

Automated testing is at the heart of agility.

Comprehensive testing. Refactoring without changing its functionality, to improve simplicity or flexibility. Continuous Integration.

AVOIDING ERRORS
Metaphor Pair Programming 40-hour Week Coding Standard

SPEED AND COMMUNICATION

The Planning Process Small Releases Simple Design

Collective Ownership
On-site Customer

SOFTWARE DEVELOPMENT METHODOLOGIES IN AGILE:

Agile Method

Term
Techniques

Examples

Team creation, Backlog creation Project segmentation Scrum meetings, Burndown charts Review release plans Distribution, review and adjustment of product standards Closure

Scrum

Phases

Values
Activities eXtreme Programming (XP) Practices

Communication, Simplicity, Feedback.

Coding, Testing, Listening, Designing Pair programming, Planning, Test Driven Development, Continuous Integration, Design Improvement, Small Releases, Coding Standards, Simple Design, System Metaphor

Agile Method

Term
Activities

Examples

Develop Overall Model, Build Feature List, Plan By Feature, Design By Feature, Build By Feature, Milestones. Domain Object Modelling Developing by Feature, Individual (Code) Ownership Feature Teams Inspections Regular Builds Visibility of progress and results.

Feature Driven Best practices Development

Principles Crystal Clear Methodology:

Frequent Delivery of Usable Code to Users, Reflective Improvement, Focus, Easy Access to Expert Users, Automated Tests, Configuration Management, Frequent Integration.

Dynamic Systems Development Method

Principles

User involvement, Frequent delivery, Development is iterative and incremental, Changes are reversible, High level scope and requirements should be baselined, Communication.

CONCLUSION
Agile Pulls Testing Forward You need to change your tools and approaches to move it forward You might need to change the model/structure of your team With Agile, you will create faster Release cycles, shorter Iterations, more satisfied customers, and team members that enjoy what they are doing