Agile Methodology in SW Testing
Can anyone please help me suggesting some references to know about Agile Methodology in SW Testing.
Re: Agile Methodology in SW Testing
Re: Agile Methodology in SW Testing
a member of QASymphony. www.qasymphony.com
qTrace - Screen Capture Software with Intelligence
qTest - Cloud-based Test Management
These really don't explain how a QA works in a fast paced agile shop works. Some places release on weekly basis with dev-qa ratio of 1-50 or worse. In situation like that QA's role is vastly different. It's a very lengthy discussion but I've been brought in specific environments to address this problem. Good agile organizations where QA has failed to take traction and figure out how to evolve testing.
The main differences are:
- QA relies on extensive requirements and process around developing and tracking them. QA often pushes for things like requirements change management to track evolvement of requirements. In a fast paced agile shops, this process is very streamlined. It's the first agile manifest "Individuals and interactions over processes and tools". This makes traditional QA very difficult
- QA skills often do not line up with agile environment. QA specific tools, such as QTP, is not something developer will want to learn, nor what business wants to invest in. Tooling has to be in sync with dev's so there's a natural transition between unit, system, functional, and even performance testing to accomodate the fast pace.
This is just couple of big ones I can think of. Each organization has their own challenges. The traditional QA market is quickly evolving and shrinking at the same time. Those who are able to identify how to address these challenges will find there are lots of opportunities. For those who do not, they will go into a lesser known entities who are still stuck to waterfall. Many of them claim to do agile but it's only at the task level where they continue to operate at waterfall at mid level management and above where QA is involved in.
Agile as the name refers implies something to do very quickly. Hence Agile Testing refers to validate the client requirements as soon as possible and make it customer friendly. As soon as the build is out, testing is expected to get started and report the bugs quickly if any found. Refer this link http://www.isoftwaretesting.com/2012...ntages-of.html
A quick look into Agile Testing:-
- There will be sprints in this methodology and usually they are of 2-3 weeks.
- At the start of each sprint we will have user stories which are nothing but the business requirement related to specific business component within the application.
- Each sprint can have multiple user stories and there will be QA and Dev resources assign to it.
- Now at the begining of the sprint the developer will start with coding for the fucntionality and QA will focus on the test case development.
- By the mid of the sprint cycle the testing will begin and bugs registered.
- By the end of the sprint cycle regression testing will be done for each functional components.
- Depending on the severeity and priority of the defects, a particular functional component will be marked as UAT ready or go into another Test cycle.
- Depending on the status of the functional component the story will be either marked as complete or moved onto the next sprint.
Agile methods were developed as a response to the issues that the traditional V-Model and waterfall methodologies had with defining requirements and delivering a product that turned out to be not what the end user actually wanted and needed.
Agile methodology has four key features:
1. Stable code,
2. Continuous stakeholder feedback,
3. Cross functional and Self-directed teams,
4. Sustainable pace.