The Process of software testing part three

What's a 'test plan'?

A software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product.

The completed document will help people outside the test group understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. The following are some of the items that might be included in a test plan, depending on the particular project:

  1. Title
  2. Identification of software including version/release numbers
  3. Revision history of document including authors, dates, approvals
  4. Table of Contents
  5. Purpose of document, intended audience
  6. Objective of testing effort
  7. Software product overview
  8. Relevant related document list, such as requirements, design documents, other test plans, etc.
  9. Relevant standards or legal requirements
  10. Traceability requirements
  11. Relevant naming conventions and identifier conventions
  12. Overall software project organization and personnel/contact-info/responsibilties
  13. Test organization and personnel/contact-info/responsibilities
  14. Assumptions and dependencies
  15. Project risk analysis
  16. Testing priorities and focus
  17. Scope and limitations of testing
  18. Test outline - a decomposition of the test approach by test type, feature, functionality, process, system, module, etc. as applicable
  19. Outline of data input equivalence classes, boundary value analysis, error classes
  20. Test environment - hardware, operating systems, other required software, data configurations, interfaces to other systems
Test environment setup and configuration issues
  1. Test data setup requirements
  2. Database setup requirements
  3. Outline of system-logging/error-logging/other capabilities, and tools such as screen capture software, that will be used to help describe and report bugs
  4. Discussion of any specialized software or hardware tools that will be used by testers to help track the cause or source of bugs
  5. Test automation - justification and overview
  6. Test tools to be used, including versions, patches, etc.
Test script/test code maintenance processes and version control

  1. Problem tracking and resolution - tools and processes
  2. Project test metrics to be used
  3. Reporting requirements and testing deliverables
  4. Software entrance and exit criteria
  5. Initial sanity testing period and criteria
  6. Test suspension and restart criteria
  7. Personnel allocation
  8. Personnel pre-training needs
  9. Test site/location
  10. Outside test organizations to be utilized and their purpose, responsibilties, deliverables, contact persons, and coordination issues
  11. Relevant proprietary, classified, security, and licensing issues.
  12. Open issues
SOFTWARE QUALITY ASSURANCE AND CONTROL

SOFTWARE QUALITY AND COST ASPECT

STABLE PROCESS OF SOFTWARE TESTING

STABLE PROCESS OF SOFTWARE TESTING PART TWO


DEFECTS IN SOFTWARE TESTING

REDUCTION OF DEFECTS IN SOFTWARE TESTING

SOFTWARE TESTING AND EFFECTING FACTORS

SCOPE OF SOFTWARE TESTING

TESTING LIFE CYCLE PART ONE

TESTING LIFE CYCLE PART TWO

TESTING LIFE CYCLE PART THREE

SOFTWARE TESTING AND CONSTRAINTS WITH IN IT

TESTING CONSTRAINTS PART TWO

LIFE CYCLE TESTING

TEST METRICS

Independent Software Testing

Test Process

Testing verification and validation

Functional and structural testing

Static and dynamic testing

V model testing

Eleven steps of V model testing

Structural testing

Execution testing technique

Recovery Testing technique


Operation testing technique


Compliance software testing technique

Security testing technique

No comments:

Post a Comment