Effective Software Testing: 50 Ways to Improve Your Software Testing

摘要: From the Book: In most organizations, testing program functions as final "quality gate" for an application, allowing or denying move from comfort of software engineering environment into real world. With this role comes a large responsibility: success and possibly organization, can rest on quality product. There are multitude small tasks that must be performed managed by team. So many, in fact, it is tempting to focus purely mechanics pay little attention surrounding required program. Issues such acquisition proper test data, testability application's requirements architecture, appropriate procedure standards documentation, hardware facilities, often addressed very late, if at all, lifecycle. For projects any significant size, scripts tools alone will not suffice, fact experienced testers attest to. The knowledge what constitutes successful, end-to-end effort typically gained through experience. The realization could have been much more effective, certain had earlier project lifecycle, valuable lesson. Of course, point it's usually too late benefit experience. Effective Software Testing provides experienced-based practices key concepts used organization implement successful efficient goal provide distilled collection techniques discussions canbe directly applied personnel improve their products, avoid making costly mistakes oversights. This book details 50 specific points, which contained ten parts roughly follow structure itself concept testing: integrated development process whole effective. Isolating one box "workflow" common mistake avoided. The material varies management related topics, managing changing makeup team, technical aspects ways system integration unit process. Although some pseudo-code given where necessary, content tied particular technology application platform. It important note there factors outside scope heavily factor failure project. complete ensure effort, also deal with issues relating business case, budgets, schedules, culture organization. In cases, these odds needs effective environment. recommendations assume capable adapting, providing support necessary its success. Organization This organized separate chapters span 10 coverage areas. The selected best broken down sequence parallels phases life cycle. reader approach sequentially, meaning chapter-by-chapter part-by-part, simply refer when gain information understanding problem. part, each chapter stands own, although references other chapters, books, additional information. Part I describes requirement phase considerations effort. It all stakeholders, including involved informed changes. addition, basing cases importance team's involvement during cannot understated; thorough obtained. Part II covers test-planning activities, strategy creating environments, itself. Planning take place early possible cycle, lead times considered implementing successfully. Early planning allows schedules budgets estimated, approved, then incorporated overall plan. III focuses A team mixture domain knowledge, well structured concise division roles responsibilities. IV discusses architectural under test. Often overlooked, testable, data enable gray-box defect diagnosis. Part V design procedures, creation documentation tests, discussion techniques. As further refined over time iterations, so procedures include new modified functions. Part VI examines use developer strategy. Unit implementation result gains quality. If done properly, later successful. There difference, however, between casual, ad-hoc based problem, structured, repeatable system. Part VII explains automated tool issues, types project, build vs. buy decision, concerns deciding right numerous available throughout cycle described here. custom covered. VIII testing. capture/playback, harnesses, regression tests described. Part IX non-functional application. Items discussed performance, security, usability, compatibility, concurrency testing. Part X execution way track defects, gather metrics. Audience The target audience Quality Assurance professionals, managers. Much presented value managers developers looking increase