Software Test Design Write Comprehensive Test Plans to Uncover Critical Bugs in Web, Desktop, and Mobile Apps /

Mostrar otras versiones (2)

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...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Amey, Simon (Autor)
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Birmingham : Packt Publishing, Limited, 2022.
Temas:
Computer software > Testing.
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)
Tabla de Contenidos:
  • 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
  • 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
  • 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"
  • "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
  • 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

Ejemplares similares