Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start 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

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Why you should not have a QA team (RTC, 2013)

Romanian Testing Community Conference, May 2013

Gábor Török

on 5 March 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Why you should not have a QA team (RTC, 2013)

QUALITY ASSURANCE QUALITY ACTIONS 2011/2 2012/1 2012/2 acceptance test framework track bugs level 2 support acceptance tests for all features track all issues rewrite all acceptance tests jenkins whobrokethetests.prezi.com qa writes code exploratory testing tests speed-up engineers ux product team pm qa writes acceptance tests bake quality into processes ownership and responsibility need for automated tests more formal team release assistance avoid interrupting developers faster release raise awareness of quality qa is no role but mindset brave new world devtools why why not 2013/1 how engineering evolved at prezi why kill then learning team framework and processes best practices you can be very agile in a small team reflects to problems in processes transfer knowledge don't outsource know-how full stack quality is important for the team automate your qa use manual resources for exploratory testing WHY YOU SHOULD NOT HAVE A QA TEAM learnings everyone is qa + go to persons code review testing workshops tech lead qa roles release assistance level 2 support issue management test automation jenkins { = + + what is the system that allows no qa run all tests on each code change continuous delivery kanban feature switches devops kanban weekly meetings daily stand-ups engineering friday product team no flaky tests ATDD scaling monitoring, alerts former qa roles 4 20 10 20 6 38 400 40 8 45 1000 70 0 64 1260 190 bootcamp { { jobs.prezi.com gabor.torok@prezi.com preprod
Full transcript