| | | | j | i | i f Maste rfield Nyilvantartasba vétel (FINY} sz4ma: 00595-2008 TRAINING (ERE NIN NS Tananyag Minésitett szoftverteszteld képzési program ISTQB Foundation Level - Agile Tester Extension modul Képzési adatok: Intenzitas: 16 tanéra -2 x 8 x 45 perc Helyszin: 1134 Budapest, Robert Karoly krt. 82-84. Képzési programot készitette: Trinspire Kft. 1134 BUDAPEST, ROBERT KAROLY KRT. 82-84. TEL: (061) 2880178 FAX: (061) 2880177 WWW.MASTERFIELD.HUf Masterfield Oktatokézpont ; Cim: 1134 Budapest, Rébert Kéroly kt, 82-64 Vv Masterfield Telefon: (06 1) 288 0176; Fax: (06 1) 288 0177 Neca en S| E-malt: [email protected] Web: wma. mmasterfotd Felnéttképzési nylivantartési szém: 00595-2008 Intézmény-akkreditéciés lasstromszém: AL-2072 A tanfolyamon a hallgat6k megismerik szoftvertesztelés sajétosségait agilis fejlesztési médszertant kéveté kérnyezetben és felkészitjk dket az ISTQB Foundation Level - Agile Tester Extension vizsgdra” TARTALOMJEGYZEK ISTQB FOUNDATION LEVEL - AGILE TESTER EXTENSION I. Agile Software Development 7 1. The Fundamentals of Agile Software Development 8 2. Aspects of Agile Approaches 14 II. Fundamental Agile Testing Principles, Practices, and Processes 27 1. The Differences between Testing in Traditional and Agile Approaches 28 2. Status of Testing in Agile Projects 35 3. Role and Skills of a Tester in an Agile Team 42 III. Agile Testing Methods, Techniques, and Tools 45 1. Agile Testing Methods 47 2. Assessing Quality Risks and Estimating Test Effort 57 3. Techniques in Agile Projects 64 4. Tools in Agile Projects 83 GYAKORLAT 97 JeGyYZeET Amennyiben tanfolyamunk elnyeri tetszését, lajkoljon minket a Facebook-on, ahol értestilhet aktualis akcidinkrél és részt vehet nyereményjétékainkon! www. facebook. com/MasterfieldTrainingISTQB Foundation Level ~ Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices , Masterfield Nain. G IT COURSES FoR PROFESSHOWALS RBES Wr RBCS com Agile Tester Foundation Adapting and Extending Testing Best Practices Introductions, Objectives, and Overview Masterfield Oktatékézpont - www.masterfield.hu 1ISTQB Foundation Level ~ Agile Tester Extension \ Masterfield The Course € Who is this presenter? © What is this course? ® What are the hours? breaks? ® Must! do exercises? ® Do I have homework? ® Can I get certified? ® May Luse my cell phone or read e-mail during the course? @ Any others??? ore Ale Teer Foun astereld Tang Centre Paves i Mosterfield Y The Materials ® The slides follow the ISTQB Foundation Extension Agile Tester syllabus # The terms come from the latest ISTQB Glossary (see next slide also) ® Two mock exams are included to assess your readiness for the ISTQB Foundation Extension Agile Tester exam ® Each section includes sample exam questions to check your knowledge as you proceed ® Exercises are included for main techniques inumatfeld ia Ale Teer Foun Matertel Tuning Cate Pages Masterfield Oktatkézpont - www.masterfield, hu 2ISTQB Foundation Level ~ Agile Tester Extension J Ceres Terminology © The examinable keywords are from the latest ISTQB Glossary ® However, some terms used are common Agile terms which the ISTQB has not redefined © For these terms, refer to: = guide. Agilealliance.org/ 2 searchsoftwarequality.techtarget.com = whatis.techtargetcom/ glossary = www.scrumalliance.org/ ® Check these sites for unfamiliar agile terms voematrlta ‘Ale Tester Fontin Matec Tring Cone Pages SY “ tersdield ISTQB Agile Foundation Syllabus ® Developed and maintained by a Working Group created by the ISTQB ® Rex Black is the chair of the Working Group and a primary author ®@ Dozens of primary reviewers and multiple review cycles ® Final review and approval by over 40 ISTQB National Boards © Distills over 1,000 person-years of experience ® The ISTQB and the authors are the source of the syllabus which is used by permission as the basis for this course win matreld Ale Teste Foun Mosteril Ting Cer Page Masterfield Oktat6kézpont - www.masterfield.hu 3ISTQB Foundation Level ~ Agile Tester Extension 7 \ Mesterfield The Main Topics Covered 1. Agile Software Development Fundamental Agile Testing Principles, Practices, and Processes 3. Agile Testing Methods, Techniques, and Tools Ale Teer Fontan Masters! Tining Cente Paes? The Exercises ® In many of the exercises, you are working as a tester on the Omninet project ® Omninet is a project to deploy a network of public access Internet kiosks in places like malls, theaters, and other public places © On this realistic project, you will have a chance to apply many of the techniques we discuss sue Ale Tete Foation MasiereléTacing Centre Pee Masterfield Oktatokézpont - www.masterfield, hu 4ISTQB Foundation Level ~ Agile Tester Extension Your Course Objectives © This material is designed to help you work effectively and efficiently as a tester in Agile projects, and to help you obtain ISTOB certification © Please spend the next few minutes writing down what you’d like to get out of the course © Use the following page for your d objectives SF ¥ Don’t let the class end with an objective unfulfilled! sew ase ‘Ale Tester Foundation Mosterls Ting Cane Page oS “Meretield Course Objectives sven hu Age Tester Fortin Masereld Tring Cente Page 10 Masterfield Oktatokézpont - www.masterfield.hu 5ISTQB Foundation Level ~ Agile Tester Extension Aagle Teer Fondation Masereld Tang Cen Page Ale Tater Fondation Masel Trang Cente Page 12 Y “Monertiglg Its Your Course Please join in ? Ask questions ® Make comments © Share experiences ® Second opinions and disagreements welcome PWhy are you here? >What do you want to learn, discuss, and teach? ‘The best sessions have lot ofthis, vm as well as this. K Mostectiel Y What You'll Gain from This Course © Collaborate ina cross-functional agile gp team boing famuliar with principle and basic practices of agile software development © Adapt existing testing experience and knowledge and eusting way of testing to agile Values and principles © Support the agile team in plannin, iesPfelated adbvities "PANS © Apply relevant methods and techniques for testing in an agile piojete © Assist the agile team in test automation activities © Assist business stakeholders in defining understandable and testable user stories, scenarios, requireinents and acceplance criteria as appropriate © Work and share information with other team members using effective communication styles and channels oem Masterfield Oktat6kbzpont - www.masterfield.huISTQB Foundation Level ~ Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 1: Agile Software Development S KMostertild 1, Agile Software Development 1. The Fundamentals of Agile Software Development 2. Aspects of Agile Approaches ovate ‘ale Tester Foedtion Mazerld Tranng Cente Masterfield Oktatékézpont - www.masterfield.hu 7ISTQB Foundation Lev Agile Tester Extension el ~ Chapter 1: Terms © Agile Manifesto ® Agile software development © Incremental development model ® Iterative development model © Software lifecycle @ Test automation © Test basis ® Test-driven development ® Test oracle © User story ‘le Tester Fundtion Maser Tang Core Page 5 Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 1: Agile Software Development Section 1: The Fundamentals of Agile Software Development Masterfield Oktatékézpont - www.masterfield.huISTQB Foundation Level ~ Agile Tester Extension erected Understanding the Syllabus LO and K-levels @ In the Foundation Extension Agile Tester syllabus, you'll see learning objectives and knowledge levels These indicate what you need to know and the depth of knowledge required for the exam © The knowledge levels in the Agile Tester syllabus are’ & KI: remember, recognize, recall = K2: understand, explain, give reasons, compare, classify, summarize 1 K3: apply nemsterfléia Ai Tester Fnndton Masel Tring Cente Page 7 © FA-1.1.1 Recall the basic concept of agile software development based on the Agile Manifesto (K1) ® FA-11.2 Understand the advantages of the whole- team approach (K2) ® FA-1.13 Understand the benefits of early and frequent feedback (K2) neat le Ter Fortin wereld Taig Care Page 18 Masterfield Oktatokézpont - www.masterfield.hu 9ISTQB Foundation Level ~ Agile Tester Extension V( Mostertield Y Agile Testing Has Differences ® Testers on agile projects work differently than on traditional projects © Certain values and principles underpin agile projects © Testers work as part of a whole-team approach ® Testers collaborate with Developers 2 Business representatives 4 Other stakeholders ® Testers provide early and frequent feedback on quality ® Early feedback provides multiple benefits, as we'll see. vo matrfeld Ale Teter Foundation Mastreld Trinny Csi Page 12 S “ Mesterfietd The Agile Manifesto @ Published in 2001 by various software development experts © Values: 8 Individuals and interactions over processes and tools 2 Working software over comprehensive documentation 2 Customer collaboration over contract negotiation 8 Responding to change over following a plan © Note that these are statements of emphasis, not rejection of traditional concepts overt ‘le Tester Fxmétion Masel Tang Care Page 20 Masterfield Oktatékézpont - www.masterfield.hu 10ISTQB Foundation Level - Agile Tester Extension V Mostertiel (Mostetield Agile Principles Satisfy customers via early, continuous, valuable delivery Welcome changing requirements, even late in project Deliver working software frequently Daily whole-team collaboration Build projects around motivated individuals Use face-to-face conversations where possible Working software is the primary measure of progress Promote sustainable development Emphasize technical excellence and good design 10, Emphasize simplicity (amount of work not done) 11. Self-organizing teams maximize quality 12. Become more effective via regular retrospectives NOoRERE ‘ele Teer Fondstion Page 21 Masterfield Oxtatkézpont - www.masterfield.hu celISTQB Foundation Level ~ Agile Tester Extension The Whole-team Approach © Involve everyone with necessary knowledge, skills © Five to nine people (including business stakeholders) ® Ideally collocated ® Daily stand-up meetings © Universal quality responsibility; testers collaborate: With business representatives on acceptance tests & With developers on the testing strategy and test automation © The whole-team approach (power of three): Transfer knowledge within the team = Increase communication and collaboration Avoid unnecessary documentation Leverage everyone's skills win masterly Ale Teer Foettion Mastrls Tring Core Powe + “* Mosterfiald Example: Whole-team Approach ® On one project following a sequential lifecycle, marketing staff wrote requirements document and passed it to development and test ® We found dozens of problems in this document ® Marketing staff did not answer most of our questions ® These problems lead to: 8 Bugs and gaps in test cases 8 High rate of false positives # Developers interpreting requirements differently than test and marketing did © The whole-team approach could have avoided these problems numa Ale Teer Foun Mastreld Ting Centre Page 24 Masterfield Oktatékézpont - www.masterfield, hu 12ISTQB Foundation Level Agile Tester Extension ™ (Mes Early and Frequent Feedback ® Short iterations lead to frequent feedback on quality from testers and customers Customer feedback focuses attention on business value and risk © Benefits: = Reduced requirements misunderstandings 8 Early and ongoing clarification of customer needs = Early discovery and resolution of bugs = Understanding of velocity and quality capability © Agile projects can enjoy steady progress sovnemaserfl Atle Teter Fulton MaserfldTranng Cee Page 2 Kester Ex: Agile Lifecycle and Quality Feedback : ee oe J nec eer Mer tute] ne Tar lee inet een ~ lane Spratt su matereld a le eter Fundtion Msterils Trang Coe Masterfield Oktatdkézpont - www.masterfield.hu 13ISTQB Foundation Lev Agile Tester Extension el — Sample Exam Question @ Let's check your knowledge ® The instructor will select a sample exam question from the noteset Solve the question © The instructor will lead a discussion on the right (and wrong) answers, if needed seas he ‘Ale Tester Foundation Mastered Trang Core Page 27 Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 1: Agile Software Development Section 2: Aspects of Agile Approaches Masterfield Oktatékézpont - www.masterfield, huISTQB Foundation Level ~ Agile Tester Extension Chapter 1, Section 2: Learning Objectives © FA-1.2.1 Recalll Agile software development approaches (KI) © FA-1.2.2 Write user stories in collaboration with development, business representatives, and product owners (K3) © FA-12.3 Understand how retrospectives can be used as a mechanism for process improvement in Agile projects (2) © FA-1.24 Understand the use and purpose of continuous integration (K2) © FA-1.2.5 Know the differences between iteration and release planning, and how a tester adds value in each of these activities (K1) vo maefl e ‘ale Tener Foedation Maserld Tang Cee Page 29 S “ Mostestield ( Mestediels Agile Approaches ® Agile methods are not unified; there is diversity ® Each method implements the Agile Manifesto differently ® In this course, we consider Extreme Programming, Scrum, and Kanban as popular, representative methods ® There are common practices across these methods, which we'll examine ‘Agile Tester Fourdabon Mastrfield Teaming Centre Page 30 Masterfleld Oktatékézpont ~ www.masterfield. hu 15ISTQB Foundation Level ~ Agile Tester Extension 7 Keene Extreme Programming ® Values: communication, simplicity, feedback, courage, respect © Principles: humanity, economics, mutual benefit, self- similarity, improvement, diversity, reflection, flow, opportunity, redundancy, failure, quality, baby steps, accepted responsibility @ Primary practices: sit together, whole team, informative workspace, energized work, pair programming, stories, weekly cycle, quarterly cycle, slack, ten-minute build, continuous integration, test first programming, incremental design © Many other agile practices use some aspects of XP Ale Tener Foto Mastrele Tang Centre Page 3 \ Mesterfiele Scrum ® Practices ® Roles 8 Serum Master ensures practices and & Sprints rules are implemented followed 8 Product Increment s Product Owner represents the «2 Product Backlo customer and owns product uct Backlog alc P 2 Sprint Backlog # Development Team (3-9, self 8 Definition of Done organized) develops and tests @ Timeboxiny product : . © Scrum does not prescribe testing 8 Transparency approach, © No specific software development techniques ennai Ale Ter onkon Maser Tan Cone ae? Masterfield Oktatékézpont - www.masterfield, hu 16ISTQB Foundation Level ~ Agile Tester Extension Sy eect vou mastertld Masereld Tang Cente Kanban © Optimize flow of work in value-added chain © Instruments: = Kanban board Work-in-progress limit 8 Lead time ® Both Kanban and Scrum provide status transparency and backlogs, but: Iteration is optional in Kanban # Items can be delivered one at a time or in a release s Timeboxing is optional sooumasterfelé Age Teter Foumition Martell Tring Cente Paget Masterfield Oktatékozpont - www.masterfield.hu 7ISTQB Foundation Level - Agile Tester Extension vX% Collaborative User Story Creation ® Developers, testers, and business stakeholders collaborate to capture requirements in user stories © User stories include: 8 Functional and non-functional elements Acceptance criteria for each element © Testers bring a unique perspective to this process Identify missing elements Ask open-ended questions Suggest tests for the user story & Confirm the acceptance criteria ® Acceptance criteria clarify the feature and establish clear completion measures ermal Ale Teer Fouation Maserlé Ting Core Page 35 YS “Mestertigla Creating User Stories @ INVEST technique ® 3C elements: Independent 8 Card: physical 2 Negotiable description of story e valetie and its benefits Pease = Conversation: how the software will be used Sized appropriately ecu aaaee & Testable checking of the Collaborators can also acceptance criteria brainstorm and mind (positive and negative) map 'y various participants © User story docs; concise, sufficient, necessary vocal ie Ale Teter Fundton Mastereld Taig Cente Page Masterfield Oktatdkézpont - www.masterfield. hu 18ISTQB Foundation Level - Agile Tester Extension + “Morte Example: User Story ® Story: Find Reviews Near Address ® Asa typical user I want to see unbiased reviews of a restaurant near an address so that I can decide where to go for dinner ® Pattern: As a I want to so that mast AaleTester Fountion Masel Trang Cone Pago? Example: User Story ® Story: Closing Auction Protection © Description: MOC Agent @ Make a configurable time & At this time, cancel the open limit order intended for the closing auction if it's too passive (make everything configurable) « If both MPV Offset and Cent Offset are enabled, the more passive of the two threshold prices is selected + Fora Buy order, this is the lower of the two + For a Sell order, this is the higher of the two # Note: some details omitted; this story fills one page ale Teer Foundation ard ng Cee Page 38 Masterfield Oktatékézpont - www.masterfield.hu 19ISTQB Foundation Level ~ Agile Tester Extension V{ Mesterfigld YY» Example: Acceptance Criteria ® Assume you are testing a browser-based application © Working with the product owner, you might define the following acceptance criteria 8 All screens display correctly on current and previous versions of Internet Explorer, Firefox, Safari, and Chrome # At 100% magnification, no horizontal scrolling is required to view any part of any screen Page 39 Retrospectives © Meet at the end of each iteration 3 What worked and what didn’t work so well 18 How to improve and how to retain success ® Topics: process, people, organizations, relationships, tools © Follow through is required © Essential to self-organization and continual improvement @ Address: test effectiveness/ efficiency, test case quality, team satisfaction, and testability issues vray Ale Tester Foun Mastered Tig Centre Page 0 Masterfield Oktatékézpont - www.masterfield.hu 20ISTQB Foundation Level - Agile Tester Extension / “Mestertield ( Mestertigld What, Who, When, Where, How © Use data (e.g., root cause analysis of defects) to pick improvements in retrospectives ® Pick a small number of improvements per iteration ® Fit the retrospective process into the lifecycle © Have a facilitator organize the meeting with the whole team and business representatives ® Involve testers and examine test activities ® Keep it professional and maintain mutual trust ® Adhere to the usual attributes of a successful review oma ‘ale Ter Fastin Naserild Tang Cone age Mes EE Example: Retrospective Drives Improvement Tester describes a high rate of confirmation test failure during a sprint ® Tester shows bug tracking results demonstrating around 25% of bug fixes failed confirmation test @ Team decides to have developers work more closely with testers to upgrade unit tests © By investing a few minutes with developers on each bug fix, the team benefits: 8 Saves hours of wasted time on each sprint # Reduces schedule risk for features age 42 Masterfield Oktatokézpont - www.masterfield.hu 21ISTQB Foundation Level - Agile Tester Extension ~ “versie KM Continuous Integration © Merge changes and integrate all code daily (or more often) for quick discovery of defects © Developers code, debug, and check-in © Continuous integration automatically performs: 8 Static code analysis = Compilation = Unit testing (functional/ non-functional) Deployment 1 Integration testing (functional/ non-functional) = Reporting © Automated continuous integration, regression testing, and feedback © Manual testing of new features, changes, and defect fixes ® Some defects are put in the product backlog wanna Ale Tester Founation Mastrels Tring Care Page / CWenesiatg Benefits of and Risks of Continuous Integration © Benefits © Risks: & Early defect detection 8 The introduction and 2 Feedback on quality ongoing use of CI tools @ Daily test releases a fos : & Lower regression risk # The CI process may not adi -am = Confidence and visibility ears 8 Test automation costs too much or takes too long, & Insufficient skills to into progress w No big-bang intogration ee create good tests bil: Over-reliance on unit 2 Less repetitive testing & Over ae 3 Quick feedback on co ; Processimprovemenss © CI process requires Masterfield Oktatokézpont - www.masterfield. hu 22ISTQB Foundation Level ~ Agile Tester Extension Example: Continuous Integration @ Programmers code, test units in their local test area, then check in @ Each check-in triggers. is astatic test,a build, =f» and a white-box test ‘© We did this \! Mostertiel ees Ale Tester Foon Ale Tester Fodtion in six weeks @ Partly with open-source tools | ‘See “Mission Made Possible,” | ‘woww.rbes-us.com, 1 thank my eo colleague and coauthor on this | anticle, Greg Kubsezkowski vwewnasetaldha Maverld Trang Cente S “eenesiata Release Planning (High Level) © Planning is an on-going activity © For agile lifecycles: release and iteration planning © Release planning, Define product backlog (user stores for release) 2 Refine user epics 2 Basis of test approach and test plan for release & Identify project/quality risks, estimate effort © Testers: Define testable user stories Participate in project and quality risk analy'ses Estimate test effort = Plan testing for release @ Release plans may change during project due to internal and external factors © Testers must handle changes, see larger context of release, and obtain an adequate test basis and test oracles, Mr Tn Cee Paes Masterfield Oktatokézpont - www.masterfield.hu 23ISTQB Foundation Level - Agile Tester Extension ® Clarify user story with product owner = Assign tasks to the team : @ Iteration plans 2 sometimes change vnunet Now Size ocean Matereld Trang Cate Page 8 Masterfield Oktatékézpont - www.masterfield, hu 24 Iteration Planning (Low Level) © Iteration planning ® Testers = Define sprint backlog s Participate in risk 8 Update test plan analysis Select and elaborate user Determine testability stories Create acceptance tests & Analyze risks for user 4 Create tasks for user Stories stories t Estimate each user story, ss Estimate test effort reconcile with eam Define test levele velocity Identify functional and Ale Tester Fundton Mastered Tring Cente Page #7 Product Backlog Grooming oe. \( Metterfield non-functional test areas Work on test automation Communicate with team Accommodate changes MesterfieldISTQB Foundation Level ~ Agile Tester Extension Sample Exam Question ®Let’s check your knowledge © The instructor will select a sample exam question from the noteset © Solve the question © The instructor will lead a discussion on the right (and wrong) answers, if needed vnunet Ale Teter Fotion Masereld Trang Cente Page Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 1: Agile Software Development Section 2: Exercise Masterfield Oktatékézpont ~ www.masterfield.hu 25ISTQB Foundation Level ~ Agile Tester Extension \ Mestertield Exercise: User Story and Acceptance Criteria © Read the entire Omninet Marketing Requirements Document (also used in subsequent exercises) ® In groups of three, evaluate section 3.1.2 ® Assume that you are working to define a user story for this section 2 Define user stories 8 Define acceptance criteria for the payment processing feature = Note any testability issues that exist with this section vost ie ‘aie Teter Fondation Marereld Tring Cente Page Debrief: Acceptance Criteria © Some possible user stories t8 Processing payment (cash) t Processing payment (card) 8 Purchasing extra time ® Acceptance criteria should cover 4 Processing payment for each supported credit card, debit card, and allowed cash denomination’ ss Rejecting cards that are not allowed a Rejecting cash that is outside region or denomination © Testability issues include: No screen prototypes, so Ul can’t be evaluated 1 Difficulty in testing localization issues associated with accepting cash in foreign locations a No definition of accepted cash denominations No details on cash change handling if a user is terminated and must receive a partial refund ovate Abe Tee Founstion Masel Tsing Cente rage Masterfield Oktat6kézpont - www.masterfield.hu 26ISTQB Foundation Level ~ Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 2: Fundamental Agile Testing Principles, Practices, and Processes .. \asterfield \ Mesterteld 2. Fundamental Agile Testing Principles, Practices, and Processes 1, The Differences between Testing in Traditional and Agile Approaches Status of Testing in Agile Projects 3. Role and Skills of a Tester in an Agile Team Ate Tester Foundation Masel Trang Cowre Page St Masterfield Oktatokézpont - www.masterfield.hu 27ISTQB Foundation Level ~ Agile Tester Extension fa S \ Mes terfield Chapter 2: Terms ® Build verification test Configuration item. © Configuration management “ng Cente Page 5 Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 2: Fundamental Agile Testing Principles, Practices, and Processes Section 1: The Differences between Testing in Traditional and Agile Approaches Masterfield Oktat6kozpont - www.masterfield.hu 28ISTQB Foundation Level ~ Agile Tester Extension Chapter 2, Section 1: Learning Objectives © FA-2.1.1 Describe the differences between testing activities in agile projects and non-agile projects (K2) © FA-2.1.2 Describe how coding and testing activities are integrated in agile projects (K2) © FA-2.1.3 Describe the role of independent testing in agile projects (K2) svat he Ale Tester Feandion MasereldTinng Cente age st Vive la Difference! ® Test activities and work products follow from development activities and work products © So, testing must adapt to the lifecycle © Agile testing differences: 1 Tight integration of testing and development activities 8 Lightweight work products # Names, entry criteria, and exit criteria for test levels, 1» Testing tools # Placement of independent testing © Different organizations implement agile lifecycles differently (often for good reasons) ‘ale Tester Foundation erlang Coe Page 8 Masterfield Oktatokézpont - www.masterfield.hu 29ISTQB Foundation Level ~ Agile Tester Extension Agile © Short iterations deliver valuable, working features © Release and iteration planning and quality risk analysis @ User stories selected in each iteration © Continuous test execution, overlapping test levels © Testers, developers, and business stakeholders test Agile Tester Foun Mastered Agile © Hardening iterations may ‘occur periodically Avoid accumulating technical debt Pairing (atleast in XP) Testing and quality coaching is a best practice Heavy use of test automation for regression risk Change may occur during project —deal with it Lightweight work products Ale Teer Fouaition Mates Masterfield Oktat6kézpont - www.masterfield.hu Comparing Agile and Sequential 1 evel \ Mosterfigle Y Sequential ® Longer timeframes, deliver large groups of features Overall planning and risk analysis up front, with control throughout Scope of requirements established up front Test execution in sequential levels in last half of project Testers, developers, and business stakeholders test ° ° e Tate Cone Page 9 Comparing Agile and Sequential 2 Sequential © Hardening happens at end of lifecycle, in system test/SIT Unrecognized technical debt is a major risk Pairing is unusual Testing and quality coaching is a best practice Test automation is a best practice Unmanaged change can result inadeath march © Risk of over-documentation ° ° ° ° ow mastfelé ia Training Cente Page 6 30ISTQB Foundation Level ~ Agile Tester Extension S “ mestertiels Example: Differences, Agile and Sequential ea Taare 8d + [nsec are a_i erm wow mater Ale Tester Fownatin Matrle Taming Core age ot Work Products © Types of work products 8 Business-oriented; e.g, requirements, user docs, user stories, epics, acceptance criteria = Development; ¢.g,, database diagrams, code, automated unit tests, test-driven development 1 Test; eg,, test strategies, test logs and results, quality risk catalogs, automated and manual tests, defect reports @ Agile projects minimize documentation, emphasize working software and automated tests © Sufficient documentation must be provided for business, testing, development, and maintenance activities © In regulated, safety critical, distributed, or highly complex projects, more documentation is often required worm ‘Ale Tester Founatoe erlang Core Masterfield Oktatékézpont - www.masterfield.hu 31ISTQB Foundation Level - Agile Tester Extension Contrasting Test Levels ® Test levels: logically related test activities appropriate to test item maturity or completeness of the item with clear ownership © Sequential: exit criteria of one level part of entry criteria for next level ® Iterative (e.g., RUP): test levels may overlap to some extent (including with development) © Agile: considerable overlap of test levels and development (parallel test and development) ® Changes to user stories can cause looping vont Able Teer Feudtion Masel Tang Cee Page Mi Masterfield ( Mesterfield Y Agile Test Levels © Unit testing (developer, often automated) © Feature acceptance testing tt Feature verification (developer or tester, often automated, bbased on acceptance criteria & Feature validation (developers, esters, an business stakeholders, usually mantal, shows usefulness, progress) Unit integration testing (dev+test, sometimes not done) System testing (tester, functional and non-functional) System integration testing (tester, sometimes one iteration behind) @ Acceptance testing (alpha, beta, UAT, OAT, regulatory, and contractual, at end of each iteration, after each iteration, of after a series of iterations) © Regression testing throughout the iteration (via automated unit tests and feature verification tests) eee vn matfelé in Ale Tester Foundation Married Tring Cente Page Masterfield Oktatékézpont - www.masterfield. hu 32ISTQB Foundation Level - Agile Tester Extension Ex: Agile Testing for System-of- Systems © System testing of each iteration ® System integration testing by separate team ® Stabilization sprint at the end to fix bugs OAT and UAT before release to production 7, / Mosterfield \ Mesterfield Tools: Test and Configuration Management ® Agile relies on automation for development, testing, and configuration management 2 Developers: Static analysis and unit testing & Testers: Functional tests at the integration and system levels ® Automated tests, at all levels, in build/ test frameworks, achieving continuous integration ® Real-time, efficient detection of build, regression defects ® Regression risk higher due to extent of change across iterations and code refactoring during each iteration © Unit tests must be complemented by integration and system tests to adequately address regression risk graf Acie Teter Foundation ewtrfeld Tang Cae Page Masterfield Oktatokézpont ~ www.masterfield, hu 33ISTQB Foundation Level - Agile Tester Extension ° Masterfield Oktat6kézpont - www.masterfield.hu Ate Teste Foudtion Exam Ale Teer Foon ‘Mosterfiel ~ “Merterfisla Independent Testing? In Agile? Yes! A single tester embedded in the development team risks loss of independence and objective evaluation Fully independent, separate test teams which assign testers at end of iteration & Preserves independence ancl objectivity = Time pressures, limited familiarity, lack of relationships are a problem Midale ground: independent, separate test team, with testers assigned to teams ona long-term basis Preserves independence and objectivity © Familiar with features, whole-team relationship, available for whole iteration Manage organizational risks Keep the appropriate tester mindset 4 Don't tolerate inefficient, ineffective, or low-quality practices 18 Keep pace with change within time-box constraints wens Masterelé Training Cet Page 6? /e: Independent Testing and Agile ed ae al 34ISTQB Foundation Level - Agile Tester Extension ls x starfigld Sample Exam Question @ Let’s check your knowledge ® The instructor will select a sample exam question from the noteset Solve the question ® The instructor will lead a discussion on the right (and wrong) answers, if needed ws ane Ail Tester Font Mostrile Trang Cen Page 9 Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 2: Fundamental Agile Testing Principles, Practices, and Processes Section 2: Status of Testing in Agile Projects Masterfield Oktatékézpont - www.masterfield.hu 35ISTQB Foundation Lev Agile Tester Extension al — Viento Chapter 2, Section 2: Learning Objectives @ FA-2.2.1 Describe the basic set of work products used tocommunicate the status of testing in an Agile project, including test progress and product quality (RQ) © FA.2.2.2 Describe the process of evolving tests across multiple iterations and explain why test automation is important to manage regression risk in Agile projects (K2) marti Ale Teter Foenion Maereld Training Centre Pagel Status of Testing © Inagile project, change happens, rapidly and often © When the features change, so does product quality © Change can make a mess of your status reporting processes if you're not careful © Change also means that "It is not the strongest accurate test status is critical species that survive, nor the ae most intelligent, it isthe one mnge can : retroactive impact on most adaptable to change features from previous Charles Darwin iterations '® So, change often means existing. ists must change swvemastrflé he Al Teter Foundation Materdld Traine Cente Powe Masterfield Oktatdkézpont - www.masterfield. hu 36ISTQB Foundation Level - Agile Tester Extension Communicating Test Results ® Test progress can be recorded using automated test results, agile task boards, and burndown charts © Test status can be communicated via wikis, standard test management tools, and during stand-ups © Project, product, and process metrics can be gathered (c.g., customer satisfaction, test pass/fail, defects found fixed, test basis coverage, etc.) = Metrics should be relevant and helpful # Metrics should never be misused Automating the gathering and reporting of status and metrics allows testers to focus on testing svat Ale Teer Foun Maserfld Tring Cate Page 73 Iteration Burndown Charts sete tom “0 ‘le Tener Fodtion Masereld Tang Coe age 74 Masterfield Oktatékézpont - www. masterfield.hu 37ISTQB Foundation Level ~ Agile Tester Extension Masterfield Oktatékézpont www.masterfield. hu eng YY Daily Stand-up Meetings ® Inagile task boards, tasks move into columns (to do, work in progress, verify, and done) © Done means all tests for the task pass ® Task board status reviewed during stand-ups, which include testers and developers (whole team) © Each attendee should address: & What have you completed since the last meeting? What do you plan to complete by the next meeting? & Whats getting in your way? Team discusses any blockages or delays for any task, and works collaboratively’ to resolve them vom Able ester Fosndton Maserld Tang Coe Page 6 38ISTQB Foundation Level - Agile Tester Extension MI terfiel Y Cuero Example: Task Board ToDe JWor sn Fare] Verify | Done us. —ES-E] Reieaze Backlog toe eration Backlog Tet Results eld ha Ale Tester Fodatn, ng Cone Page 77 raining Cente Masterfield Oktat6kézpont - www.masterfield.hu 30ISTQB Foundation Lev Agile Tester Extension el - Evoling Tests Over Time ® Allow time to review tests, select regression tests, retire irrelevant tests, update tests, and automate + Each iteration grows the product and the scope of testing 2 Each iteration involves testing new and changed code, along with regression testing existing features Existing features can change, s0 tests must change ® Test data, test environments, etc, must also evolve © Configuration management of test assets and results is imporiant due to volume of tests, rate of change ® Good test design and implementation enable quick impact analysis and updates, so consider this during release planning © Incremental test case writing (thin slices, small chunks) ema Ale Tester Function Maserld Trang Care Pay 9 / tenet Automating for Regression Risk and More © Automated tests at all levels reduce technical debt and provide rapid feedback © Run automated regression tests in continuous integration and before putting a new build in test = Automated unit tests provide feedback on code and build quality (but not on product quality) 8 Automated acceptance tests provide feedback on product quality with respect to regression ® Fix regression and build bugs immediately (Keep the tests passing) © For efficiency, also automate test data generation and loading, build deployment, environment management, output comparison oer maseti Ale Tete Fonda Msterld Tring Centr Page Masterfield Oktatdkézpont - www.masterfield, hu 40ISTQB Foundation Level ~ Agile Tester Extension “Mererisla Example: Updating Acceptance Criteria @ Again, assume you are testing a browser-based application © Suppose support for Opera, iPads, and Windows tablets are added ® Update the following acceptance criteria # All screens display correctly on current and previous versions of Internet Explorer Gncluding tablets), Firefox, Safari (including iPads), Chrome, and Opera = At 100% magnification, no horizontal scrolling is required to view any part of any screen, except on iPads and tablets ® These changes require test case and environment updates, too ld Trang Conve Page 81 YS “ Mestaild Sample Exam Question ® Let's check your knowledge The instructor will select a sample exam question from the noteset Solve the question ® The instructor will lead a discussion on the right (and wrong) answers, if needed vo meterfel Ale Teer Foun Masterld Tang Cense Paget Masterfleld Oktatékézpont - www. masterfield. hu atISTQB Foundation Level - Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 2: Fundamental Agile Testing Principles, Practices, and Processes Section 3: Role and Skills of a Tester in an Agile Team /) /\K ester (Mesterfels Chapter 2, Section 3: Learning Objectives ® FA-23.1 Understand the skills (people, domain, and testing) of a tester in an Agile team (K2) @ FA-23.2 Understand the role of a tester within an Agile team (K2) omar Al Tester Fandton Maser Trang Cente Pay Masterfield Oktatékézpont - www.masterfield. hu 42ISTQB Foundation Level - Agile Tester Extension Agile Tester Skills Implications ® Collaboration, communication, and interaction! ® Beyond skills in the Foundation, you should: = Build technical proficiency 1 Solve problems while still looking for problems = Work actively with the whole team and stakeholders Know and share test results, test progress, product quality, and process quality & Collaborate for testability Respond quickly and efficiently to change ‘8 Flexibly and continuously plan Always be learning. © Quality and testing are whole-team roles, but the agile tester is the quality and testing expert oma Ale Tester Fosiation Masel Taig Cre Page 85 S “Mester Example: Tester Skills ® Many job descriptions for testers in agile organizations include white-box testing and programming skills © Quality cops need not apply; quality partners are welcome ® Process cops need not apply partners are welcome process ‘Ale Teter Fondaon Mastreld Tsing Cone Pag Masterfleld Oktatékézpont www.masterfield.hu 43ISTQB Foundation Level ~ Agile Tester Extension Agile Tester Role # Understand, implement, update test strategy Measure, report multidimensional test coverage © Use test tools ® Configure, use, manage test environments, data ® Report and help resolve bugs @ Actas. test and quality coach © Release and iteration planning © Collaborate on requirements © Participate in retrospectives Ale Teter Fodtion MarerldTating Centre Pave 87 ~% E. Sd Varying Tester Roles ae ee JS vmware Air Faadaton Masel Trans Cate Page 8 Masterfleld Oktatékézpont - www masterfield.hu 44ISTQB Foundation Level - Agile Tester Extension \{ Mesterfigld Sample Excam Question © Let’s check your knowledge ® The instructor will select a sample exam question from the noteset © Solve the question © The instructor will lead a discussion on the right (and wrong) answers, if needed evel Ale Tester Foundation aserlé Tsing Core age Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Pe gle Testing Methods, Techniques, and Tools Masterfield Oktatékézpont - www.masterfield.hu 45ISTQB Foundation Level ~ Agile Tester Extension S “ mostetiels 3. Agile Testing Methods, Techniques, and Tools 1. Agile Testing Methods 2. Assessing Quality Risks and Estimating Test Effort 3. Techniques in Agile Projects 4. Tools in Agile Projects vo muted Ale eter Fodon tl ay Cnr raed S Kmest Chapter 3: Terms © Acceptance criteria Test approach © Defect taxonomy @ Test charter * Exploratory testing —_ @ Test estimation ® Maintainability © Test execution testing automation ® Performance testing © Test strategy ® Product risk ® Test-driven © Quality risk development @ Regression testing © Unit test framework ® Security testing © Usability testing Al Tee Fondaicn ater a Gone Peet Masterfield Oktat6kézpont - www.masterfield, hu 46ISTQB Foundation Level ~ Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Agile Testing Methods, Techniques, and Tools Section 1: Agile Testing Methods S “riontertite Chapter 3, Section 1: Learning Objectives @ FA-3.1.1 Recall the concepts of test-driven development, acceptance test-driven development, and behavior-driven development (K1) © FA-3.1.2 Recall the concepts of the test pyramid (K1) @ FA-3.13 Summarize the testing quadrants and their relationships with testing levels and testing types (K2) © FA.3.14 Fora given agile project, practice the role of a tester in a Scrum team (K3) Ae Tent Fodaicn Maserld Tang Cone Page 4 Masterfield Oktatokozpont - www.masterfield.hu 47ISTQB Foundation Level - Agile Tester Extension \ Mesterfield Agile Testing Methods © Agile projects utilize many testing methods 2 Early test design 2 Farly defect prevention, detection, and removal = Right test types at right time and test level ® As an agile tester, you will use these methods © These methods align with the Foundation syllabus methods vo masta Ale Tester Foun Materelé Tring Cone Pages (Mosterfield Test-driven Development ® A development technique (test-first) & Add test for small piece of code Run the test (which should fail) 8 Write code until test passes 8 Refactor code 2 Repeat process (previous tests and added tests) ® Used in agile and sequential lifecycles @ Fix code bugs on introduction © TDD provides executable design specifications, as automated tests, in continuous integration ema ia Ale Tester Foundation Martell Tring Cae Page 95 Masterfield Oktatékézpont - www.masterfield.hu 48ISTQB Foundation Level ~ Agile Tester Extension Ale Teter Foundation Masel Tang Cone Page 97 \ Acceptance Test-driven Development osterfigld ® Define acceptance criteria and tests early in development © Collaborate so every stakeholder understands behavior © Process {Define tests for tended behavior Create automated acceptance ess 4 Program intended behavior x Run automated acceptance tests © Create reusable regression lests for continuous integration © Test data and service layers © Test system/acceptance level in appropriate environments 1 entity /quickly resolve defects Verity feature behavice 2 Meabure acceptance criteria 4 Deliver to extemal testing teams S “riestertield Behavior-driven Development © Behavior-driven development is black-box approach © Focus on expected behavior: Developer creates a test for the class under development Tests should make sense to stakeholders (including testers) « Clarify where defect lies (code, user story, oF test) ® Behavior-driven development defines tests: & Given some context 8 When some event occurs «2 Ensure some outcomes are taken by system ® Helps to define test cases for developer based on tester/stakeholder collaboration sonar ‘Ale Teter Foetion Materld Tang Centre Page 98 Masterfield Oktat6kézpont - www.masterfield.hu 41STQB Foundation Level ~ Agile Tester Extension Masterfield Oktat6kézpont - www.masterfield.hu © Test pyramid concept Ale Teter Foun ® Any test shown in Ale Teer Foettion Test Pyramid © Test pyramid emphasizes lower- level tests over upper-level tests _/ ~ is early QA and testing principle in action © Automate unit and integration es tests through API ae ® Automate system and 7 acceptance tests through / system GUI J insertion \ unit associate test levels, types, goals, and focus # Covers important dynamic types/levels Masterls Trang Cente Business oriented +S “ Mestertig! Test Quadrants, Levels, and Types @ The test quadrants ld Mixed System level functionality test ace. criteria, can be included in ‘Manual Systom/UAT level: reactive tests, scenarios, usability # Differentiates, describes types any quadrant can Support the team (verify) occur in each iteration regesion Unit level: Saez tunit/'component tests in continuous ‘integration ‘process Automated OAT level reliability, pee. data mig, security, ‘maintainability, comp, interop, es; Automated Tools ‘@iepitea) npord sip arenjeaq Technology oriented vem 50 Mastrele Tring Cee Page 100ISTQB Foundation Level - Agile Tester Extension Y Example: Test Quadrants in Action © One client follows a four-week scrum-based iterative lifecycle # Ql tests are developed and executed concurrent with development, continue during stabilization & QZ tests are developed during planning and development, executed during development and stabilization © QB tests are developed (if written) and executed during, development and stabilization. 5 Of tests are developed and run periodically, on an as- needed basis : = © They allow changes to the sprint backlog during the sprint Production bugs & Urgent client feature requests vor mae Ale Teer Foation Materld Tang Centre Page 101 K Mesterfield Example: Test Quadrants in Action ~\ omer at vv ntl Agile Teer Fost Masereld Tring Cente Page 12 Masterfield Oktatékézpont - www.masterfield.hu 51ISTQB Foundation Level ~ Agile Tester Extension \ Masterfigle The Tester’s Role in Scrum: Teamnork ® Teamwork is fundamental to agile: = Cross-functional = Self-organizing Collocated # Collaborative = Empowered = Committed = Transparent ® Credible = Open to feedback & Resilient @ Teamwork maximizes likelihood of successful testing Al ester Fumtion Maserld Trang Cente Page 10 Catal The Tester’s Role in Scrum: Iteration Zero © First iteration: 2 Identify scope 1 Divide user stories into sprints Create system architecture Plan, acquire, and install tools Create initial test strategy for all test levels Perform initial quality risk analysis Define test metrics Specify the definition of “done” 8 Create the task board & Define exit criteria ® Sets the direction for testing throughout sprints vented Ale ester Fundtion Masel Trang Cente Page 104 Masterfield Oktatékézpont ~ www.masterfield, hu 52ISTQB Foundation Level ~ Agile Tester Extension (Mestertiald The Tester’s Role in Scrum: Integration ® Continuously deliver customer value: @ Ineach sprint # At the end of the project © Continuous testing requires identifying all dependencies between functions and features = Feature integration strategy is helpful for this process = All supporting functions for a feature developed. separately numa Ale Teste Fotion Masel Trang este Pay 15 Mi Mosterfield Ee The Tester’s Role in Scrum: Planning @ What: test scope, extent of testing, test and sprint goals @ Why: explain what's in and out of scope @ Who: assign testing of features and characteristics © Where; which test environment and what changes, data, tools, and configurations are needed for it (think ahead) @ When: start date and frequency for test tasks @ How: which test methods, techniques, tools, and data © Prerequisites: predecessor tasks, expertise, training, © Dependencies: functions, code, system components, vendor, technology, tools, activities, tasks, teams, test types, test levels, and constraints © Project and quality risks: as described in Foundation and later © Priority: consider customer/ user importance, risks, dependencies © Time: duration and effort required to test, as described later © Sprint planning populates task board with tasks (1-2 days) oe mastefla Ail Tester Founton Msterild Tang Core Page 105 Masterfield Oktat6kézpont - www.masterfield.hu 93ISTQB Foundation Level - Agile Tester Extension © As project details become clearer, apply rolling wave planning # Sprint: task details for current sprint Release: create a test plan (during iteration zero) for all test activities and levels 1 Specific problems: what solutions are needed to do testing work in plan Long-term test goals: look a year or more into future strategic testing goals: how to support testing future products * Rolling four-week detailed test planning helps avoid surprises Ale Teter Foettion Nawerelé Tsing Ceo Powe wr { Mpsterfeld The Tester’s Role in Scrum: Practices @ In addition to other practices discussed in this course, testers sometimes use : Pair testing 2 Incremental test design a Keyword-driven automation Mind mapping ® Practices discussed in Foundation, Advanced Test Analyst, and Advanced Technical Test Analyst are also useful vor masertt Ale Teer Foundation Mastered Training Cente Page 08 Masterfield Oktat6kézpont - www.masterfield, hu 54ISTQB Foundation Level - Agile Tester Extension / “ocessiad Sample Exam Question © Let’s check your knowledge The instructor will select a sample exam question from the noteset © Solve the question The instructor will lead a discussion on the right (and wrong) answers, if needed Age Teer Foantion Masereld Tring Centre Page 08 Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Agile Testing Methods, Techniques, and Tools Section 1: Exercise Masterfield Oktatokézpont - www.masterfield, hu 55ISTQB Foundation Level - Agile Tester Extension YS “Mesterfield Exercise: Omninet Test Planning © For the Omninet payment processing user story considered so far, determine: = What: test scope and extent of testing for this feature (define tests for each quadrant) = Where: the test environment, test data, and test props needed to test it = Dependencies: functions, code, system components, vendor, technology, tools, and activities associated with testing this feature ® Define tasks for this user story and plan the schedule of the tasks in the current iteration © Note any additional planning issues you observe omar Ale Teter Futon Maserld Tang Cente Page 1 +S % Mesterfiele Debrief: Omninet Test Planning ® Solutions should include: What: acceptance and rejection of payments; extent of testing depends on level of risk 8 Where: a prototype including the payment subsystem, block rates, and “fake” cards/cash = Dependencies: payment subsystem ready, payment UI ready, integration of payment subsystem to UL complete, ability to simulate payment approve/decline © You might have noted certain project risks, such as: vendor failure to deliver, delays assembling prototypes, lack of clarity on expected behavior Ale Teste Foundation Masel Training Cente Page 12 Masterfield Oktatékézpont - www.masterfield, hu 56ISTQB Foundation Level - Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Agile Testing Methods, Techniques, and Tools Section 2: i Assessing Quality Risks and Estimating Test Effort \{ Mesterfield Chapter 3, Section 2: Learning Objectives © FA-3.2.1 Assess product quality risks within an agile project (K3) © FA-3.2.2 Estimate testing effort based on iteration content and product quality risks (K3) wtf Ale Teer Foun Mastered Trang Cente Pages Masterfield Oktatokézpont - www.masterfield, hu 57ISTQB Foundation Level ~ Agile Tester Extension “rears Quality Risks and Estimation © Reduce quality risk to an acceptable level ® Lightweight techniques can be used: 8 Identify quality risks Assess level of risk 2 Estimate test effort 8 Mitigate risks through test design, implementation, and execution ® Short iterations and fast change have implications svn masfld a ‘Ale Teter Foundation Masel Trning Cente Pages © Select, allocate, and prioritize test conditions to maximize effectiveness and efficiency © Quality risk analysis supports this process Risk: a possible negative outcome s Level of risk: based on likelihood and impact Quality risks: potential problems with product quality s Project risks: potential problems for project success © Agile quality risk analysis occurs: Ata high evel during release planning by business Stakeholders & Ata detailed level during iteration planning by the whole team. In each iteration, the tester designs, implements, and executes tests for the risks Aaile Teser Foundation Masterild Training Cee Page 116 Masterfield Oktatékézpont - www.masterfield, hu 58ISTQB Foundation Level ~ Agile Tester Extension 4 \ Masterfield Quality Risks © Quality risks include all features and attributes that can affect customer, user, stakeholder satisfaction Incorrect calculations (functional) Slow response time (non-functional performance risk) = Confusing interface (non-functional usability tisk) ® Risk analysis prioritizes tasks and guides the sizing of the tasks High risks require extensive testing, come earlier, and involve more story points = Low risks receive cursory testing, come later, and involve fewer story points ® Risk-based prioritization also includes sprint backlog items vnunet Ale Teer Founésion Materiel Trang Cente Page 17 S “Mestertials Process of Quality Risk Analysis © Inagile, same techniques apply as in the Foundation ® Agile quality risk analysis process 8 Gather the agile team sist iteration backlog items & Identify functional, non-functional quality risks for each item 18 Assess identified risks: categorize each risk, determine risk level 4 Build consensus and ensure a good distribution of risk ratings 18 Use level of risk to choose extent of testing s Select appropriate test techniques for each risk iter © Adjustments may occur during an iteration © Risk analysis may detect opportunities for early defect removal (e.g., problems in user stories) mater Al Test Fondation Masterelé Tang Cire Page 08 Masterfield Oktatékbzpont - www.masterfield.hu 59ISTQB Foundation Level ~ Agile Tester Extension \ Mosterield J cua sks ae potential system problems which could reduce user stsiction isk print uber Aggregate measur of problem sk oo information | requirements, ser stor, oF ther isk fmpe bss come or options sk of ptm [> Lk et ek of bn >) i \ \ = i Likeli-| | | Risk | Extent of Quality Risk hood Impact! Pri #| Testing. | Tracing Risk Category | aki ine? - Hake Airc of ey high Y raceatezoes 2—Hign | The productor anhelp | 3=-Mediam | technical and rEaeasive fami te Stow | bisnessik it and jo ey tow | tom your memo ce scum Ae Ter Foun Masri ing Cente fae 19 7, + “i Mesterfiald Example: Allocating Test Effort ‘© Extensive: run large number of tests, both broad and deep, combine and vary interesting conditions, use all relevant techniques with Strong coverage criteria © Broad: run medium number of tests, exercise many different interesting conditions, use most relevant techniques with medium coverage criteria © Cursory: ran small number of tests, sample most interesting conditions, use efficient techniques with weak coverage criteria © Opportunity: leverage other tests or activities to test 1-2 inferesting conditions, investing very little time and effort, using reactive techniques especially © Report bugs only: allocate only a small amount of extra lime to report and manage these accidental bugs worms Ale Teer Fomation Mastrle Tsing Centre Page 120 Masterfield Oktat6kbzpont - www.masterfield.hu 60ISTQB Foundation Level - Agile Tester Extension / “Cetera Estimating Testing Effort ® Test strategy is defined during release planning © During iteration planning, user stories are estimated (eg., via planning poker in story points) ® Story points give implementation effort © Risk level should influence story points ® Planning poker can be used to Feach consensus, involve whole team, and avoid missing anything ® Reliable estimation, including testing, is necessary for smooth work pace and meaningful velocity Ae Tester Fnsion Maser Tring Cvse Page 121 > * Mestecigld Sample Exam Question % Let’s check your knowledge ® The instructor will select a sample exam question from the noteset Solve the question © The instructor will lead a discussion on the right (and wrong) answers, if needed Agile Teer Fountion MastriléTraning Cre Page 122 Masterfield Oktatokézpont - www.masterfield.hu 61ISTQB Foundation Level - Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Agile Testing Methods, Techniques, and Tools Section 2: Exercise YS “KMestertield Exercise: Omninet Risk and Estimation © For the Omninet payment processing user story considered so far, determine: 2 What quality risks exist (include functional and non- functional risks) What level of risk is associated with each risk 8 What extent of testing is required for each risk The effort associated with doing that amount of testing 1 Estimate working hours related to testing (without unit and integration test) ® You may refer to the Marketing Requirements Document to clarify details © Template shown on next page vrata Agle Tester Foetation Maserld Taig Cee Page 124 Masterfield Oktatdkézpont - www.masterfield.hu 62ISTQB Foundation Level - Agile Tester Extension Masterfiel Mi Ansterfield Likeli- Risk | Extent of Quality Risk “hood [Impact] Pri #| Testing. | Tracing . q ester Ae Tver Foon Meer Tang Cee age Debrief: Omninet Risk. and Estimation ® Examples of risks include: Accepting invalid payments Rejecting valid payments 2 Time-out during payment approval process Slow payment approval process © The level of risk is influenced by: = Implementation assumptions (buy vs. build) 8 Frequency of failure in production Extent of testing can be significant if risk level is high ® The associated effort could influence the buy vs, build decision and decision to support cash Agile Tester Founéton MasterielaTaning Cate Page 126 Masterfleld Oktatékézpont - www,masterfield.hu 63ISTQB Foundation Lev Agile Tester Extension el ~ Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Agile Testing Methods, Techniques, and Tools Section Techniques in Agile Projects Chapter 3, Section 3: Learning Objectives @ FA-3,3.1 Interpret relevant information to support testing activities (K3) © FA-3.3.2 Explain to business stakeholders how to define testable acceptance criteria (K2) © FA-3.3.3 Given a user story, write acceptance test- driven development test cases (K3) ® FA-3.34 For both functional and non-functional behavior, write test cases using black box test design techniques based on given user stories (K3) @ FA.3,3.5 Execute exploratory testing to support the testing of an Agile project (K3) Al Tester Funston Mastereld Tating Cente Page 18 Masterfield Oktatékézpont - www.masterfield. hu 64ISTQB Foundation Lev Agile Tester Extension el - > “Menertele Techniques in Agile Projects © The test techniques and levels for traditional projects apply to agile projects ® However, factors influence and vary the manner of use of these techniques and levels © Terminology is different © The amount of documentation is reduced @ Requirements are often user stories in a prioritized release backlog, ® Non-functional requirements are sometimes specified as user stories, too, though this can be problematic oval Ale Teer Feunion Mastered Trang Cenve age 29 Test Bases in Agile Projects © User stories © Defects found (e.g,, other products, previous releases), sometimes organized as a defect taxonomy © System major functions and features © Relevant quality characteristics (e.g., reliability, maintainability) © User profiles and personas © Supported configurations © Any relevant standards © Quality risks © User documentation @ Marketing and web material vnemasterelé Ale Tester Fomeion Materold Tring Conte Page 10 Masterfleld Oktatékézpont ~ www.masterfield.hu 65ISTQB Foundation Level ~ Agile Tester Extension User Story “Done” ® Consider the following criteria: «© Each user story consistent with the others in the iteration f Aligned with product theme & Understood by the entire agile team 1 Have sufficiently-detailed, testable acceptance criteria ® Card, conversation, and confirmation completed 1 User story acceptance tests completed & Development and test tasks for selected user stories identified, estimated, and within achievable velocity © “Done” in this case means the user story can be a programming and testing ba sematrfld he Ale Tester Foundation Masel Trang Cente Page 131 S “rtostesfile Done vs. Ready im) ol Ale Teer Foditice ; age 122 Masterfield Oktatékézpont - www.masterfield.hu 66ISTQB Foundation Level ~ Agile Tester Extension Testable Acceptance Criteria © Testable acceptance criteria must addres: 1 Externally observable functional behavior 2 Relevant quality characteristics, especially non- functional ones # Steps to achieve goals or tasks (use cases) & Business rules or procedures relevant to the user story 8 Interfaces between system and users, other systems, external data repositories, etc. # Design and implementation constraints Format, types, valid/invalid/default data © Can be addressed textually and/or graphically ove materfl ‘gle Tater Fomeation Materld Taing Cente Page on Other Information Needed © Testers also need = Information about testing interfaces = What tools are available to support testing Clarification on system operation and utilization (if test bases uncleas) '8 Clear definition of done (Shared across team), including test coverage © Given the lightweight documentation, consider if you have necessary knowledge and skill © Throughout iteration, information gaps that affect testing will be found © Testers must work collaboratively with others on the team to resolve those gaps © Unlike sequential projects, getting relevant information for testing is an ongoing process on agile projects © Measuring whether a specific test level or activity is done is part of the tester role ema Ale Tester Foundtion Masterele Tring Core Page 1 Masterfield Oktat6kézpont - www.masterfleld.hu 67ISTQB Foundation Level ~ Agile Tester Extension Al Tester Fnton Ale Teer Founion Mosterfield Example: User Story Development Assume you are testing a browser-based application to allow online bill payment You receive the following user story: “Asa customer, I want to be able to open a popup window that shows the last 30 transactions on my account, with backward/ forward arrows allowing me to scroll through transaction history, so that I can see my transaction history without closing the ‘enter payment amount’ window.” e You'll work with the business stakeholder to define: Sufficiently-detailed, testable acceptance criteria 2 User story acceptance tests Example: User Story Acceptance Criteria User Story ® Asacustomer, I want to be able to open a popup window that shows the last 30 transactions on my account, with backward/forward arrows allowing me to scroll through transaction history, so that I can see my transaction history without closing the “enter payment amount” window MasereldTating Centre Page 5 S Krmostesfiele Acceptance Criteria © Inally populated with 30 most recent transactions ine uansactons display ‘No tansacion Nistor yet Backward scrolls back 10 transactions forward scrolls forward 10 transactions “Transaction data retrieved only for curent account Displays within 2 seconds of pressin “chow transaction history” centrol. = Backward forward arrows at bottom Conforms to corporate UI standard © Canminimize or close pop-up through standard controea upper ight © Properly opens inall supported bromsel vom ie Masterfield Oktatékézpont ~ www.masterfield, hu Macerld Tang Conre Page 16 68ISTQB Foundation Level - Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: x Agile Testing Methods, Techniques, and Tools Section 3: Exercise 1 Exercise: Payment User Story ® Consider the following user story for payment processing "Asa customer, I want to be able to use a credit card (Visa, MasterCard, or American Express), a debit card (Cirrus or Plus), and local currency (cash only) to make a payment on the Omninet kiosk, so that I can purchase blocks of time on the Internet’ © Refine the acceptance criteria that you developed in the exercise for section 1.2 ® Identify additional information you would need, beyond what's in the user story and/or the Marketing Requirements Document (MRD) soumatereld a Ae Tse Foon Msterls Tring Centre Page 8 Masterfield Oktatékézpont - 69 www.masterfield.huISTQB Foundation Level - Agile Tester Extension ° e ° Masterfield Oktat6kbzpont - www.masterfield,hu ‘le est Fundtion Maserld Trang Cre Page 138 Aale Teer Fonstion Mastertls Ting Centre Page 140 ~/ “tent Debrief: Refined Acceptance Criteria Acceptance criteria refinements might include: 2 Thescreen prototypes mentioned in the MRD 1 Criteria related to response time, recoverability issues (eg. ifa session rashes) usability / Ut standards, and other quality charatteristis 1 Steps describing credit card, debit card, and cash payment ‘© Rules about retry limits on cards = How the payment subsystem interacts with payment authorization Implementation assumptions (eg, build versus bay) Default purchase amount (if any) ‘You might ask about: '8 Can geta simulator for the payment authorization subsystem? How do I get the props I need (valid invalid cards and cash)? If we want to automate these tests, do we have tools that can coordinate GUT actions with authorization at the back-end? 4 Will the system allow payment and initiation ofa session during an update? 4 Beyond the risks and the acceptance criteria, what else needs to be covered? : event SM eertsciata Black-box: Test Design Agile testing is test-first (test design leads programming) You can use all techniques in the Foundation and Advanced Test Analyst to help design these tests For example, if a user story includes lower and upper limits for an input value, test the boundaries (valid and invalid) as well as other equivalence partitions Boundary values can be useful to test non-functional requirements For example, if the system should support 100 concurrent users, test that (and probably beyond) Keep test documentation lightweight during test design (eg,, don’t use IFEE 829 templates) orate 70ISTQB Foundation Level - Agile Tester Extension Example: Black-box Test Design ® Consider these acceptance criteria = Initially populated with 30 most-regent transactions; ifno transactions, display "No transaction history yet 2 Backward serolls back 10 transactions; forwatd scrolls forward 10 transactions 1 Transtction daa retrieved only for current account ® Use equivalence partitioning and boundary value analysis to derive test cases © Test design reveals additional questions about behavior 10 partial “1 partial “1 multi ju Screen sen seroll sly scroll, a> FHSS HST ate \ \ \ — GREER show this \ (Gaes ae theca) Ser \ \ See Crore |_| omens 0 show | ster scrolling os | aterm | See] phn cat note J—Sno uchistory yee" Stoll | with many tn? 7 TYEE arrows? fod sro gl Tt Foudton Blades i Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Agile Testing Methods, Techniques, and Tools Section 3: Exercise 2 Masterfield Oktatokézpont - www.masterfield.hu 71ISTQB Foundation Level ~ Agile Tester Extension Exercise: Black-box Payment Tests ® Consider the following quality risks identified earlier Accepting invalid payments # Rejecting valid payments ® Use any of the black-box test design techniques from the Foundation Syllabus to create tests = Show your model = Define inputs and expect results @ List agile specific aspects related to the design of these test cases Age Teer Foun Masertfeld Tang Ce Pre 3 S “ mostertiels Debrief: Black-box Payment Tests ® You can use equivalence partitioning and boundary value analysis © The initial steps of that process are shown below, though we need further decomposition and defined expected results DOAWDE ad > QODESD Payment = a) @. ic =) DLE? ED GS) _ va watt ovo mee ie Ale Tester Founition asereld Tang Core Page Masterfield Oktatékézpont - www masterfield.hu 72ISTQB Foundation Level Agile Tester Extension < s < = \ Masterfi { Mesterfiste Acceptance Test-driven Development ® Acceptance test-driven development involves the agile team (including business) defining tests prior to programming, following this process: 8 Analyze, discuss, clarify user story Create tests for user story (whole team or test with team approval) © Tests are examples of how to use the system to accomplish something 2 Positive path ss Negative path & Nonfunctional © Tests are written in clear language for all project stakeholders © Tests must cover, but not expand, the user story severe Ale Teer Fondation Maserld Traring Cente Page us S “mesterfigis Example: ATDD for Pop-up Window © Cover EP/BVA tests design a alisha vahingtn,29 tx inthis act carter and tin other ace © Try navigation forward and @ kenji_yamiato, 30 trx in this acct backward (positive, negative) ad . © Create the following accounts Mank-willams, 31 tx this acct and dave smith no transactions 3 Iintacwong wancactoreig & ferny_banKbaum,39 tx this act another sesount only = cosmo_banciano, 40 tx this acct and 2 fosechemandes, Lx this acct trxinother act maxine_karoley, 41 tr in this acct ee oe eeeeate a pecan aera ee eee eee esteem Lanes he sect pls other acct Rak wtams Show aloe be [esr fe ine ist ie i “a ransactone Wis act plus other act | onm bavciane | show 37x allow bv ae TO Sei ci ‘ple Teter Foundation Page 16 Masterfield Oktatékézpont - www.masterfield.hu 73ISTQB Foundation Level - Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Beye Agile Testing Methods, Techniques, and Tools Section 3: Exercise 3 S “ Mostestield Exercise: ATDD for Payment Processing © Use the black-box tests you designed earlier to create an acceptance test-driven development table as shown previously ® Design behavior-driven test cases for this user story ® Create test automation keywords for this user story ® Note any additional test considerations (such as test data, props, etc.) required for the tests ® If you are not confident about your design, use the debrief from the previous exercise vnunet he ‘eile Teter Fondation Mastered Traine Cate Page 8 Masterfield Oktatékézpont ~ www.masterfield. hu 74ISTQB Foundation Level ~ Agile Tester Extension \ Masterfield Y Solution: ATDD Table Ale Tester Fondation Masel Trang Coote Page 49 “ier Debrief: ATDD for Payment Processing ® The table might include the following columns # Test ID 8 Test name & Action (eg, “insert card”) = Insert (eg, "valid amex card,” “fake cash") © Input (eg, “valid pin,” “invalid pin”) a Request (eg., "1 block,” “12 blocks”) Expected result (“start session,” “reject cash”) ® Automating this test would require the ability to simulate approve/ decline responses from an authorization simulation or test harness son mitered Able Tester Fount Materld Tang Cone ae 150 Masterfield Oktatkézpont - www.masterfleld.hu 78ISTQB Foundation Level - Agile Tester Extension “nenseite Exploratory Testing and Reactive Strategies © Exploratory testing and other techniques associated with reactive test strategies are useful in all situations, since requirements are never perfect © Inagile projects, limited documentation and on-going change make these reactive strategies even more useful © Blend reactive testing with other strategies (e.g,, analytical risk- based, analytical requiements-based,tegression-avetse) © For exploratory testing: 4 Analysis during iteration planning produces the test conditions) for ihe test charter ehich will guide see sesion (0150 minute) Sy a est thread (not time-boxed), «Test design and test execution oceurat the same time, covering the charter once software s delivered to testers : © Test design can use all dynamic test techniques discussed in Foundation, Advanced Test Analyst, and Advanced Technical ‘Test Analyst, influenced by the results of the previous tests ‘Ale Teter Foundton Masereld Trang Ceaee Page 51 Managing Exploratory Test Sessions ® Session-based test management is useful Session includes time to setup, design/ execute tests, and investigate bugs, and actual time should be recorded © Sessions should include activities for survey (basic familiarization), analysis (evaluate function), and deep coverage (corner cases, scenarios, interactions) ® Session charter may list actor (intended user), purpose (test conditions), setup (pre-conditions), priority, references (test basis), test data, activities (suggested actions), test oracle, variations to try vmasterfld ie ‘Ale Tester Fondation Materld ring Cente Page 132 Masterfield Oktat6kézpont - www.masterfield.hu 76ISTQB Foundation Level ~ Agile Tester Extension Questions and Heuristics © Questions to ask while exploring: ‘ Whatis most important to discover? 8 How might the system fail? 8 What does/should happen if/when? a Will customer/user be satisfied (validation)? © Does it install /upgrade/ uninstall? © Utilize all creativity, intuition, ideas, and skills with... ‘8 The system 1 The business domain The ways people use the software fa The ways the software fails © Also, consider heuristics such as boundaries, CRUD (Create, Read, Update, Delete), configuration variations, and possible interruptions ne mastereld Ale Teste Fometon Mostrle Trang Cer Page 53 MV Mesterfield Lagging © Regardless of the kind of testing being done, testers must log important details, such as: | What data, risks, user stories, ete, have been covered # Notes about interesting discoveries, system stability, defects found, next steps 11 Details to be escalated to relevant stakeholders 8 Concems or questions about expected behavior, test efficiency, test environments, test data, or the system The actual behavior (e.., screen captures) © If insufficient logging is done, testing may need to be repeated ‘© Test logs should be captured/ summarized in the relevant test management or task management process a tered Al Tester Fondation Mastrels Ting Cte Page 4 Masterfield Oktatokézpont - www.masterfield.hu 77ISTQB Foundation Lev Agile Tester Extension el ~ Example: Blended Test Strategy @ One of our clients uses the following approach to testing = Developers create automated unit tests using J-unit, and use static testing tools to evaluate code quality #8 Business stakeholders collaborate to create automated feature verification tests with Fitnesse & Independent testers create automated system regression tests using two proprietary tools & Senior independent testers also run exploratory tests as sessions and as ways of expanding the scope of scripted tests 1 Consultants (who do customization for clients) test the customizations in client environments ® Multiple strategies, types, and levels of testing Ale Teer Fondation Macerfeld Tsing Cea age 5 Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Agile Testing Methods, Techniques, and Tools Section 3: Exercise 4 Masterfield Oktatékézpont ~ www.masterfield. hu 78ISTQB Foundation Level - Agile Tester Extension Exercise: Exploratory Test Charter © Select any aspect of the Omninet system other than the payment processing described in section 3.1.2 © Create a test charter, using the template on the next page © Schedule the creation and running of test charters (during the current iteration) ® Summarize test levels and techniques used for this user story ® Use the test pyramid for planning the effort of the levels sr marl Ale ee oekton serene Cee Pe 57 Template: Exploratory Test Charter @ Actor © Purpose © Setup © Priority © References © Test data © Activities © Test oracle © Variations to try Ale Tester Foundation Masereld Tang Cenee Page 98 Masterfield Oktatékézpont - www.masterfield.hu 79ISTQB Foundation Level ~ Agile Tester Extension oS “KMeatertigld Debrief: Exploratory Test Charter Actor customer ® Purpose: check if filtering allows access to pornographic, objectionable, lewd ebscene,or violent sites, or blocks access te sie that aren © Setup: initiate «browsing session ® Priority high {© References! MRD section 3.1.6, user story “XYZ” 4 Test data: none needed & Activities: To get started, think of words that qualify as or are associated wih pomography, lewd behavior, Sbsceniy, violence oF are otherwise objectionable or could be objectionable to some pes: use a search engine to locate websites based on these words; ty to wt the site repent © Testorocle: As Justice Stewart said, you'll know it when you se it However, some people might have less tolerance for such things than You, so er onthe side of reporting questionable sis © Variations to try: the possibilities are endless Agile Teer Foun Macereld ating Cee Pre 139 S Kthosterticl Unit/ Integration Testing “Done” Unit Testing Integration Testing © 100% decision coverage © All functional requirements © Static analysis of all code tested positive and negative No unresolved major © All unit interfaces tested defects © All highest risks tested No technical debtin design ‘ay defects found are Allcode, unit tests,and unit TePorted test results reviewed © No unresolved major All unit tests automated defects Important characteristics © As many regression tests within agreed limits automated as possible vermeil Age Teer Fonte Mstrele Ting Cee age 60 Masterfield Oktatokézpont - www.masterfield.hu 80ISTQB Foundation Level - Agile Tester Extension i Mastertield System Test “Done” ® End-to-end tests of all features, user stories, and system functions completed successfully ® All user personas tested ® Thorough testing of relevant quality characteristics ® Production environments tested, with coverage of supported hardware and software configurations ® All quality risks covered ® System-level regression tests automated to the extent possible ® All defects reported © No unresolved major defects Ale Tse Fomsion Masel Trang Cone Page 161 Epic or Feature “Done” © Consider the following for epics or features (can span multiple user stories) w All constituent user stories and acceptance criteria defined and approved Design and code are complete, with no technical debt ot unfitished refactoring 1 Unit tests, integration tests, and system tests performed and done per agreed criteria No major open defects st User documentation (eg. release notes, user manuals, and on- line help) done © Having all the features done doesn’t mean the release is done; you might need: «t Further testing (¢,, performance testing) ts Resolution of additional bugs (e.., production bugs foun in previous releases) met Agile Teer Foinion Masterls Ting Cer Page Masterfield Oktat6kézpont - www.masterfield.hu 81ISTQB Foundation Level - Agile Tester Extension i, Iteration and Release “Done” Iteration Release @ All features done @ All relevant, necessary test coverage achieved 1 Regression New features © Feature integration tested © Relevant characteristics tested ® Quality is deemed © Documentation written, acceptable (e.g., defect reviewed, and approved find rate, backlog) © Ifthe iteration is done, © Residual quality risk software is potentially acceptable shippable, but might not Schedule and cost be shipped ‘le Teter Foundation Masel Trang Coute age 1 Sample Exam Question © Let's check your knowledge © The instructor will select a sample exam question from the noteset © Solve the question ® The instructor will lead a discussion on the right (and wrong) answers, if needed vem ‘Ale Teste Foun Masereld Tang Cne Pag 16 Masterfield Oktatékézpont - www.masterfield, hu 82ISTQB Foundation Level ~ Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Chapter 3: Agile Testing Methods, Techniques, and Tools Section 4: Tools in Agile Projects VAG; Chapter 3, Section 4: Learning Objective @ FA3.4.1 Recall different tools available to testers according to their purpose and to activities in Agile projects (K1) evel Mustereld Tring Cente Page 6 Masterfield Oktatékézpont - www.masterfield.hu 83ISTQB Foundation Level - Agile Tester Extension Tools in Agile Projects ® The tools in Foundation can be used, but often in different ways @ Some agile teams use test management tools, requirements management tools, and defect tracking, tools might be used © Others use agile-specific tool task management (which is sometimes ill-suited for test tasks) ® Configuration management tools are important to support test automation ® Additional tools are often used to enable team collaboration and information sharing © Tools should enable, not constrain, the team ‘le Teter Fudation Masel Tring Cte Page 67 \( Mosterfield Task Management and Tracking Tools @ Some teams opt for task management software © These tools can Record user stories and related tasks Support the estimation and velocity measurement processes ® Maintain traceability of development and test tasks to the associated user story 5 Track and summarize developer and tester status as the iteration proceeds '® Give metrics, charts, and dashboards of current status, down to the user story and task level and up to the iteration and. release level, for all stakeholders 4 Integrate with configuration management tools © Physical task boards can be used, instead Ale Teer Foendtin Maser Tring Cee Page 18 Masterfield Oktatékézpont - www.masterfield.hu 84ISTQB Foundation Level ~ Agile Tester Extension Scrum Task Board Sample Masterfield Oktatékézpont - www.masterfield.hu 85ISTQB Foundation Level - Agile Tester Extension Kanban Board Sample 2 nog 54m) caged) Teng) pate ne Ale Teer Foun ® To complement, e-mail, documents, and verbal communication © Wikis for: diagrams, discussions, photos of whiteboard drawings; a scrapbook of useful tools and techniques; metrics, charts, and dashboards on product status; recording conversations © Instant messages/ chats for: instant direct communication between teams, groups, and pairs; support for distributed teams; saving money via VOIP © Desktop sharing for: product demonstrations, code reviews, and pairing; recording product demonstrations Ale Tater Foust Mate Tring Cate Page 72 Masterfield Oktatékézpont - www.masterfield. hu 86ISTQB Foundation Level - Agile Tester Extension ~S “moresia'd CM, Build, and Distribution Tools © Continuous integration tools provide: 1 Quick feedback on code quality Stepwise integration of systems Visibility on build status and history = Automatic reporting, © Automatic deployment tools: 1 Locate and install appropriate build in test environment Reduce errors and delays of hand installation © Configuration management tools: Store source code, automated tests, manual tests, and other test work products = Provide traceability between versions of software and the specific tests used 4 Allow rapid change while saving historical information Ale Teste Fondation Masel Tang Cee age 72 Test Creation and Execution Tools @ Tools used by agile testers include: = Mind maps for test design = Application lifecycle management or task management for test case management Test data preparation, generation, load, validation, and anonymization tools = Automated test execution tools that support behavior- driven development, test-driven development, and acceptance test-driven development 1 Tools to capture and log activities during exploratory testing * Many open-source options are available sor mae Ale Tester Fondation MaserlsTanng Cenre Page 74 Masterfield Oktatokézpont - www.masterfield.hu 87ISTQB Foundation Level - Agile Tester Extension aS \* Merter Cloud Computing and Virtualization Tools © Virtualization can increase the test resources available © Setting up a new test environment can be quick and sometimes cheap ® Known-good configurations can be saved prior to installing a new release @ In addition to server virtualization, service virtualization, client virtualization, and data virtualization can be useful for testers vor mera Ale Tete Fotion Masterlé Tang Centre Page 15 Sample Exam Question ® Let's check your knowledge @ The instructor will select a sample exam question from the noteset ® Solve the question ® The instructor will lead a discussion on the right (and wrong) answers, if needed soem ie ‘Ale Tester Fountion Masel Tsing Cote Page 176 Masterfield Oktatékdzpont - www.masterfield. hu 88ISTQB Foundation Level - Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Questions, Comments, and Discussion about the Course? Agile Tester Foundation Adapting and Extending Testing Best Practices Fd Bibliography Masterfield Oktatékézpont - www.masterfield.hu 89ISTQB Foundation Level ~ Agile Tester Extension \{ Mepterfiels Syllabus Referenced Books 1 Leo van der Aalst and Cecile Davis, “TMap NEXT® in Scrum,” ICT-Books.com, 2013 Gojko Adzic, “Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing,” Neuri Limited, 2009 David Anderson, “Kanban: Successful Evolutionary Change for Your Technology Business,” Blue Hole Press, 2010 Kent Beck, “Test-driven Development: By Example,” Addison-Wesley Professional, 2002 ‘Atle Tester Foundation Mastecield Tring Centre Page 179) / K mostertiola \ Syllabus Referenced Books 2 Kent Beck and Cynthia Andres, “Extreme Programming Explained: Embrace Change, 2e” Addison-Wesley Professional, 2004 Rex Black, “Pragmatic Software Testing” John Wiley and Sons, 2007 Rex Black, “Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing, 3e,” Wiley, 2009 David Chelimsky et al, “The RSpec Book: Behavior Driven Development with Rspec, Cucumber, and Friends,” Pragmatic Bookshelf, 2010 vom Able Tester Foundton Maserld Tang Conse Pag 190 Masterfield Oktatékozpont - www.masterfield.hu 90ISTQB Foundation Level - Agile Tester Extension Syllabus Referenced Books 3 Mike Cohn, “User Stories Applied: For Agile Software Development,” Addison-Wesley Professional, 2004 Lisa Crispin and Janet Gregory, “ Agile Testing: A Practical Guide for Testers and Agile Teams,” Addison- Wesley Professional, 2008 Adam Goucher and Tim Reilly, editors, “Beautiful Testing: Leading Professionals Reveal How They Improve Software,” O'Reilly Media, 2009 Ron Jeffries, Ann Anderson, and Chet Hendrickson, “Extreme Programming Installed,” Addison-Wesley Professional, 2000 sommes ha Ale Teter Fonion Maseld Trang Cemre Page 181 Ki Syllabus Referenced Books 4 Capers Jones and Olivier Bonsignour, “The Economies of Software Quality,” Addison-Wesley Professional, 2011 Tilo Linz, “Testing in Scrum: A Guide for Software Quality Assurance in the Agile World,” Rocky Nook, 2014 Ken Schwaber and Mike Beedle, “Agile Software Development with Scrum,” Prentice Hall, 2001 Erik van Veenendaal, “The PRISMA approach’, Uitgeverij Tutein Nolthenius, 2012 Karl Weigers and Joy Beatty, “Software Requirements, 3e,” Microsoft Press, 2013 sore hs Ale Tester Fondation Masel Taning Cente Page 1 Masterfield Oktatokézpont - www.masterfield.hu onISTQB Foundation Level ~ Agile Tester Extension Standards and ISTQB Documents Referenced Standards RTICA/FAA DO-1788, Software Considerations in Airborne Systems and Equipment Certification, 1992 1S0/1EC 2500012005, Software Engineering - Software ‘oduct Quality Requirements and Evaluation (SQuaRE), 2005 Relevant ISTOB Documents ISTQB Advanced Level Test Analyst Syllabus, Version 2012 ISTQB Advanced Level Test Manager Syllabus, Version 2012 ISTQB Foundation Level Agile Tester Overview, Version 1.0 ISTQB Foundation Level Syllabus, Version 2011 svoumasterfld ie ‘Ale Tester Furdton MaterldTrning Cente Page 183 MY Ciencia Other Syllabus References Various contributors, guide.Agilealliance.org Various contributors, www.agilemanifesto.org Elisabeth Hendrickson, “Acceptance Test-driven Development,” testobsessed.com/ 2008/12/acceptance-test- driven-development-atdd-an-overview Bill Wake, “INVEST in Good Stories, and SMART Tasks,” xp123.com/ articles /invest-in-good-stories-and-smart-tasks Greg Kubaczkowski and Rex Black, “Mission Made Possible,” www.tbes-us.com/ images /documents/ Mission- Made-Possible.pdf Ken Schwaber and Jeff Sutherland, editors, “The Serum Guide,” www.scrum.org Various contributors, www sourceforge.net In some cases, link rot has made these references out of date; please report these situations to [email protected]. wnat ‘Ale Teer Fouton Masefed Traine Cente Page 18 Masterfield Oktatékézpont - www.masterfield.hu 92ISTQB Foundation Level ~ Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices eee Lor More Information... \ Mesterfield SS. ... Contact RBCS For over twenty years, RBCS has delivered services in consulting, outsourcing and training for software and hardware testing. Employing the industry's most experienced and recognized consultants, RBCS conducts product testing, builds and improves testing groups and hires testing staff for hundreds of clients worldwide. Ranging from Fortune 20 companies to start-ups, RBCS clients save time and money through improved product development, decreased tech support calls, improved corporate reputation and more. To learn more about RBCS, visit www.rbes-us.com, Address: RBCS, Inc. 31520 Beck Road. Bulverde, TX 78163-3911 usa, Phone: +1 (830) 438-4890 E-mail: [email protected] Web: www thes-us.com Twitter: @RBCS Facebook RBCS.Ine oon Able Tester Fenton Masereld Trang Cente ae 16 Masterfield Oktatékézpont - www.masterfield. hu 93ISTQB Foundation Level - Agile Tester Extension Agile Tester Foundation Adapting and Extending Testing Best Practices Thank you for your attention Ex and participation! pe. the material in this class ‘helpful for you in your career st professional! Change History Rev # | Date Released | Change (07 _[ Maria, 2014 [Tnitial draft during development (09 April, 2014 | Updated based on review comments and submitted for accreditation tothe ASTOB, O91 | Feb6,2015 | Mastrfeld Training Centre customization 10 [April 2015 [Finalized as part of creating e-learin 11 [July AS | Fed few minor ears moved dei veranda Ale ee eon vata Coen rae Masterfield Oktat6kbzpont - www.masterfield.hu 94ISTQB Foundation Level ~ Agile Tester Extension YS “ Mostertield Thank you for your attention and participation! www.tmasterfield.hu Masterfield Oktatokézpont ~ www.masterfield.hu 95M asterfi ‘eld Nyilvantartésba vétel (FINY) széma: 00595-2008. IEE NUNS Gyakorlat Minésitett szoftvertesztelé képzési program ISTQB Foundation Level - Agile Tester Extension modul Képzési adatok: Intenzitas: 16 tandra -2 x 8 x 45 perc Helyszin: 1134 Budapest, Robert Karoly krt. 82-84. zési progr zitette: Trinspire Kft. 1134 BUDAPEST, ROBERT KAROLY KRT. 82-84. TEL: (061) 2880176 FAX: (061) 2880177 WWW.MASTERFIELD.HUows suSru nv L0e-co02 “somo mBukdos Zouorsnen serene - an STON Eze = —evsmepda aeanys 1 - smog pune ere a uM 0 wo. ——vnennnnn epas as sumamoac ony swuai0g Jo 91qe1, _wownseq sweweunbey Bunaye¥ uA Powesou sub iy ‘1ae-002 ‘Soe wBuldog SER RR Sa NTN TED Somes tome wont aera ites gmt mero sn yeaa pana | speia | poe tsi] 0) 10% weia puoses | uray | exoum{| zo 10% yeisag| pega] ‘eroum{| yo) avep fa resorddy | pasoiddy uwondeosea | sommy aa) A, JuouND0g syuowasmMboy Supa] soy MAIDA 19UI9}U] IY HeNIIUG, 99Lyoreoea ponosoy shan #10z-c00z's9aua WBUKdOD rowoisney ‘saat SCL exp pe a OYS SSN uORDOUTUGD HAY & MO Bae _swopung vo aygeneas) saree ousqu 20 “exado Nop uO fo UO ang yo stop © yum zosm on placed Tey POH URED YEO "UDA IDO} 6x adsaoyoxd woo. a) sy zou aseypund oy syuea sosn ap 7 Bungse esau da dead Trews sort xp ogee jo spuoces (0p) Abas nam st KOH Yo PO} HALE aM UD (ei pur 6x adGonaid uoasns 205) (uo pose smn 20 S74) PAE HAG adSjojoud usoas 2) (quo prearasey 10 st ‘ssond vwondo a asm ap 8 es (rx adQoqord wars 93) afessoun auroojan Sau ue AeyIp legs SOI UMNO ED SUOTESES ADH, 10310 swuorssosyuaum yuo9 o Ange a Se Tom se SuOSIS sory se pur uaums noe uonewszopu o} ssa5pe ype suas 2}u09 E> apranud eYs UA puso ap 61 soane sane agg soy pur ‘soy rou ‘soda jno 9a es UNAS 24 Busaa.e pu wuouaked Sundanne “am 99 Tes 59595} BUTEIC 0" 40253815 A, anep ase9pps posinboy, _wounsoq swewesmboy BupeseH wURILID ere Lye cag powoseu subhu ny ‘L0z-¢00zsoawa WOuKdo, Foun (etgereseun Asa) pe sort amp soy twsuNdoG ATOKA HOHE UNNI AH 35 (2 syuousasrbos oumoag swtuasbay warsK5 UNO a 29S EU) ‘woysds Bunerado sx0puIM ry soso yous oaopdi}UDUT HOSOI, OL. a 0 ein Ssandig uno sounded SdH 962 HO] ¥ HONDOUIOD YUEN, saxras woneonddy sv dd suoneraaigge Buwory ayy ‘oolaxd stp jo sosodind op 203, Jo snus za soon apgeuoseas 1} 52 ‘pi sruossno peo igap pur “Pse> ome yor uo 0 Aa ‘soypadsoumn>op SMU adoos, 100Ly0 90605 onosou mubnu ny W102-2002 sone WBUKGOD urutewos our preg 1 9) worse motnan ur pony Sys0r4 30H an yo do xp ved par ISTTeYS 8004 IA UNO SASH} FL “meas poyp oy uoR>ause> aouoy Kew wae soquao [poop "rey 1993969 0} PARADE SON ej sodas 0 04 ‘ayepdn areas yoy ans sm arepdn aseayjos see ous sep feo vores sous umd joy, uosioa sos039 WunBIN worsiaa uaysis Bumerado won’ 298 0 219899 apue9 > sor Yow. 404 “SySON| oI wIEA.ONG OH AE AA TENE SIUABE 2H Te sys0ny oy siepdn areajosysnd ose Ser sae 294 Le, soins (go) Aas pu (0) way ua2ayaq pouod wopurer est Anan 205 Sepp jum rye Be AnD Oy DOLIOOSA TRS SON a ‘papeoyiano sar veyy 80] 2 sIfor 194295 uoREDdde oxy to MOREDRECE pePAIN Kj ‘PauuODs TeYS SOF aN OE OM P>POI suornuap qestarysayno 20 2pe> snore x08 STIR, woun20q siowsunbey BuneRseH UNAS jpn ou are op 3 yo seteg onosou 6s ny ‘10z-c00 ‘Sat 2 BLO eo worsen soyqe aes wounded aymumsed parepdy) BONN svonup somes 0 wopous posjou MON, soypyed eweug x0 waxes Sumesedg ‘papa saepdn ‘sou, sevepdn 104s pur ue sanz ap 0 ooUO> [PoyS BOP YH 2H FIO} WY doz iy dqponewoine aed aye pe sepdn aresuyos SaokeysumIM ANNO LP wpa asenyos OTERO ‘Woon aun yp ye s28.40n9 2p HIS ue 3954024 a ae “A10)= RIA AYP 480P ‘oH papwoqwaop ZENO Pu SAEIOOD Te HTD peo ‘sayeuruy uowsas © aouo—paysta iy “#'9—AATEMLpIAUOD 95H and ojaup Sumony (ous postu oj vont x pimjatou) 90 BABB] sem om yo aso suoisos jeu9) ews 1057) sone woog poo: sino 10 wom ‘sna waa 20 Surpuas sure sory Yow HeLONd “poo ajqeuonoalgo onyesousd yo Seyderp 249519 ews soursg ‘soe ang ur your 2p 555558 yo SoSH Ju 98 remo svn -osmoug pu wns Buperodo a 4q pauoddas saenBuey ye oddns or pamSiguoo 24 [ef 089404 SONY FOURS YEH "woysses a 109 alten ax 3227s 0) onl ayp pi s98n au wea Tes woos axnonjoy an ‘pas Apuousino> sue sane acu ago $9201 Up ‘pe pores sro} aon yey Areurd ayy wt ayexaco oy posnSiguno 9q es 48004 TUTEIC PE omer pads uonrouun> Sst 9c weap sapeoo ane reps sin “suoReuIe>219e> 30.0944 wt ame SSO UO wouns0q stuousunbey Buna uD sve 1011019608 penesny suOny ny Yioe-e007soRu.a WOUKEOD ouorsnea ‘pumas ayy jo smoure ayn Aad es alessour au “Aeanse sem uossoe aye aBesea® aaoa es 1 ye um pasmum Su 40} puns & 241004 IeyS DSN 24, vworssos yup teu) Ker Se Mp ‘hep sad ou yo sonumur (og) Kos vei asour pp 0} uae we 205 pasos s apustano Ktostauodng sum jo 9044 Supe Sa worsas 5 aen © AONE OY AREA TENS SHB HID TE 0 PON wouncea swowsunbsy Bune UNIS 102