Crispin and Gregory define agile testing and illustrate the tester's role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors of agile testing.

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.

The Agile Software Tester is the must have book for any forward thinking software tester who wants to move forward in the fast moving and existing world of agile software development. This publication will introduce you to this challenging and yet rewarding world and help you build a fulfilling and enjoyable career. From manual testing to automation, it is all here. While many organisations have adopted the agile framework fully with a carefully planned strategy and 100% company commitment which means they are now reaping the benefits gained there are still plenty of software companies out there who have, for one reason or another, not. These companies still ignore the agile framework methodology or they have simply placed a taskboard in the centre of the office and stated ‘there, we are agile’. While it is true that the agile methodology is not for everyone and not every software development project is suited to the framework it is, however, the way forward for the majority of companies who are involved in software development. As agile has grown in popularity and usage over the decades the amount of literature about the subject has also grown. However most of the books currently available on the market focus on the project management or software development areas of the software development life cycle, there is still very little for the agile software tester to read. In the agile world; testing and the software tester are just as important as any other process or person and that is why I have written this book. Hopefully experienced and new testers alike will find some useful pointers within these humble pages which will help them enhance their career and enjoyment of testing software. Version 7

In an IT world in which there are differently sized projects, with different applications, differently skilled practitioners, and on-site, off-site, and off-shored development teams, it is impossible for there to be a one-size-fits-all agile development and testing approach. This book provides practical guidance for professionals, practitioners, and researchers faced with creating and rolling out their own agile testing processes. In addition to descriptions of the prominent agile methods, the book provides twenty real-world case studies of practitioners using agile methods and draws upon their experiences to propose your own agile method; whether yours is a small, medium, large, off-site, or even off-shore project, this book provides personalized guidance on the agile best practices from which to choose to create your own effective and efficient agile method.

Janet Gregory and Lisa Crispin pioneered the agile testing discipline with their previous work, Agile Testing. Now, in More Agile Testing, they reflect on all they've learned since. They address crucial emerging issues, share evolved agile practices, and cover key issues agile testers have asked to learn more about. Packed with new examples from real teams, this insightful guide offers detailed information about adapting agile testing for your environment; learning from experience and continually improving your test processes; scaling agile testing across teams; and overcoming the pitfalls of automated testing. You'll find brand-new coverage of agile testing for the enterprise, distributed teams, mobile/embedded systems, regulated environments, data warehouse/BI systems, and DevOps practices. You'll come away understanding - How to clarify testing activities within the team - Ways to collaborate with business experts to identify valuable features and deliver the right capabilities - How to design automated tests for superior reliability and easier maintenance - How agile team members can improve and expand their testing skills - How to plan "just enough," balancing small increments with larger feature sets and the entire system - How to use testing to identify and mitigate risks associated with your current agile processes and to prevent defects - How to address challenges within your product or organizational context - How to perform exploratory testing using "personas" and "tours" - Exploratory testing approaches that engage the whole team, using test charters with session- and thread-based techniques - How to bring new agile testers up to speed quickly-without overwhelming them The eBook edition of More Agile Testing also is available as part of a two-eBook collection, The Agile Testing Collection (9780134190624).

Software development continues to be an ever-evolving field as organizations require new and innovative programs that can be implemented to make processes more efficient, productive, and cost-effective. Agile practices particularly have shown great benefits for improving the effectiveness of software development and its maintenance due to their ability to adapt to change. It is integral to remain up to date with the most emerging tactics and techniques involved in the development of new and innovative software. The Research Anthology on Agile Software, Software Development, and Testing is a comprehensive resource on the emerging trends of software development and testing. This text discusses the newest developments in agile software and its usage spanning multiple industries. Featuring a collection of insights from diverse authors, this research anthology offers international perspectives on agile software. Covering topics such as global software engineering, knowledge management, and product development, this comprehensive resource is valuable to software developers, software engineers, computer engineers, IT directors, students, managers, faculty, researchers, and academicians.

Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach.

Uncover surprises, risks, and potentially serious bugs with exploratory testing. Rather than designing all tests in advance, explorers design and execute small, rapid experiments, using what they learned from the last little experiment to inform the next. Learn essential skills of a master explorer, including how to analyze software to discover key points of vulnerability, how to design experiments on the fly, how to hone your observation skills, and how to focus your efforts. Software is full of surprises. No matter how careful or skilled you are, when you create software it can behave differently than you intended. Exploratory testing mitigates those risks. Part 1 introduces the core, essential skills of a master explorer. You'll learn to craft charters to guide your exploration, to observe what's really happening (hint: it's harder than it sounds), to identify interesting variations, and to determine what expected behavior should be when exercising software in unexpected ways. Part 2 builds on that foundation. You'll learn how to explore by varying interactions, sequences, data, timing, and configurations. Along the way you'll see how to incorporate analysis techniques like state modeling, data modeling, and defining context diagrams into your explorer's arsenal. Part 3 brings the techniques back into the context of a software project. You'll apply the skills and techniques in a variety of contexts and integrate exploration into the development cycle from the very beginning. You can apply the techniques in this book to any kind of software. Whether you work on embedded systems, Web applications, desktop applications, APIs, or something else, you'll find this book contains a wealth of concrete and practical advice about exploring your software to discover its capabilities, limitations, and risks.

Agile software development has grown in popularity and usage over the decades. As a result, the amount of literature about the subject has also grown tremendously. However most of the books currently available on the market focus on the project management or software development areas of the software development life cycle, there is still very little for the agile software tester to read. In the agile world testing and the Software QA Tester are just as important as any other process or person and that is why I have written this book. Hopefully experienced and new QA's alike will find some useful pointers within these humble pages which will help them enhance their career and enjoyment of testing software. The QA professionals involvement in agile projects remains challenging because of the very different nature of the agile methodology compared to older methodologies such as waterfall and the V model. This is also not helped by a level of misunderstanding about the true nature of agile that still persists in many companies and deep-rooted prejudices aimed at QA's by some programmers and project managers (they are nothing more than failed programmers being a common feeling). Although there are many QA professionals succeeding in agile projects, many others continue to struggle to succeed and achieve their true potential that their skills and dedication deserve. QA's who have spent many years testing outside of agile can also often struggle to make the jump across the waterfall. However with quality training, good management and self-belief this jump can be completed, this is where the fifth edition of this book comes in.

Softwaretests stellen eine kritische Phase in der Softwareentwicklung dar. Jetzt zeigt sich, ob das Programm die entsprechenden Anforderungen erfüllt und sich auch keine Programmierungsfehler eingeschlichen haben. Doch wie bei allen Phasen im Software-Entwicklungsprozess gibt es auch hier eine Reihe möglicher Fallstricke, die die Entdeckung von Programmfehlern vereiteln können. Deshalb brauchen Softwaretester ein Handbuch, das alle Tipps, Tricks und die häufigsten Fehlerquellen genau auflistet und erläutert, damit mögliche Testfehler von vornherein vermieden werden können. Ein solches Handbuch ersetzt gut und gerne jahr(zehnt)elange Erfahrung und erspart dem Tester frustrierende und langwierige Trial-und-Error-Prozeduren. Chem Kaner und James Bach sind zwei der international führenden Experten auf dem Gebiet des Software Testing. Sie schöpfen hier aus ihrer insgesamt 30-jährigen Erfahrung. Die einzelnen Lektionen sind nach Themenbereichen gegliedert, wie z.B. Testdesign, Test Management, Teststrategien und Fehleranalyse. Jede Lektion enthält eine Behauptung und eine Erklärung sowie ein Beispiel des entsprechenden Testproblems. "Lessons Learned in Software Testing" ist ein unverzichtbarer Begleiter für jeden Software Tester.