Web page element that should to be filled with valid data (e.g., text box) or which value must be selected (e.g., value in drop-down menu) to be able to proceed to the next Web page. For example, in the “Email” field, valid data must have one and only one “@” character. Null input is always considered to be invalid for the required field.

(Also called “certification testing”). A quick test to determine if software is ready for release. Acceptance testing follows regression testing. As a rule, test documentation for acceptance testing comes in the form of a checklist. Related articles: Testing And Bug Fixes, What To Do If You Are The First Test Engineer At A Software Start-Up

Testing done without any preparation. Doing ad hoc testing, the tester just follows his or her heart to try to find bugs. Related articles: Ad hoc testing.

Testing done before a release. When you hear “alpha testing,” it refers to when the testing is done, not how the testing was done. As a rule, alpha testing is done inside the company. In some cases, alpha testing is outsourced to other companies. Related articles: Alpha testing. Also see Beta Testing

(in BTS) The list of persons who should get emails containing: – Notification that the bug has been filed – Updates about changes to the bug Related article: Also Notify in Bug Tracking System.

The version of the application formatted according to the convention accepted at the company. For example, at ShareLane we have this convention: <major release number>.<minor release number>-<build number>/<DB version number> e.g., 1.0-23/34 Related article: Release.

(in BTS) Alias of the person who assigned the bug to its current owner. Related article: Assigned by in Bug Tracking System.

(in BTS) Alias of the current bug owner. Related article: Assigned to in Bug Tracking System.

(in BTS) File (usually an image) uploaded as an illustration to the bug. Related article: Attachment in Bug Tracking System.