Jeff Carollo

James A. Whittaker

Jason Arbon

Describes the techniques Google uses to test their software, and offers similiar techniques for analyzing risk and planning tests, allowing an Internet company to become more productive.

How Google Tests Software

[tips, tricks, tours, and techniques to guide test design]

Exploratory software testing

Career Superpowers

Mike Andrews

Rigorously test and improve the security of all your Web software! It’s as certain as death and taxes: hackers will mercilessly attack your Web sites, applications, and services. If you’re vulnerable, you’d better discover these attacks yourself, before the black hats do. Now, there’s a definitive, hands-on guide to security-testing any Web-based software: How to Break Web Software. In this book, two renowned experts address every category of Web software exploit: attacks on clients, servers, state, user inputs, and more. You’ll master powerful attack tools and techniques as you uncover dozens of crucial, widely exploited flaws in Web architecture and coding. The authors reveal where to look for potential threats and attack vectors, how to rigorously test for each of them, and how to mitigate the problems you find. Coverage includes · Client vulnerabilities, including attacks on client-side validation · State-based attacks: hidden fields, CGI parameters, cookie poisoning, URL jumping, and session hijacking · Attacks on user-supplied inputs: cross-site scripting, SQL injection, and directory traversal · Language- and technology-based attacks: buffer overflows, canonicalization, and NULL string attacks · Server attacks: SQL Injection with stored procedures, command injection, and server fingerprinting · Cryptography, privacy, and attacks on Web services Your Web software is mission-critical–it can’t be compromised. Whether you’re a developer, tester, QA specialist, or IT manager, this book will help you protect that software–systematically.

Functional and Security Testing of Web Applications and Web Services

How to Break Web Software

Как тестируют в Google

CD-ROM contains: Canned HEAT v.2.0 -- Holodeck Lite v. 1.0.

A Practical Guide to Testing

How to Break Software

Herbert H. Thompson

Learn how to destroy security bugs in your software from a tester's point-of-view. It focuses your security test on the common vulnerabilities--ther user interface, software dependencies, design, process and memory. (Midwest)

Effective Techniques for Security Testing

How to Break Software Security

Creativity is the one universal ingredient of success. Creatives report higher job satisfaction and lead more fulfilling lives than any other class of people. And yet our school curricula focus on rote learning and test taking at the expense of creativity, problem-solving and higher-order thinking. In this book, Microsoft Distinguished Engineer James Whittaker shows you how to develop your creative mind and use it as the fulcrum of a lifestyle where creativity doesn't just happen, it becomes the default case for everything you do in work and life. Learn to supercharge your creativity to make your work more interesting and your life more exciting. In this book lies the key to: Learning faster and retaining knowledge better. Discovering and nurturing your creative biorhythms. Becoming an expert in your field. Turning your creativity on at will. This book is based on the hugely popular course by the same title and is written by a serial creative who wants nothing more than to expand the creative class with people just like you.

Developing Your Creative Self

The 7 Stages of Creativity

How to Find and Fix the Killer Software Bugs that Evade Conventional Testing In Exploratory Software Testing, renowned software testing expert James Whittaker reveals the real causes of today’s most serious, well-hidden software bugs--and introduces powerful new “exploratory” techniques for finding and correcting them. Drawing on nearly two decades of experience working at the cutting edge of testing with Google, Microsoft, and other top software organizations, Whittaker introduces innovative new processes for manual testing that are repeatable, prescriptive, teachable, and extremely effective. Whittaker defines both in-the-small techniques for individual testers and in-the-large techniques to supercharge test teams. He also introduces a hybrid strategy for injecting exploratory concepts into traditional scripted testing. You’ll learn when to use each, and how to use them all successfully. Concise, entertaining, and actionable, this book introduces robust techniques that have been used extensively by real testers on shipping software, illuminating their actual experiences with these techniques, and the results they’ve achieved. Writing for testers, QA specialists, developers, program managers, and architects alike, Whittaker answers crucial questions such as: • Why do some bugs remain invisible to automated testing--and how can I uncover them? • What techniques will help me consistently discover and eliminate “show stopper” bugs? • How do I make manual testing more effective--and less boring and unpleasant? • What’s the most effective high-level test strategy for each project? • Which inputs should I test when I can’t test them all? • Which test cases will provide the best feature coverage? • How can I get better results by combining exploratory testing with traditional script or scenario-based testing? • How do I reflect feedback from the development process, such as code changes?

James A. Whittaker

About

Books

Join the club