| Spanish | English |
| adaptador de prueba | test adapter (The code assembly that is responsible for loading a particular type of test) |
| agente de prueba | test agent (A background process that receives, runs, and reports on tests and collects data on a single computer. The test agent communicates with test agent controller, usually located on another computer) |
| Analizador de prueba de carga | Load Test Analyzer (A Visual Studio window that displays results of any load test run, after it has run. It is used to examine any load test results that have already ended) |
| archivo de prueba | test file (A file used as part of a testing process to check the validity or correctness of a program or procedure) |
| Asistente para prueba de carga | Load Test Wizard (A wizard that guides you through the process of creating a load test) |
| banco de pruebas | benchmark (A quantitative measure of performance that is used to compare the company's products, services, or processes to an external standard. Competitive benchmarks are based on industry best, and process benchmarks are based on best in class) |
| caso de prueba | test case (A specification that describes the goals of a test, the results that the test might produce, the circumstances in which it will be run, and how it should be implemented) |
| condición de prueba | test condition (In a database unit test, a set of frequently used validation functions that test whether a unit test returns the expected results) |
| configuración de pruebas | test settings (A set of variables that define how tests are going to be run and any data to be collected or system actions taken while tests are run. For example, collect code coverage data or emulate a specific network) |
| conjunto de pruebas | test suite (A set of selected test cases. A test suite can contain other test suites, but each test suite can be contained in only one other test suite) |
| conjunto de pruebas basado en consulta | query-based test suite (The set of test cases that are returned when a specific query is run. If new test cases that meet the criteria in this query are added to the test suite, the new test cases will automatically appear in the query-based test suite) |
| duración de la versión de prueba | duration of trial (The length of time for which a trial of an application is valid) |
| edición de prueba | trial edition (A version of a product that can be used (typically at no cost) for a limited period of time for purposes of evaluation) |
| Editor de lista de pruebas | Test List Editor (The window in Visual Studio Team System that is used to manage, execute, and control large numbers of tests and test lists) |
| Editor de prueba de carga | Load Test Editor (The Visual Studio editor in which a .loadtest file is opened. It displays a tree structure of nodes) |
| Editor de prueba de rendimiento web | Web Performance Test Editor (The Visual Studio editor in which a Web test is edited. It displays a tree structure of request nodes) |
| Eficacia de la prueba | Test Effectiveness (A report that communicates the amount of code covered or exercised for a particular test run) |
| entorno de prueba | test environment (An environment that corresponds as closely as possible to the production environment and within which system and user acceptance tests can be carried out) |
| escenario de prueba de carga | load test scenario (A scenario used to model how a group of users interacts with a server application. A scenario consists of a test mix, a load profile, a network mix, and a browser mix. A load test can have more than one scenario) |
| Grabadora de prueba web | Web Test Recorder (A feature in Visual Studio Team Edition that records the actions you perform while you browse a Web site. As you move through the site, recorded requests are added to the Web test) |
| herramienta de prueba de objetos | Object Test Bench (A tool that creates instances of a project's objects, calls their methods, and evaluates the results) |
| implementación de pruebas | test deployment (The deployment of tests and all dependent files noted by the user or the system from their default location (for example, bin/debug) to the execution directory) |
| instalación de prueba | sideloading (The process of loading apps that were not distributed via the Windows Store, usually for testing an app before it is ready for sale) |
| Kit de pruebas de compatibilidad de hardware | Hardware Compatibility Test kit (A collection of tests that verify hardware and device driver operations under a specific operating situation on Microsoft Windows operating systems. The tests exercise the combination of a device, a software driver, and an operating system under controlled conditions and verify that all components operate properly) |
| matriz de ejecuciones de prueba | sample runmap (An array of sample runs that make up an entire image) |
| Modo de prueba-Modo real | Test Mode/Live Mode (The modes on the Accounts page for a custom spam filter policy rule to run in. A rule can be run in test mode to monitor what would happen if rule were deployed, or in live mode, where the rule is actually deployed) |
| Monitor de prueba de carga | Load Test Monitor (A Visual Studio window that displays results during a load test run) |
| método de prueba | test method (Any method that is marked with the TestMethod attribute. You cannot run a unit test if its test method is not in a test class) |
| plan de pruebas | test plan (A set of test cases and their associated test configuration information and the iteration when it is planned to run these tests. The test cases can be organized into a test suite hierarchy) |
| plantilla de prueba manual | manual test template (A template used by the system to give the tester a consistent experience when documenting a manual test) |
| prueba cíclica de redundancia | cyclic redundancy check (A procedure used in checking for errors in data transmission. CRC error checking uses a complex calculation to generate a number based on the data transmitted. The sending device performs the calculation before transmission and includes it in the packet that it sends to the receiving device. The receiving device repeats the same calculation after transmission. If both devices obtain the same result, it is assumed that the transmission was error free. The procedure is known as a redundancy check because each transmission includes not only data but extra (redundant) error-checking values. Communications protocols such as XMODEM and Kermit use cyclical redundancy checking) |
| prueba de aceptación | acceptance testing (Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a product or product component) |
| prueba de aceptación | acceptance test (A formal evaluation of a hardware product performed by the customer, usually at the factory, to verify that the product is performing according to specifications) |
| prueba de aceptación de la compilación | build acceptance test (A group of tests used to determine the health of a build at a high level. Typically, these tests exercise the core functionality to help team members determine whether further testing is worthwhile. They are run after the daily build to verify that compilation of source code has been built successfully and is ready for further testing) |
| prueba de caja blanca | white box view (A unit test is typically written by a developer to verify the behavior of a specific method or set of methods. They can also be used for white-box testing or in conjunction with load or stress testing) |
| prueba de carga | load testing (Testing at or beyond the limits of a specified requirement to understand its behavior and failure trigger points) |
| prueba de carga | load test (A test that studies the behavior of the program when it is working at its limits. Types of load tests include volume tests, stress tests, and storage tests. Volume tests study the largest tasks the program can deal with. Stress tests study the program's response to peak bursts of activity. Storage tests study how memory and space is used by the program, either in resident memory or on disk. A test that is designed to put a server application under heavy user load to pinpoint performance and/or scalability problems) |
| prueba de comprobación de la compilación | build verification test (A group of tests used to determine the health of a build at a high level. Typically, these tests exercise the core functionality to help team members determine whether further testing is worthwhile. They are run after the daily build to verify that compilation of source code has been built successfully and is ready for further testing) |
| prueba de concepto | proof of concept (The verification that the selected technology performs according to pre-established criteria in a lab environment designed to simulate the production environment) |
| prueba de esfuerzo | stress test (A test that determines an application's breaking points and pushes the application past its upper limits as resources are saturated) |
| prueba de humo | smoke test (A group of tests used to determine the health of a build at a high level. Typically, these tests exercise the core functionality to help team members determine whether further testing is worthwhile. They are run after the daily build to verify that compilation of source code has been built successfully and is ready for further testing) |
| prueba de interacción humana | Human Interactive Proof A challenge meant to be easily solved by humans, while remaining too hard to be economically solved by computers (HIP) |
| prueba de IU codificada | coded UI test (An automated test of the user interface of an application. A coded UI test exercises user actions and validates the expected results) |
| prueba de posicionamiento | hit test (A comparison of the mouse position with on-screen geometry. Commonly used to detect whether the mouse has been clicked over on-screen geometry) |
| prueba de regresión | regression test (A test that is run after the daily build to verify that compilation of source code has been built successfully) |
| prueba de seguridad | security test (A test that looks for attack paths that might be used to gain access to assets) |
| prueba de tablero | checkerboard test (A memory test employed to detect catastrophic failures and wiring problems within the memory chip and on the data bus by writing an alternating pattern of 0's and 1's to the memory chip) |
| prueba de validación | validation test (A test that ensures that the functionality called for in a scenario or quality of service requirement is working) |
| pruebas automáticas de encendido | power-on self test (A set of routines stored in read-only memory (ROM) that tests various system components such as RAM, the disk drives, and the keyboard, to see if they are properly connected and operating. If problems are found, these routines alert the user with a series of beeps or a message, often accompanied by a diagnostic numeric value. If the POST is successful, it passes control to the bootstrap loader) |
| pruebas de exploración de vulnerabilidades mediante datos aleatorios | fuzzing (A testing process that supplies structured but invalid input to software application programming interfaces (APIs) and network interfaces to maximize the likelihood of detecting errors that might lead to software vulnerabilities) |
| pruebas de exploración de vulnerabilidades mediante datos aleatorios | fuzz testing (A testing process that supplies structured but invalid input to software application programming interfaces (APIs) and network interfaces to maximize the likelihood of detecting errors that might lead to software vulnerabilities) |
| pruebas de iteración | iteration test (A test that is run after the build verification tests. These tests verify the functionality called for in the iteration plan) |
| punto de prueba | test point (A pairing of a test case and a test configuration) |
| resultado de la prueba | test result (The verdict from executing a test: pass, fail, or inconclusive) |
| script de prueba | test script (A defined requirement that is checked against a product and yields either a pass or a fail result. Pass indicates meeting the requirement and fail indicates not meeting the requirement) |
| serie de pruebas | test run (A set of pairings of test cases and test configurations to be run. The results of this set of pairings can be viewed together. Test runs are either automated or manual) |
| Sesión de prueba Live Meeting mediante VoIP en el centro de conferencia | VOIP-enabled Live Meeting trial conference center session (A Live Meeting session conducted using VoIP to transmit data and conducted on a Live Meeting conference center accessed with a trial account) |
| tarea de prueba | test task (An assignment to create test cases and test a specific area of the product, usually in the context of a scenario or quality of service requirement) |
| tipo de prueba | test type (A set of functionality and/or a template to help expose parts of the underlying test framework) |
| versión de prueba | Test Drive (A scaled-down version of a product where a user can try out different features before buying it) |
