Muutke küpsiste eelistusi

E-raamat: Testing in Scrum: A Guide for Software Quality Assurance in the Agile World

  • Formaat: 240 pages
  • Ilmumisaeg: 28-Mar-2014
  • Kirjastus: Rocky Nook
  • Keel: eng
  • ISBN-13: 9781492001539
Teised raamatud teemal:
  • Formaat - EPUB+DRM
  • Hind: 33,50 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
  • Formaat: 240 pages
  • Ilmumisaeg: 28-Mar-2014
  • Kirjastus: Rocky Nook
  • Keel: eng
  • ISBN-13: 9781492001539
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

"These days, more and more software development projects are being carried out using agile methods like Scrum. Agile software development promises higher software quality, a shorter time to market, and improved focus on customer needs. However, the transition to working within an agile methodology is not easy. Familiar processes and procedures change drastically. Software testing and software quality assurance have a crucial role in ensuring that a software development team, department, or company successfully implements long-term agile development methods and benefits from this framework. This book discusses agile methodology from the perspective of software testing and software quality assurance management. Software development managers, project managers, and quality assurance managers will obtain tips and tricks on how to organize testing and assure quality so that agile projects maintain their impact. Professional certified testers and software quality assurance experts will learn how to work successfully within agile software teams and how best to integrate their expertise. Topics include: Agile methodology and classic process models How to plan an agile project Unit tests and test first approach Integration testing and continuous integration System testing and test nonstop Quality management and quality assurance Also included are five case studies from the manufacturing, online-trade, and software industry as well as test exercises for self-assessment. This book covers the newISTQB Syllabus for Agile Software Testing and is a relevant resource for all students and trainees worldwide who plan to undertake this ISTQB certification"--



These days, more and more software development projects are being carried out using agile methods like Scrum. Agile software development promises higher software quality, a shorter time to market, and improved focus on customer needs.

However, the transition to working within an agile methodology is not easy. Familiar processes and procedures change drastically. Software testing and software quality assurance have a crucial role in ensuring that a software development team, department, or company successfully implements long-term agile development methods and benefits from this framework.

This book discusses agile methodology from the perspective of software testing and software quality assurance management. Software development managers, project managers, and quality assurance managers will obtain tips and tricks on how to organize testing and assure quality so that agile projects maintain their impact. Professional certified testers and software quality assurance experts will learn how to work successfully within agile software teams and how best to integrate their expertise.

Topics include:

  • Agile methodology and classic process models
  • How to plan an agile project
  • Unit tests and test first approach
  • Integration testing and continuous integration
  • System testing and test nonstop
  • Quality management and quality assurance


Also included are five case studies from the manufacturing, online-trade, and software industry as well as test exercises for self-assessment.

This book covers the new ISTQB Syllabus for Agile Software Testing and is a relevant resource for all students and trainees worldwide who plan to undertake this ISTQB certification.
1 Introduction 1(6)
1.1 Target Audience
2(1)
1.2 Book Contents
3(2)
1.3 Case Study
5(1)
1.4 Website
6(1)
2 Agile vs. Traditional Approaches 7(18)
2.1 Scrum
7(8)
2.2 Kanban
15(2)
2.3 Traditional Process Models
17(4)
2.4 Comparing Process Models
21(4)
3 Planning an Agile Project 25(16)
3.1 Product Vision
26(1)
3.2 Architecture Vision
26(2)
3.3 Product Backlog
28(2)
3.4 Story Map
30(2)
3.5 Sprint Backlog
32(1)
3.6 Team Charter
33(2)
3.7 Test Planning and Test Management
35(2)
3.7.1 Traditional Test Management
35(1)
3.7.2 Test Management in Scrum
35(2)
3.7.3 Test Levels in Scrum
37(1)
3.8 Introducing Agile Planning
37(1)
3.9 Questions and Exercises
38(3)
3.9.1 Self-Assessment
38(1)
3.9.2 Methods and Techniques
39(1)
3.9.3 Other Exercises
39(2)
4 Unit Testing and Test First 41(38)
4.1 Unit Testing
41(17)
4.1.1 Classes and Objects
42(1)
4.1.2 Testing the Methods of a Class
43(8)
4.1.3 Object State Testing
51(3)
4.1.4 State-Based Coverage Criteria
54(2)
4.1.5 Testing with Method Permutations
56(2)
4.2 Test First
58(10)
4.2.1 Test First and Scrum
61(1)
4.2.2 Implementing Test First
62(2)
4.2.3 Using Test First
64(4)
4.3 Unit Testing Frameworks
68(1)
4.4 Stubs, Mocks and Dummies
69(2)
4.5 Unit Test Management
71(4)
4.5.1 Unit Test Planning
74(1)
4.6 Questions and Exercises
75(4)
4.6.1 Self-Assessment
75(1)
4.6.2 Methods and Techniques
76(1)
4.6.3 Other Exercises
76(3)
5 Integration Testing and Continuous Integration 79(30)
5.1 Integration Testing
79(7)
5.1.1 Typical Integration Failures and Their Causes
80(2)
5.1.2 Designing Integration Test Cases
82(3)
5.1.3 The Differences between Unit and Integration Tests
85(1)
5.2 The Role Played by System Architecture
86(4)
5.2.1 Dependencies and Interfaces
88(1)
5.2.2 Testability and Testing Effort
89(1)
5.3 Integration Levels
90(4)
5.3.1 Class Integration
90(2)
5.3.2 Subsystem Integration
92(1)
5.3.3 System Integration
92(2)
5.4 Traditional Integration Strategies
94(1)
5.5 Continuous Integration
94(9)
5.5.1 The CI Process
95(3)
5.5.2 Implementing CI
98(3)
5.5.3 Optimizing CI
101(2)
5.6 Integration Test Management
103(2)
5.7 Questions and Exercises
105(4)
5.7.1 Self-Assessment
105(1)
5.7.2 Methods and Techniques
106(1)
5.7.3 Other Exercises
107(2)
6 System Testing and Testing Nonstop 109(32)
6.1 System Testing
109(3)
6.2 The System Testing Environment
112(2)
6.3 Manual System Testing
114(3)
6.3.1 Exploratory Testing
114(1)
6.3.2 Session-Based Testing
115(1)
6.3.3 Acceptance Testing
116(1)
6.4 Automated System Testing
117(9)
6.4.1 Record/Playback Testing
117(2)
6.4.2 Keyword-Driven Testing
119(5)
6.4.3 Behavior-Driven Testing
124(2)
6.5 Using Test First for System Testing
126(1)
6.5.1 System Test Repository
126(1)
6.5.2 Pair Programming
127(1)
6.6 Non-functional Testing
127(4)
6.7 Automated Acceptance Testing
131(1)
6.8 When Should System Testing Take Place?
132(3)
6.8.1 System Testing in a Final Sprint
132(1)
6.8.2 System Testing at the End of a Sprint
133(1)
6.8.3 System Testing Nonstop
134(1)
6.9 The Release Sprint and Deployment
135(2)
6.10 System Test Management
137(1)
6.11 Questions and Exercises
138(3)
6.11.1 Self-Assessment
138(1)
6.11.2 Methods and Techniques
139(1)
6.11.3 Other Exercises
140(1)
7 Quality Management and Quality Assurance 141(28)
7.1 Traditional Quality Management
141(5)
7.1.1 The ISO 9000 Standard
141(1)
7.1.2 The Principles of PDCA
142(1)
7.1.3 Strengths and Weaknesses
143(2)
7.1.4 Process Modeling and Software Development
145(1)
7.2 Agile Quality Management
146(5)
7.2.1 Simplifying QM Documentation
146(2)
7.2.2 Changing QM Culture
148(2)
7.2.3 Retrospectives and Process Improvement
150(1)
7.3 Dealing with Compliance Requirements
151(3)
7.3.1 Requirements of Software Development Processes
151(1)
7.3.2 Traceability Requirements
152(2)
7.3.3 Product Attribute Requirements
154(1)
7.4 Traditional Quality Assurance
154(2)
7.4.1 QA Tools
155(1)
7.4.2 Organization
155(1)
7.5 Agile Quality Assurance
156(6)
7.5.1 Principles and Tools
156(3)
7.5.2 Strengths and Weaknesses
159(3)
7.6 Agile Testing
162(3)
7.6.1 Critical Factors for Successful Agile Testing
162(2)
7.6.2 Test Planning in Scrum
164(1)
7.7 Skills, Training, Values
165(2)
7.8 Questions and Exercises
167(2)
7.8.1 Self-Assessment
167(1)
7.8.2 Methods and Techniques
168(1)
7.8.3 Other Exercises
168(1)
8 Case Studies 169(40)
8.1 Using Scrum to Develop Video and Audio Production Software
169(5)
8.2 Nonstop System Final Testing—Using Scrum to Develop the TestBench Tool
174(7)
8.3 Using Scrum to Develop an Online Store
181(3)
8.4 Introducing Scrum at ImmobilienScout24
184(6)
8.5 Scrum in a Medical Technology Environment
190(10)
8.6 Testing in Scrum at GE Oil & Gas
200(9)
Appendix 209(12)
A Glossary
211(4)
B References
215(6)
B.1 Literature
215(2)
B.2 Websites
217(2)
B.3 Standards
219(2)
Index 221
Tilo Linz is CEO of imbus AG, a leading service company for software testing in Germany. He is president of the German Testing Board and served as president of the ISTQB from 2002-2005. His work emphasis is on consulting and coaching projects on software quality management, optimizing software development, and testing processes.