Glossary Of Software Testing

Back to HomePage
[ About Me | Software Testing | Build | Gourmet ]


PLEASE WAIT ....

Alpha

Alpha is the test period during which the product development is nearing completion and usable in a test environment but not necessarily bug-free, minor design changes may still be made.
This test is conducted at developer's location by customer in a controlled environment with Developer.

Automation

The process of writing a set of instructions that are designed, scripted, tested, and checked in by a person, then executed by a machine, to produce results that can be analyzed.

Branch Testing

Branch Testing seeks to ensure that every branch has been executed.Branch coverage can be checked by probes inserted at points in the program that represent arcs from branch points in the flowgraph. This instrumentation suffices for statement coverage as well.This comes under Structural Testing.

Cause-effect graphig

A test case design technique in which test cases are designed by consideration of cause-effect graphs.

Certification

The process of confirming that a system of component compiles with its specified requirements and is acceptable for operational use.

Defect

An incorrect step, process or data definition in a computer program, in common usage defect is referred as an error or a bug or a defect is a variance from a desired product attribute. There are two categories of defects.
1. Defect from product specification.
The product built varies from the product
specified. For example, the specifications may say that a is to be added to b to produce
c. If the algorithm in the built product varies from that specification, it is considered to be
defective.
2. Variance from customer/user expectation.
This variance is something that the user
wanted that is not in the built product, but also was not specified to be included in the built
product. The missing piece may be a specification or requirement, or the method by which the
requirement was implemented may be unsatisfactory.

Defects generally fall into one of the following three categories:

1. Wrong.
The specifications have been implemented incorrectly. This defect is a
variance from customer/user specification.
2. Missing.
A specified or wanted requirment is not in the built product. This can be a
variance from specification, an indication that the specification was not implemented, or a
requirement of the customer identified during or after the product was built.
3. Extra.
A requirement incorporated into the product that was not specified. This is
always a variance from specifications, but may be an attribute desired by the user of the product.

First Customer Ship

 FCS is the period which signifies entry into the final phase of a project. At this point, the product is considered wholly complete and ready for purchase and usage by the customers.

Functional Freeze

A release reaches the Functionality Freeze milestone when the x-functional team gives the approval that the entry criteria for FF has been met. Development releases a build to QA for testing and verification against the entry criteria. All Must/Hopefully features to be included in the release will have been implemented and the functionality of each feature has been either presented in a meeting or documented.

revision

 Third digit in a product number (dot dot release). A change in the revision happens whenever the shipping product rev. Product may be rev for a specific bug fix or to fix some port related issues.(e.g. 2.1.3 to 2.1.4) No new functionality is added in a revision release. Revision releases are not proactively shipped to customers on support.

References:

Testers home SQATesters
Software QA/Test Resource Center
Introducing Software Testing by Louise Tamres
Effective Methods for Software Testing by William E Perry

The Contents and Definations are taken from reliable sources and the links are also provided for them as reference
Back to HomePage
Counter
Hosted by www.Geocities.ws

1