软件测试术语表[1] 软件测试
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。