<def-root>A <fen>Tester</fen> uses a concrete or conceptual <fen>Product</fen> in order to determine either whether it works or to find out how well or in which manner it works. The <fen>Tester</fen> may have particular <fen>Unwanted_characteristics</fen> in mind that they are specifically looking for. The operational test may also be carried out under a particular set of <fen>Circumstances</fen> that are typically relevant to the functioning of the <fen>Product</fen>.
<ex><fex name="Tester">Sun</fex> has (hopefully) already <t>tested</t> <fex name="pro">it</fex> <fex name="des">for compliance</fex>.</ex>
<ex><fex name="pro">The Velcro hook and loop closure system</fex> has been <t>tested</t> <fex name="Circumstances">under wet conditions</fex> and retains its holding power after 10,000 open and close functions. <fex name="tes">CNI</fex> <fex name="unw">INI</fex></ex>
<ex><fex name="tes">Roe</fex> revisited the compound and <t>tested</t> <fex name="pro">it</fex> <fex name="fun">as a mosquito repellent</fex>.</ex></def-root>
<def-root>The person who uses the <fen>Product</fen> to see if it is intact or to ascertain its characteristics during operation.
<ex>I just wish <fex name="Tester">we</fex> could have <t>tested</t> the car with a manual gearbox, instead of the five-speed automatic</ex>
</def-root>
<def-root>The entity that the <fen>Tester</fen> uses to ascertain whether it is intact.
</def-root>
<def-root>An entity or property whose presence would impair the acceptability or usefulness of the <fen>Product</fen>.
<ex>To ensure that the remedy is complete, nCipher have fully reviewed the software and <t>tested</t> it <fex name="unw">for similar errors</fex>.</ex></def-root>
<def-root>This FE is used for a <fen>Means</fen> action which the <fen>Tester</fen> carries out in testing the <fen>Product</fen>.
<ex><fex name="mea">How</fex> we <t>tested</t> the Radeon 9700 Pro video-card.</ex></def-root>
<def-root>An action that the <fen>Tester</fen> intends to accomplish subjecting the <fen>Product</fen> to a test of its functioning.
<ex>Once you have copied your site and have <t>tested</t> it <fex name="pur">to make sure it works normally</fex>, you're ready to pull out the scalpel and start hacking away.</ex></def-root>
<def-root>This FE identifies the <fen>Manner</fen> in which the <fen>Tester</fen> uses the <fen>Product</fen> in order to evaluate its functioning.
<ex>Engineers <fex name="man">carefully</fex> <t>tested</t> the fields of view to make sure that security personnel would be able to view all critical areas.</ex></def-root>
<def-root>This FE identifies the extent to which the <fen>Tester</fen> examines the <fen>Product</fen>.
</def-root>
<def-root>This FE is the position of the <fen>Tester</fen> during the act of testing. Typically, it is expressed in a <ment>from</ment>-PP.
</def-root>
<def-root>The desirable state of affairs which the <fen>Tester</fen> hopes to find to obtain when using the <fen>Product</fen>.
<ex>Test-Driven Development requires you to set an expectation of a result and then <t>test</t> <fex name="des">that the result is achieved</fex>.</ex> </def-root>
<def-root>The <fen>Time</fen> when the <fen>Tester</fen> uses the <fen>Product</fen> to evaluate its functioning.
</def-root>
<def-root>The FE <fen>Circumstances</fen> is used for circumstances that obtain during the test procedure. These are typically relevant to how the <fen>Product</fen> functions.
<ex>We <t>tested</t> the drive <fex name="Circumstances">using the generic drivers of the OS</fex>.</ex></def-root>
<def-root>The length of the time period during which the <fen>Tester</fen> continuously or repeatedly operates the <fen>Product</fen> to determine its operational characteristics.
<ex>Before launching BioCheck, we <t>tested</t> the system <fex name="dur">for a year</fex> in Washington DC in response to more than 50 actual 9-1-1 calls.</ex></def-root>
<def-root>The location in which the test is carried out.
<ex>We <t>tested</t> the product <fex name="pla">in California</fex> first.</ex></def-root>
<def-root>A use to which the <fen>Product</fen> is put .
<ex>If you have HTML files from another source and you can't first read them into Microsoft
Word, you can try the process, but I haven't <t>tested</t> it <fex name="fun">for that use</fex>. </ex></def-root>
<def-root>A variable of behavior of the <fen>Product</fen> which is specifically evaluated.
<ex> ILCSO staff have <t>tested</t> <fex name="tpr">the behavior of the ILCSO-standard version of WebVoyage with several browsers</fex>.</ex></def-root>
<def-root>The length of time from when the testing event began to be repeated to when it stopped.
<ex>This approach has been <t>tested</t> <fex name="per">since 2001</fex>.</ex></def-root>
<def-root>The <fen>Result</fen> of the Operational_testing. </def-root>
Operating_a_system
FN: subject to a test of functioning or operation
COD: a procedure intended to establish the quality, performance, or reliability of something
COD: to test while in flight
COD: deliberately crash (a new vehicle) under controlled conditions in order to evaluate and improve its ability to withstand impact
FN: the act of performing a critical evaluation of something by using it
FN: the act of testing the functioning of something while it is in flight
COD: a flight of an aircraft or rocket to test its functioning.
COD: to test while in flight
FN: a test of efficacy.
FN: determine by use how well (something) functions.