Cargando…
Software Test Design Write Comprehensive Test Plans to Uncover Critical Bugs in Web, Desktop, and Mobile Apps /
A guide to writing comprehensive test plans covering exploratory testing and feature specification; black and white box testing; security, usability, and maintainability; and load and stress testing Key Features Cover all key forms of testing for modern applications systematically Understand anti-pa...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Birmingham :
Packt Publishing, Limited,
2022.
|
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
MARC
| LEADER | 00000cam a22000007a 4500 | ||
|---|---|---|---|
| 001 | OR_on1351749922 | ||
| 003 | OCoLC | ||
| 005 | 20231017213018.0 | ||
| 006 | m o d | ||
| 007 | cr cnu---unuuu | ||
| 008 | 221203s2022 enk o 000 0 eng d | ||
| 040 | |a EBLCP |b eng |c EBLCP |d ORMDA |d OCLCF |d N$T | ||
| 020 | |a 1804614734 | ||
| 020 | |a 9781804614730 |q (electronic bk.) | ||
| 029 | 1 | |a AU@ |b 000073244386 | |
| 035 | |a (OCoLC)1351749922 | ||
| 037 | |a 9781804612569 |b O'Reilly Media | ||
| 050 | 4 | |a QA76.76.T48 | |
| 082 | 0 | 4 | |a 005.1/4 |2 23/eng/20221213 |
| 049 | |a UAMI | ||
| 100 | 1 | |a Amey, Simon, |e author. | |
| 245 | 1 | 0 | |a Software Test Design |h [electronic resource] : |b Write Comprehensive Test Plans to Uncover Critical Bugs in Web, Desktop, and Mobile Apps / |c Simon Amey. |
| 260 | |a Birmingham : |b Packt Publishing, Limited, |c 2022. | ||
| 300 | |a 1 online resource (426 p.) | ||
| 500 | |a Description based upon print version of record. | ||
| 505 | 0 | |a Cover -- Title Page -- Copyright and Credits -- Contributors -- Table of Contents -- Preface -- Part 1 -- Preparing to Test -- Chapter 1: Making the Most of Exploratory Testing -- What is exploratory testing? -- Advantages, disadvantages, and alternatives -- Understanding when testing should begin -- Understanding the test activities -- The spiral model of test improvement -- Identifying if a feature is ready for testing -- Performing the first test -- Mapping out new features -- Using your naivety while testing -- Running complete exploratory testing -- Using exploratory testing by necessity | |
| 505 | 8 | |a Checking exploratory test results -- Using curiosity in testing -- Summary -- Chapter 2: Writing Great Feature Specifications -- Advantages, disadvantages, and alternatives to feature specifications -- Alternatives to feature specifications -- Improving the handover from the product owner -- Understanding the requirements format -- Numbering -- Sections -- Requirement priority -- Improving requirement statements -- Specific -- Be precisely wrong rather than vaguely right -- Measurable -- Agreed -- Realistic -- Complete -- Independent -- Consistent -- Round-up of requirement statement improvements | |
| 505 | 8 | |a Improving requirement content -- Keep it obvious, cover everything -- Version requirements -- Describing configuration -- Completing the specification -- Functional test requirements -- Error cases -- User experience specification -- Security test requirements -- Maintainability -- Non-functional tests -- Documentation -- Round-up of specification sections -- The first draft of a feature specification -- Turning a specification into a test plan -- Countering arguments against specifications -- "This feature is too small to be specified" -- "We don't know that behavior" | |
| 505 | 8 | |a "We don't have time to write a specification" -- Summary -- Chapter 3: How to Run Successful Specification Reviews -- Why do we need a specification review? -- Advantages, disadvantages, and alternatives of specification review meetings -- Advantages of specification review meetings -- Disadvantages of specification review meetings -- Alternatives to specification review meetings -- Inviting the right people -- Scheduling the meeting -- Running the meeting -- Fixing incorrect requirements -- Opening the black box -- Setting a good tone for the meeting -- Prioritizing requirement testing | |
| 505 | 8 | |a Review meeting checklist -- Summary -- Chapter 4: Test Types, Cases, and Environments -- Understanding different levels of testing -- Test level examples -- Test ordering -- The testing pyramid -- Advantages and disadvantages of unit tests -- Advantages and disadvantages of integration tests -- Advantages and disadvantages of system tests -- Defining test cases -- Prescriptive and descriptive test steps -- Evaluating different test environments -- Using temporary test environments -- Using permanent staging areas -- Setting the correct version, configuration, and environment | |
| 500 | |a Performing systematic testing | ||
| 520 | |a A guide to writing comprehensive test plans covering exploratory testing and feature specification; black and white box testing; security, usability, and maintainability; and load and stress testing Key Features Cover all key forms of testing for modern applications systematically Understand anti-patterns and pitfalls in system design with the help of practical examples Learn the strengths and weaknesses of different forms of testing and how to combine them effectively Book Description Software Test Design details best practices for testing software applications and writing comprehensive test plans. Written by an expert with over twenty years of experience in the high-tech industry, this guide will provide you with training and practical examples to improve your testing skills. Thorough testing requires a thorough understanding of the functionality under test, informed by exploratory testing and described by a detailed functional specification. This book is divided into three sections, the first of which will describe how best to complete those tasks to start testing from a solid foundation. Armed with the feature specification, functional testing verifies the visible behavior of features by identifying equivalence partitions, boundary values, and other key test conditions. This section explores techniques such as black- and white-box testing, trying error cases, finding security weaknesses, improving the user experience, and how to maintain your product in the long term. The final section describes how best to test the limits of your application. How does it behave under failure conditions and can it recover? What is the maximum load it can sustain? And how does it respond when overloaded? By the end of this book, you will know how to write detailed test plans to improve the quality of your software applications. What you will learn Understand how to investigate new features using exploratory testing Discover how to write clear, detailed feature specifi cations Explore systematic test techniques such as equivalence partitioning Understand the strengths and weaknesses of black- and white-box testing Recognize the importance of security, usability, and maintainability testing Verify application resilience by running destructive tests Run load and stress tests to measure system performance Who this book is for This book is for anyone testing software projects for mobile, web, or desktop applications. That includes Dedicated QA engineers managing software quality, Test and test automation engineers writing formal test plans, Test and QA managers running teams responsible for testing, Product owners responsible for product delivery, and Developers who want to improve the testing of their code. | ||
| 590 | |a O'Reilly |b O'Reilly Online Learning: Academic/Public Library Edition | ||
| 650 | 0 | |a Computer software |x Testing. | |
| 650 | 7 | |a Computer software |x Testing. |2 fast |0 (OCoLC)fst00872601 | |
| 776 | 0 | 8 | |i Print version: |a Amey, Simon |t Software Test Design |d Birmingham : Packt Publishing, Limited,c2022 |
| 856 | 4 | 0 | |u https://learning.oreilly.com/library/view/~/9781804612569/?ar |z Texto completo (Requiere registro previo con correo institucional) |
| 938 | |a ProQuest Ebook Central |b EBLB |n EBL30256355 | ||
| 938 | |a ProQuest Ebook Central |b EBLB |n EBL30256355 | ||
| 938 | |a EBSCOhost |b EBSC |n 3464648 | ||
| 994 | |a 92 |b IZTAP | ||