Software Testing Definitions

General Testing Process


Obtain requirements, functional design, and internal design specifications and other necessary documents.
Obtain budget and schedule requirements.Determine project-related personnel and their responsibilities, reporting requirements, required standards and processes (such as release processes, change processes, etc.)
Identify application's higher-risk aspects, set priorities, and determine scope and limitations of tests.
Determine test approaches and methods - unit, integration, functional, system, load, usability tests, etc.
Determine test environment requirements (hardware, software, communications, etc.)
Determine testware requirements (record/playback tools, coverage analyzers, test tracking, problem/bug tracking, etc.)
Determine test input data requirements
Identify tasks, those responsible for tasks, and labor requirements
Set schedule estimates, timelines, milestones
Determine input equivalence classes, boundary value analyses, error classes
Prepare test plan document and have needed reviews/approvals
Write test cases
Have needed reviews/inspections/approvals of test cases
Prepare test environment and testware, obtain needed user manuals/reference documents/configuration guides/installation guides, set up test tracking processes, set up logging and archiving processes, set up or obtain test input data
Obtain and install software releases
Perform tests
Evaluate and report results
Track problems/bugs and fixes
Retest as needed
Maintain and update test plans, test cases, test environment, and testware through life cycle

Types of Non-functional Testing:

• Performance Testing
• GUI Testing
• Recovery Testing
• Memory Management
• Reliability Testing
• Maintainability
• Configuration Testing

Defect age

Defect age is nothing but the time gap between bug raised and bug resolved. Defect age analysis suggests how quickly defects are resolved by category. Defect age reports are a type of defect distribution report that shows how long a defect has been in a particular state, such as Open.

Build Interval Period:

The time gap between the two consecutive build versions is called Build Interval Period.

Risk Management:

An organized process to identify what can go wrong, to quantify and access associated risks and to implement and control the appropriate approach for preventing or handling each risk identified.
Risk Analysis is the process of evaluating risks, threats, controls and vulnerabilities.
Risk: Potential loss to organization
Vulnerability:This is a design, implementation and operational flaw.
Threat:This exploits vulnerability and triggers risks to become loss.