Your SlideShare is downloading. ×
Quality Assurance in Agile
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Quality Assurance in Agile

482
views

Published on

SQA Days 11. День 1. Стендовая секция …

SQA Days 11. День 1. Стендовая секция
Юрий Малый
AdStream
Киев, Украина

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
482
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Scrum encourages multi-skilled workers, rather than only “working to job title” such as a “ tester” only doing testing. In other words, Team members “go to where the work is” and help out as possible. If there are many testing tasks, then all Team members may help. This does not imply that everyone is a generalist; no doubt some people are especially skilled in testing (and so on) but Team members work together and learn new skills from each other.
  • Scrum encourages multi-skilled workers, rather than only “working to job title” such as a “ tester” only doing testing. In other words, Team members “go to where the work is” and help out as possible. If there are many testing tasks, then all Team members may help. This does not imply that everyone is a generalist; no doubt some people are especially skilled in testing (and so on) but Team members work together and learn new skills from each other.
  • JPBR1 - Joint Product Backlog Refinement 1 JPBR2 - Joint Product Backlog Refinement 2 PBR - Product Backlog Refinement Design Session SP1 - Sprint Planning 1 SP2 - Sprint Planning 2 SPV - DoD validation D - Demo JD - Joint Demo R - Retrospection JLR - Joint Local Retrospection JR - Joint Retrospection PR - Production check
  • Scenario and data examples
  • Continuous integration Ground rules
  • System health monitoring - TeamCity projects
  • System health monitoring Failed builds on plasma at all locations
  • Transcript

    • 1. Quality assurance in Agile Yuriy Malyi. AdStream
    • 2. There are no “ TE S TE RS ” in S crum/A gileO nly te am m e m b e rs with p rim ary s killswh o s h ou ld b e com e “C ros s F u nctional”
    • 3. TE A M Teammem ber
    • 4. TE A M• Te am s ≈ “F e atu re Te am s ”• 1 00% allocate d to one fe atu re (at a tim e )• C ros s -fu nctional• C ros s -com p one nt• Id e ally, co-locate d• S tab le , long-live d (e .g., 3 ye ars toge th e r)• le arn ne w-are a s kills from e ach oth e r• 7 + / 2 p e op le -• E ach te am m ate is re sp onsib l for Q U ALITY ! e
    • 5. S print Time Line
    • 6. Meetings plan
    • 7. Real res ultsNot effective!
    • 8. Keep itS IMPLE !
    • 9. Main ideas• No predefined proces s• E s timates – “ It’s jus t an es timate”• Team is allowed to des cope• Maximize automation• Minimize manual tes ting• Quality proved by tes t coverage
    • 10. A TDD Requirements asE xecutable Tes ts ...
    • 11. E xamples = S pecifications = Requirements = A utomated A cceptanc e Tes ts !
    • 12. Feedback to improve requirements ... Make s ure he is dead h ttp :/ www.you tu b e .com / / watch ?v= Wp s f-E b yBh I
    • 13. Tes ting types• Unit• A TF S cripts• Manual• Regres s ion (A TF)• F2B (For continuous integration projects )
    • 14. DB Bu s ine s s Logic UI U ser Acce p tance A TDDR e gre s s ion Te s ting A TF Te s ting F u nctional QA S e le niu m / Te s ting We b D rive r E as yB, JBe h ave Inte gration B DD Te s ting JU nit Th ird p arty lib s : U nit Te s ting TDD TDD D BU nit M ockito, H am cre s t JU nit
    • 15. S cenarios and data examples Te s t s te p s coincid e with b u s ine s s flow and cove r S TP < ft file = / ataF ile .01 .xls te m p late = / rad e .v4.2.tp l> D T < s ce nario re f= ‘xxx1 .01 > < trad e S te p d e s crip tion= S te p 1 : Inj ct T rad e - Bu y e nam e = "Trad e " ack= Y b og- trad e = Y cas h = N cs d - ins t= N ‘ work= Trad e .U nm atch e d / > < cons S te p d e s crip tion= S te p 2: Inj ct C S V C ons 1 from ‘ e ou tp u tF ile = "file C ons “ inp u tS h e e tN am e = Inp u t -MK T - C ons ‘ colu m ns = "C ons 1 “ cas h = N ‘ cs d - ins t= N ‘ work= ‘Trad e .M atch e d / > U s e r re ad ab le < / ce nario> s Valid ators are re late d inp u t and ou tp u t < /ft> to th e e xte rnal d ata in E xce l s ys te m s re qu e s ts
    • 16. Ground rules• E ns u re wh at you com m it will work• Take re s p ons ib ility for you com m it• D on’t “com m it and ru n”• D on’t m ake th ings wors e• F ix th e b u ild fas t… or e ls e !• Be re s p ons ib le
    • 17. S ys tem health monitoring TeamC ity projects U nit , Inte gration and Be h avioral te s ts are always gre e n – “one h ou r” p olicy in action ATF te s t ne e d s s om e inve s tigation to d e fine re s p ons ib le p e rs ons
    • 18. Failed builds on plas ma at all locations
    • 19. Pres s ure to deliver and engineering quality... The Downfall of A gile Hitler h ttp :/ www.you tu b e .com / / watch ?v= l1 wKO 3rID 9g
    • 20. “ If you are going through hell, keep going.” -- Wins ton C hurchill
    • 21. Q/A ?