Next Generation Testing Conference, Pune - The faster smarter and reliable lean startup QA

961 views

Published on

Slide Deck for our presentation @ Unicom's India Testing Week - Next Generation Testing Conference, Pune (http://goo.gl/3UXU2E)
Summary:
We are QAs on a lean start-up team. And wanted to share the lessons learned in ensuring quality of the product while being part of a team which was always focused on releasing to production. One of the techniques we use as a lean start-up team is Continuous Deployment. Using CD, we were not only able to deliver usable software to the market faster, but also the foundational principles of CD help us get faster feedback on how reliable our software, in terms of defects, bugs, performance, security. If you carefully look to find out the current need in the software industry, you'll find that there are majorly 2 key elements. One of them being 'How fast can I go-live with my product into the market', i.e. being Faster. And second is 'How perfect is my software? or Can it perform under extreme conditions?' i.e. how reliable is it? This is the topic for our presentation - The faster, smarter and reliable lean start-up QA.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
961
On SlideShare
0
From Embeds
0
Number of Embeds
53
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Next Generation Testing Conference, Pune - The faster smarter and reliable lean startup QA

  1. 1. The faster, smarter and reliable lean startup QA By: Jesal Mistry ThoughtWorks Sandeep Mankar ThoughtWorks
  2. 2. QAs on a lean startup team
  3. 3. to talk about
  4. 4. practices followed
  5. 5. challenges faced
  6. 6. and lessons learnt
  7. 7. in ensuring quality
  8. 8. while eliminating process
  9. 9. and focusing on the product!
  10. 10. agile techniques
  11. 11. on a lean startup team
  12. 12. we had to be disruptive
  13. 13. Agile techniques + Lean approach http://www.clipartsfree.net/vector/large/16540-wedding-sign-vector.png
  14. 14. so,
  15. 15. practices that we followed
  16. 16. minimum viable product (MVP) dset needs a min change!
  17. 17. release when needed is your regression complete?
  18. 18. every commit = production ready Easier said ! then done!!
  19. 19. feature toggles n who, whe & what
  20. 20. automated integration tests f well…most o the times!
  21. 21. prioritize + progress wall using Mingle e do I have tim for this?
  22. 22. acceptance tests using Cucumber
  23. 23. “to automate, or not to automate?”
  24. 24. automated build deployment using Go pipelines maintain?!
  25. 25. automated infrastructure provisioning using Puppet st how do we te these?
  26. 26. local Dev/QA sandbox for testing using Vagrant *conditions apply
  27. 27. invariably helped us achieve
  28. 28. Continuous Deployment (CD)
  29. 29. but hold on…
  30. 30. as always, there were challenges for QA!!!
  31. 31. and, as always, we learnt to…
  32. 32. test early in the cycle
  33. 33. faster feedback to developers and BAs
  34. 34. b’coz faster feedback is crucial specially for a lean startup
  35. 35. calling out complex scenarios in story / feature kick offs
  36. 36. so that YOU don’t have to test everything!
  37. 37. taking calling out risks upfront make mistakes
  38. 38. think how will it work in Production?
  39. 39. test closer to production
  40. 40. and, when in doubt… ask the business!
  41. 41. prioritize your tests
  42. 42. validated automate your user journeys
  43. 43. and use it as a safety net
  44. 44. minimize time taken to test
  45. 45. be flexible about what defects must be fixed
  46. 46. if it is not required tomorrow, let’s not test it right now
  47. 47. don’t forget to test your infrastructure!
  48. 48. identifying and maintaining environments
  49. 49. test your application configurations
  50. 50. and most importantly
  51. 51. test your deployment pipelines!
  52. 52. and there is more…
  53. 53. once your app gets some traction
  54. 54. test with production data
  55. 55. analytics
  56. 56. special environments ~ performance ~
  57. 57. re-focus your tests
  58. 58. and reduce redundant testing
  59. 59. b’cos QAs should help make
  60. 60. faster
  61. 61. smarter
  62. 62. reliable
  63. 63. product releases!
  64. 64. so, where does that bring us?
  65. 65. Need of the Hour x faster time to market smarter QA build reliable software
  66. 66. Thank You! ~&~ Questions? by Jesal Mistry ThoughtWorks jmistry@thoughtworks.com @jesalnmistry Sandeep Mankar ThoughtWorks smankar@thoughtworks.com @smankar8

×