軟件測試術語表

軟件測試術語表  軟件測試工程師

acceptance testing: Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component.
接收測試：用來使一個用戶、客戶或者其它的權威機構決定是否接收一個系統或者組件的測試。 actual outcome: The behaviour actually produced when the object is tested under specified conditions.實際輸出：被測對象在特定條件下實際產生的行為。

ad hoc testing: Testing carried out using no recognised test case design technique.
探索式測試：不使用可識別的測試用例設計技術所進行的測試。

alpha testing: Simulated or actual operational testing at an in-house site not otherwise involved with the software developers.
α測試：在軟件開發人員缺席的情況下內部做的模擬的或者實際的操作性測試。

arc testing: A test case design technique for a component in which test cases are designed to execute branch outcomes.
分支測試：一種針對組件的測試用例設計技術，通過分支覆蓋來進行測試用例設計。 Backus-Naur form: A meta language used to formally describe the syntax of a language.
Backus-Naur 形式：一種用來從形式上描述一種語言的語法的元語言。 basic block: A sequence of one or more consecutive, executable statements containing no branches.
基本塊：一個由不包含任何分支的一個或者多個連續的、可執行的指令組成的序列。

basis test set: A set of test cases derived from the code logic which ensure that \% branch coverage is achieved.
基本測試集：基于代碼的邏輯結構且保證一定的分支覆蓋率的測試用例的集合。

bebugging: The process of intentionally adding known faults to those already in a computer program for the purpose of monitoring the rate of detection and removal, and estimating the number of faults remaining in the program.
錯誤撒播：通過在計算機程序中人為的引入已知的錯誤來監測發現和消除錯誤的比率、估計程序中剩余的錯誤數的方法。

      behavior: The combination of input values and preconditions and the required response for a function of a system. The full specification of a function would normally comprise one or more behaviors.
行為：系統中一個功能的輸入值、前提條件和必要的響應的集合。一個功能的完整說明需要包含一個或多個行為。

beta testing: Operational testing at a site not otherwise involved with the software developers.
β測試：在軟件開發人員缺席的情況下做的操作性測試。

big-bang testing: Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
非漸增式測試：在單獨測試所有構成系統的組件之前不進行任何額外測試的集成測試。

black box testing: Test case selection that is based on an analysis of the specification of the component without reference to its internal workings.
黑盒測試：不涉及組件的內部工作情況而只根據組件規格說明來選擇測試用例的測試方法。

bottom-up testing: An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.
自底向上的測試：集成測試時先測試最低層的組件，然后用最低層的組件來幫助測試更高層組件的一種方法。這個過程一直重復進行直到最高層的組件被測試到。

boundary value: An input value or output value which is on the boundary between equivalence classes, or an incremental distance either side of the boundary.
邊界值：位于兩個等價類之間的輸入或輸出值，或者邊界附近的值。

boundary value analysis: A test case design technique for a component in which test cases are designed which include representatives of boundary values.
邊界值分析：為被測組件設計包含典型邊界值的測試用例的一種測試用例設計方法。

boundary value coverage: The percentage of boundary values of the component's equivalence classes which have been exercised by a test case suite.
邊界值覆蓋：被一組測試用例覆蓋到的被測組件等價類的邊界值占所有邊界值的百分比。

原文轉自：http://www.anti-gravitydesign.com