System Under Test definition

System Under Test means the software applications and physical and/or cloud computing resources that you choose to configure as a set in the Software as the applicable target of use.
View Source

Examples of System Under Test in a sentence

  • Before presenting a general measurement procedure, the docu- ment specifies measurement conditions by introducing recom- mendation on configuration of the System Under Test (SUT), the environment conditions of the test and the measurement instruments.

  • An “abstract test architecture” shows interconnections between components in the System Under Test (SUT) in an abstract form.

  • In this context, the model of the system is used as a container of data useful to derive information about the System Under Test (SUT), its boundary and to design test vectors  Test bench setup: information is extracted from the model in order to support a semi- automatic setup of a test experiment and HW test plant.

  • Two players, the tester and the System Under Test (SUT), play on a state space consisting of an automaton A = (Q, T, q0).

  • It relates to a process of test generation based on the model of a System Under Test (SUT) [30].

  • Examples of technical narrative include identification, and capabilities gap analysis, test technology integration, and System Under Test integration, test technology accreditation, provision of adequate time for travel, set-up and training, timelines for task accomplishment.

  • Model-Based Testing (MBT) is a form of black-box testing where the software being tested, called System Under Test (SUT), is tested for correctness with respect to a model.

  • The generation of test scenarios using models of the SUT (System Under Test) in section 4.

  • This document is about Model Based Testing in eDIANA and different dimensions are considered: The generation of test scenarios using models of the SUT (System Under Test); test modelling which is concerned with modelling testing structure, test behaviour and testing artefacts; the traceability between test scenarios and requirements and variability management in testing.

  • In testing, ex- periments are conducted with a System Under Test (SUT) to determine whether it behaves as expected.

Related to System Under Test

  • RDDS test Means one query sent to a particular “IP address” of one of the servers of one of the RDDS services. Queries shall be about existing objects in the Registry System and the responses must contain the corresponding information otherwise the query will be considered unanswered. Queries with an RTT 5 times higher than the corresponding SLR will be considered as unanswered. The possible results to an RDDS test are: a number in milliseconds corresponding to the RTT or undefined/unanswered.

  • EPP test Means one EPP command sent to a particular “IP address” for one of the EPP servers. Query and transform commands, with the exception of “create”, shall be about existing objects in the Registry System. The response shall include appropriate data from the Registry System. The possible results to an EPP test are: a number in milliseconds corresponding to the “EPP command RTT” or undefined/unanswered.

  • DNS test Means one non-­‐recursive DNS query sent to a particular “IP address” (via UDP or TCP). If DNSSEC is offered in the queried DNS zone, for a query to be considered answered, the signatures must be positively verified against a corresponding DS record published in the parent zone or, if the parent is not signed, against a statically configured Trust Anchor. The answer to the query must contain the corresponding information from the Registry System, otherwise the query will be considered unanswered. A query with a “DNS resolution RTT” 5 times higher than the corresponding SLR, will be considered unanswered. The possible results to a DNS test are: a number in milliseconds corresponding to the “DNS resolution RTT” or, undefined/unanswered.

  • Start-Up Testing means the completion of applicable required factory and start-up tests as set forth in Exhibit C.

  • S&P CDO Monitor Test A test that will be satisfied on any date of determination (following receipt, at any time on or after the S&P CDO Monitor Election Date, by the Issuer and the Collateral Administrator of the Class Break-even Default Rates for each S&P CDO Monitor input file (in accordance with the definition of “Class Break-even Default Rate”)) if, after giving effect to a proposed sale or purchase of an additional Collateral Obligation, the Class Default Differential of the Highest Ranking Class of the Proposed Portfolio is positive. The S&P CDO Monitor Test will be considered to be improved if the Class Default Differential of the Proposed Portfolio that is not positive is greater than the corresponding Class Default Differential of the Current Portfolio.