Ensure your web APIs are consistent and bug-free by implementing an automated testing process. In Testing Web APIs you will: Design and implement a web API testing strategy Set up a test automation suite Learn contract testing with Pact Facilitate collaborative discussions to test web API designs Perform exploratory tests Experiment safely in a downloadable API sandbox environment Testing Web APIs teaches you to plan and implement the perfect testing strategy for your web APIs. In it, you’ll explore dozens of different testing activities to help you develop a custom testing regime for your projects. This practical book demystifies abstract strategic concepts by applying them to common API testing scenarios, revealing how these complex ideas work in the real world. You’ll learn to take a risk-driven approach to API testing, and build a strategy that goes beyond the basics of code and requirements coverage. Your whole team will soon be involved in ensuring quality! About the technology Web APIs are the public face of your application, and they need to be perfect. Implementing an automated testing program is the best way to ensure that your web APIs are production ready. About the book Testing Web APIs is a unique and practical guide, from the initial design of your testing suite through techniques for documentation, implementation, and delivery of consistently excellent APIs. You’ll see a wide range of testing techniques, from exploratory to live testing of production code, and how to save time with automation using industry-standard tools. This book helps take the hassle out of API testing. What's inside Design and implement a web API testing strategy Set up a test automation suite Contract testing with Pact Hands-on practice in the downloadable API sandbox About the reader For dedicated software QA and testers, or experienced developers. Examples in Java. About the author Mark Winteringham is the OpsBoss at Ministry of Testing, where he teaches many aspects of software testing. Table of Contents PART 1 THE VALUE OF WEB API TESTING 1 Why and how we test web APIs 2 Beginning our testing journey 3 Quality and risk PART 2 BEGINNING OUR TEST STRATEGY 4 Testing API designs 5 Exploratory testing APIs 6 Automating web API tests 7 Establishing and implementing a testing strategy PART 3 EXPANDING OUR TEST STRATEGY 8 Advanced web API automation 9 Contract testing 10 Performance testing 11 Security testing 12 Testing in production

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.

This book will help you write better stories, spot and fix common issues, split stories so that they are smaller but still valuable, and deal with difficult stuff like crosscutting concerns, long-term effects and non-functional requirements. Above all, this book will help you achieve the promise of agile and iterative delivery: to ensure that the right stuff gets delivered through productive discussions between delivery team members and business stakeholders. Who is this book for? This is a book for anyone working in an iterative delivery environment, doing planning with user stories. The ideas in this book are useful both to people relatively new to user stories and those who have been working with them for years. People who work in software delivery, regardless of their role, will find plenty of tips for engaging stakeholders better and structuring iterative plans more effectively. Business stakeholders working with software teams will discover how to provide better information to their delivery groups, how to set better priorities and how to outrun the competition by achieving more with less software. What's inside? Unsurprisingly, the book contains exactly fifty ideas. They are grouped into five major parts: - Creating stories: This part deals with capturing information about stories before they get accepted into the delivery pipeline. You'll find ideas about what kind of information to note down on story cards and how to quickly spot potential problems. - Planning with stories: This part contains ideas that will help you manage the big-picture view, set milestones and organise long-term work. - Discussing stories: User stories are all about effective conversations, and this part contains ideas to improve discussions between delivery teams and business stakeholders. You'll find out how to discover hidden assumptions and how to facilitate effective conversations to ensure shared understanding. - Splitting stories: The ideas in this part will help you deal with large and difficult stories, offering several strategies for dividing them into smaller chunks that will help you learn fast and deliver value quickly. - Managing iterative delivery: This part contains ideas that will help you work with user stories in the short and mid term, manage capacity, prioritise and reduce scope to achieve the most with the least software. About the authors: Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko's book Specification by Example was awarded the #2 spot on the top 100 agile books for 2012 and won the Jolt Award for the best book of 2012. In 2011, he was voted by peers as the most influential agile testing professional, and his blog won the UK agile award for the best online publication in 2010. David Evans is a consultant, coach and trainer specialising in the field of Agile Quality. David helps organisations with strategic process improvement and coaches teams on effective agile practice. He is regularly in demand as a conference speaker and has had several articles published in international journals.

2012 Jolt Award finalist! Pioneering the Future of Software Test Do you need to get it right, too? Then, learn from Google. Legendary testing expert James Whittaker, until recently a Google testing leader, and two top Google experts reveal exactly how Google tests software, offering brand-new best practices you can use even if you’re not quite Google’s size...yet! Breakthrough Techniques You Can Actually Use Discover 100% practical, amazingly scalable techniques for analyzing risk and planning tests...thinking like real users...implementing exploratory, black box, white box, and acceptance testing...getting usable feedback...tracking issues...choosing and creating tools...testing “Docs & Mocks,” interfaces, classes, modules, libraries, binaries, services, and infrastructure...reviewing code and refactoring...using test hooks, presubmit scripts, queues, continuous builds, and more. With these techniques, you can transform testing from a bottleneck into an accelerator–and make your whole organization more productive!

A practical guide to effective business model testing 7 out of 10 new products fail to deliver on expectations. Testing Business Ideas aims to reverse that statistic. In the tradition of Alex Osterwalder’s global bestseller Business Model Generation, this practical guide contains a library of hands-on techniques for rapidly testing new business ideas. Testing Business Ideas explains how systematically testing business ideas dramatically reduces the risk and increases the likelihood of success for any new venture or business project. It builds on the internationally popular Business Model Canvas and Value Proposition Canvas by integrating Assumptions Mapping and other powerful lean startup-style experiments. Testing Business Ideas uses an engaging 4-color format to: Increase the success of any venture and decrease the risk of wasting time, money, and resources on bad ideas Close the knowledge gap between strategy and experimentation/validation Identify and test your key business assumptions with the Business Model Canvas and Value Proposition Canvas A definitive field guide to business model testing, this book features practical tips for making major decisions that are not based on intuition and guesses. Testing Business Ideas shows leaders how to encourage an experimentation mindset within their organization and make experimentation a continuous, repeatable process.

This volume focuses on the human exposures and medical effects studies in the SemipaiatinskJ Altai region of Siberia that were a consequence of the radioactive fallout from nuclear test explosions that took place at the Semipalatinsk Test Site of the former Soviet Union. It contains a detailed account of a NATO Advanced Research Workshop (ARW) devoted to the subject, and a selection of the papers presented. The title of the ARW was "Long-term Consequences of Nuclear Tests for the Environment and Population Health (SemipaiatinskJAltai Case Studies)". The estimated exposures to large numbers of people in the Altai lie in an important dose rate and dose domain. Hence the research reported herein provides new and unique information on the effects of radiation on humans. Also emphasized at the ARW were studies involving fallout from the Pacific Island tests of the U. S. A . . There have been over 2300 nuclear weapon test explosions to date. More than 500 took place in the atmosphere and outer space; the remainder were underground. The atmospheric tests comprise the largest source of anthropogenic radioactivity released into the earth's atmosphere to date. The vast majority, in number and yield, were carried out by the former Soviet Union (FSU) and the United States. Each superpower maintained two primary test sites, one continental primarily for small yield tests, and the other more remote for larger yield tests. For the U. S. A.