A simple glossary of Software Testing
Ad Hoc Testing
Goal oriented passing through the product. Sometimes to prove or disprove a notion of how the product will behave.
The part of the Test Phase of the PLC where code is complete and the product has achieved a degree of stability. The product is fully testable (determined by QA). All functionality has been implemented and QA has finished the implementation of the test plans/cases. Ideally, this when development feels the product is ready to be shipped.
Creation of individual tests created to run without direct tester intervention.
The part of the Test Phase of the PLC where integration testing plans are finished, depth testing coverage goals met; Ideally, QA says product is ready to ship. The product is stable enough for external testing (determined by QA).
Black Box Test
Tests in which the software under test is treated as a black box. You can't "see" into it. The test provides inputs and responds to outputs without considering how the software works.
Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).
Matrix tests which generally cover all product components and functions on an individual basis. These are usually the first automated tests available after the functional specifications have been completed and test plans have been drafted.
Generally a good thing to do after eating garlic and before going out into public. Or you may have to take a breath test if you're DUI.
A phenomenon with an understanding of why it happened.
Phase of the PLC where functionality is coded in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.
When development has finished all new functional code. This is when development is in a "bug fixing" stage.
Phase of the PLC where development is coding product to meet Functional/Architectural Specifications. QA develops test tools and test cases during this phase.
Tests that check for compatibility of other software or hardware with the software being tested.
Phase of the PLC where an idea for a new product is developed and a preliminary definition of the product is established. Research plans should be put in place and an initial analysis of the competition should be completed. The main goal of this phase is to determine product viability and obtain funding for further research.
Shows which functions (i.e., GUI and C code level) have been touched and which have not.
Verification of data to assure that it is still correct.
To search for and eliminate malfunctioning elements or errors in the software.
See Design Phase.
This is when a component of a product is dependent on an outside group. The delivery of the product or the reaching a certain milestone is affected.
Encompasses Integration testing, real world testing, combinatorial testing, Interoperability and compatibility testing.
Phase of the PLC where functions of the product are written down. Features and requirements are defined in this phase. Each department develops their departments' plan and resource requirements for the product during this phase.
A major update to a product.
A bug that no one wants to admit to.
The center of interest or activity. In software, focus refers to the area of the screen where the insertion point is active.
Phase of the PLC defining modules.
Their implementation requirements and approach, and exposed API. Each function is specified here. This includes the expected results of each function.
See Green Master.
Green Master (GM)
Phase of the PLC where the certification stage begins. All bugs, regressed against the product, must pass. Every build is a release candidate (determined by development).
Graphical User Interface.
Depth testing which covers groups of functions at the subsystem level.
Tests that verify operability between software and hardware.
Load tests study the behavior of the program when it is working at its limits. Types of load tests are Volume tests, Stress tests, and Storage tests.
This term refers to making software specifically designed for a specific locality.
A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.
Events in the Product Life Cycle which define particular goals.
Test that measures how long it takes to do a function.
A flaw without an understanding.
Product Life Cycle - see Software Product Life Cycle.
Pre-build 1; product definition phase. (Functional Specification may still be in process of being created).
Product Life Cycle
The stages a product goes through.
from conception to completion. Phases of product development includes: Definition Phase, Functional/Architectural Specification Phase, Coding Phase, Code Complete Phase, Alpha, Beta, Zero Bug Build Phase, Green Master Phase, STM, and Maintenance/Inline Phase.
Phase of the PLC where the product must be defined with a prioritized feature list and system and compatibility requirements.
A general test plan given at the macro level which defines the activities of the test team through the stages of the Product Life Cycle.
Real World Testing
Integration testing which attempt to create environments which mirror how the product will be used in the "real world".
Retesting bugs in the system which had been identified as fixed, usually starting from Alpha on.
People, software, hardware, tools, etc. that have unique qualities and talents that can be utilized for a purpose.
Something that could potentially contribute to failing to reach a milestone.
See Ship to Manufacturing.
Test how memory and space is used by the program, either in resident memory or on disk.
Tests the program's response to peak activity conditions.
A test that works in harmony with other tests. The timing is such that both tests work together, but yet independently.
A breakdown of each functional area into an individual test. These can be automated or done manually.
Phase of the PLC where the entire product is tested, both internally and externally. Alpha and
Beta Tests occur during this phase.
A specific plan that breakdown testing approaches on a functional area basis.
A set of test cases.
The degree to which the intended target users can accomplish their intended goals.
Test the largest tasks a program can deal with.
White Box Test
It is used to test areas that cannot be reached from a black box level. (Sometimes called Glass
Zero Bug Build
Phase of the PLC where the product has stabilized in terms of bugs found and fixed. Development is fixing bugs as fast as they are found, the net resulting in zero bugs on a daily basis. This is usually determined when after a few builds have passed. This is the preliminary stage before Green Master.