Agile testing - Reducing time to Market
Upcoming SlideShare
Loading in...5
×
 

Agile testing - Reducing time to Market

on

  • 1,292 views

Agile Testing - strategies to reduce time to market

Agile Testing - strategies to reduce time to market

Statistics

Views

Total Views
1,292
Views on SlideShare
764
Embed Views
528

Actions

Likes
1
Downloads
12
Comments
0

4 Embeds 528

http://www.techbudha.com 522
http://www.linkedin.com 2
http://feeds.feedburner.com 2
http://prlog.ru 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Traditional testing focus on conformance to requirements <br />
  • Change in market trends <br /> Shorter product cycle <br />

Agile testing - Reducing time to Market Agile testing - Reducing time to Market Presentation Transcript

  • Agile Testing- Reducing the time to market Manoj K G Founder and Director, TeamSuccesso
  • Reference
  • Agile Software Methodologies SCRUM KANBAN
  • Who is an Agile Tester?
  • Delivery Side Business Side Agile Tester Agile Team FOCUS ON QUALITY CUSTOMER NEEDS
  • How does the Agile Tester contribute?
  • Testing in Agile is a whole team responsibility
  • What’s different in Agile? 4 4 1 2 5 6 2 3 5 1 1 7 2 3 3 1 Focus on Incremental Delivery
  • How often do you release?
  • 1 time in every two year to 50 times a day
  • Existing features
  • OK, back to some fundamentals…..
  • Iterative Model- When are you identifying the bugs? Req. capture New feature 1X Cost to Fix 5X New feature Regression-existing function 10X Regression-existing function Beta testing 100X Beta testing
  • From Agile Testing by Lisa and Janet
  • From Agile Testing by Lisa and Janet
  • Unit Tests – Leveraging TDD
  • Unit Tests 1. Written by programmers 2. Part of Definition of Done 3. Reviewed with testers TDD is a SKILL which requires investment from management and team
  • Upper Environment Code quality Unit Test coverage Functional Test coverage Lower Environment Guard your gates during code deployments
  • Blue Green Deployments
  • BUG Driven Unit tests Simulate identified bug by a automated test Write code to make the unit test pass Refactor the covered code
  • From Agile Testing by Lisa and Janet
  • Role of Quadrant 2 tests
  • Guides development by programmers
  • Providing early feedbacks
  • Functional tests 1. 2. 3. 4. Written by testers Inputs for developers Part of Definition of Done Consulted with developers Automation of functional tests are critical for early feedbacks
  • From Agile Testing by Lisa and Janet
  • Role of Quadrant 3 tests
  • 80% of repetitive testing efforts comes from scenarios in Q1 and Q2 In Q3, Unleash the power of human intellect for increasing the value of the product
  • Scenario testing, Exploratory testing, Usability Testing
  • Soap Opera Testing
  • Use Personas
  • From Agile Testing by Lisa and Janet
  • Focus on the nonfunctional requirements that increase the value of Product
  • Functional tests 1. Done by testers/programmers/ Specialists 2. Should be part of user stories
  • Transforming a Legacy application to Agile Testing
  • Refactor your tests
  • Risk Based Testing
  • Automate from RBT
  • Thank you twitter - https://twitter.com/goodoldmanoj Blog - www.techbudha.com LinkedIn - http://www.linkedin.com/pub/manoj-k-g/12/811/495