Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Transcript of Agile Testing
A process used to identify the correctness, completeness, and quality of developed computer software
An investigation conducted to provide stakeholders with information about the quality of the product or service under test.
It's not just audit the software
Developers start coding and testers create test cases upon delivery of requirements by the business
A large chunk of application is deployed
Testing takes several days/weeks
QA Feedback to the team provided and defects are fixed
...and cycle starts over again.
This approach is not setback-free...
* Delays between delivery and feedback
* Little room for collaboration between teams
* Changes in requirements often not communicated resulting in teams having different expectatios
Business facing that supports the team
Automated and Manual testing
Based on requirements
Simulates customer experience
Testing over deliverable prototype
Business facing that critiques the product
Technology facing that supports the team
Integrated within the build process
Technology facing that critiques the product
Testing with specific tools
Tools to measure performance and security
Based on infrastructure
The Agile Tester
Bibliography and Resources
Agile follows a more fluid and continuous process because all parties of an agile team focus together on a small portion of the system and take a new small piece after the current one is completed.
But... how do we know all the different types of tests we need to do? How do we know when we’re “done” testing?
How friendly the application is
Testing with/by business
Several core practices used by agile teams relate to testing, and these go beyond the boundaries of whom we normally refer to as "testers". On an agile team everybody tests, and we test with different approaches to achieve different goals.
Why these tests?
* Go faster, do more
* Value to testers
* Designing for testing
* Timely feedback
An agile tester is a professional tester who
* embraces change,
* collaborates well with both technical and business people,
* understands the concept of using tests to document requirements and drive development,
* knows how to collaborate to automate tests,
* has experience in exploratory testing,
* is able to understand customer's software requirements and is willing to learn what the customers do.
* continually looks for ways the team can do a better job of producing high quality software
There are 10 principles for applying agile values in testing
The Agile Tester
Provide Continuous Feedback
Deliver Value to the Customer
Enable Face-to-face communication
Keep It Simple
Practice Continuous improvement
Respond to Change
Focus on People