| French | English |
| adaptateur de test | test adapter (The code assembly that is responsible for loading a particular type of test) |
| Affichage des tests | Test View (A window that allows you to navigate to your tests for editing (authoring)) |
| Afficheur de résultats de test de performances Web | Web Performance Test Result Viewer (A Visual Studio window where Web tests are run and results are displayed) |
| agent de test | 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) |
| analyseur de test de charge | 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) |
| approche de test | test approach (The test goals, coverage, techniques, and data for the project and each of the iterations) |
| Assistant Test de charge | Load Test Wizard (A wizard that guides you through the process of creating a load test) |
| atelier de test | test harness (An application that loads test adapters and owns the process that executes tests) |
| Banc de test d'objets | OTB (A Visual J feature that is designed for simple object-level testing) |
| Banc de test d'objets | Object Test Bench (A Visual J feature that is designed for simple object-level testing) |
| cas de test | 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) |
| chargement de version test | 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) |
| classe de test | test class (Any class that is marked with the TestClass attribute) |
| combinaison de tests | test mix (A formula that defines the probability of a virtual user running a given test in a load test scenario) |
| condition de test | test condition (In a database unit test, a set of frequently used validation functions that test whether a unit test returns the expected results) |
| configuration de série de tests | run configuration (Settings that are stored in a run configuration file and that impact the runtime environment of a test run) |
| configuration de test | test configuration (A set of configuration variables that specify the correct setup required for testing an application) |
| contrôleur d'agent de test | test agent controller (A background process that manages a set of machines with the test agent software installed) |
| déploiement de tests | 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) |
| développeur de tests | test developer (A tester typically assigned to authoring coded tests) |
| effectuer un test Ping | Ping device (The action of testing a particular device on the network for troubleshooting purposes using the ping utility) |
| Enregistreur de test 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) |
| environnement de test | 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) |
| expiration du test Ping | ping time out (The amount of time after which a ping attempt fails) |
| Explorateur de tests | 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) |
| fenêtre Affichage des tests | Test View window (A window that allows you to navigate to your tests for editing (authoring)) |
| fenêtre Résultats des tests | Test Results window (A window which displays the current status of every test in the test run) |
| fichier de test | test file (A file used as part of a testing process to check the validity or correctness of a program or procedure) |
| kit Microsoft Hardware Compatibility Test | 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 (HCT) |
| liste de tests | test list (A list of tests that can be selected and managed from Test Manager) |
| mode Test | Test mode (A Directory Services option on the Accounts page. When a customer is running in Test mode, all e-mail for recipients who are not on the user list is redirected to a separate e-mail address after filtering (thus this mail is not rejected)) |
| mode Test | Test mode (A Directory Services option on the Accounts page. When a customer is running in Test mode, all e-mail for recipients who are not on the user list is redirected to a separate e-mail address after filtering (thus this mail is not rejected)) |
| Mode Test/Mode réel | 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) |
| modificateur de test | test shim (A type of test fake that works by introducing a detour to the entry point of methods or properties that are called by a unit under test. The shim is executed instead of the existing code, and is under the control of the tests. A shim can be applied to any code, even if it was not designed to be isolated during testing) |
| modèle de test manuel | manual test template (A template used by the system to give the tester a consistent experience when documenting a manual test) |
| moniteur de test de charge | Load Test Monitor (A Visual Studio window that displays results during a load test run) |
| méthode de test | 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) |
| métrique de test | test metric (A unit of measure for testing) |
| numéro du test de calcul | calculation pass number (An ordinal position used to refer to a calculation pass) |
| Outil de test de de compatibilité d'Internet Explorer | Internet Explorer Compatibility Test Tool (A tool that provides a user interface that enables you to display data about your Internet Explorer issues in real-time, including allowing you to filter your results and upload your data to your ACT database using the ACT Log Processing Service) |
| paramètres de test | 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) |
| plan de test | 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) |
| point de test | test point (A pairing of a test case and a test configuration) |
| Programme de test de mémoire Windows | Windows Memory Tester (A Boot Configuration Data (BCD) application object) |
| projet de test | test project (A project created specifically to hold test types) |
| Rapport d'efficacité de test | Test Effectiveness (A report that communicates the amount of code covered or exercised for a particular test run) |
| résultat de test | test result (The verdict from executing a test: pass, fail, or inconclusive) |
| Résultats des tests | Test Results (A window which displays the current status of every test in the test run) |
| script de test | 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) |
| scénario de test de charge | 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) |
| seuil de métrique de test | test metric threshold (A goal for the project, measured using a test metric) |
| site Web de test | staging Web site (A Web site that is maintained on a private file or Web server) |
| site Web de test | staging web (A Web site that is maintained on a private file or Web server) |
| stub de test | test stub (A type of test fake that is an alternative implementation of an interface or class that is called by a unit under test. The test stub is under the control of the unit tests. Designing a system so that its parts can be replaced by test stubs results in more flexible code) |
| suite de tests | 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) |
| suite de tests | 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) |
| suite de tests basée sur une requête | 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) |
| série de tests | 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) |
| test alpha | alpha test (A type of post-pixel blending operation which allows applications to control when pixels are written to the render target) |
| test automatisé | automated test (A set of steps that a computer may run programmatically to test the functionality of the system) |
| test basé sur la technologie HIP | HIP challenge (A challenge meant to be easily solved by humans, while remaining too hard to be economically solved by computers) |
| test boîte noire | black box test (A test that is based on a component's actual behavior, without regard to its implementation) |
| test codé de l'interface utilisateur | 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) |
| test d'acceptation | acceptance testing (Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a product or product component) |
| test d'acceptation de build | 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) |
| test d'analyse mémoire | 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 (échiquier) |
| test de calcul | calculation pass (A stage of calculation in a multidimensional cube in which applicable calculations are evaluated) |
| test de charge | load testing (Testing at or beyond the limits of a specified requirement to understand its behavior and failure trigger points) |
| test de charge | 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) |
| test de contrainte | stress test (A test that determines an application's breaking points and pushes the application past its upper limits as resources are saturated) |
| test de détection de fumée | 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) |
| test de laboratoire | lab test (A procedure that is intended to detect and quantify substances or identify the nature of a disease) |
| test de performances | performance test (A procedure used to assess performance) |
| test de pénétration | penetration test (A test that looks for attack paths that might be used to gain access to assets) |
| test de régression | regression test (A test that is run after the daily build to verify that compilation of source code has been built successfully) |
| test de sécurité | security test (A test that looks for attack paths that might be used to gain access to assets) |
| test de validation | validation test (A test that ensures that the functionality called for in a scenario or quality of service requirement is working) |
| test de vérification | check-in test (A test run by a developer to determine whether his code has affected the general stability of the product) |
| test de vérification de build | 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) |
| test d'itération | iteration test (A test that is run after the build verification tests. These tests verify the functionality called for in the iteration plan) |
| test déclaratif | declarative test (An ordinary Web test that is generated by using the Web Test Recorder that is launched when a new Web test is created) |
| test en attente | pending test (A test that has been selected to run but is not yet in progress. Pending tests can be viewed in the Test Results window) |
| test en labo | lab test (A procedure that is intended to detect and quantify substances or identify the nature of a disease) |
| test en laboratoire | laboratory test (A procedure that is intended to detect and quantify substances or identify the nature of a disease) |
| test fonctionnel | functional test (A test that verifies that all of the functions of a feature are correctly implemented) |
| test générique | generic test (A known Visual Studio test type that encapsulates an unknown test or tool and allows Visual Studio to treat it as a known type) |
| test manuel | manual test (A test performed by a human) |
| test ordonné | ordered test (A test that contains other tests, which are run in a specific order) |
| test partenaire | Partner Test (A test, written by a Microsoft partner, that uses the test framework's extensibility interfaces) |
| test Ping | ping (A protocol for testing whether a particular computer is connected to the Internet by sending a packet to its IP address and waiting for a response) |
| test unitaire | unit test (A test that confirms the functionality and peformance of specific modules and behaviors of code. Often a subset of unit tests are also used as check-in test to discover bugs before a build) |
| test unitaire de base de données | database unit test (A unit test that validates whether a certain aspect of your database is working as you expect) |
| test Web codé | coded Web test (A type of test that is typically created by converting an existing recorded Web test into C or Visual Basic code) |
| test à données aléatoires | 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 (fuzzing) |
| test à données aléatoires | 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 (fuzzing) |
| tests exploratoires | exploratory testing (The testing of an application without a set of tests defined in advance) |
| type de test | test type (A set of functionality and/or a template to help expose parts of the underlying test framework) |
| tâche de test | 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) |
| éditeur de test de charge | Load Test Editor (The Visual Studio editor in which a .loadtest file is opened. It displays a tree structure of nodes) |
| éditeur de test de performances Web | Web Performance Test Editor (The Visual Studio editor in which a Web test is edited. It displays a tree structure of request nodes) |
| élément fictif de test | test fake (A mechanism that allows you to isolate part of an application so that it can be tested separately from another part on which it would be dependent in typical operation. During testing, a test fake executes instead of the methods and properties of the other part. The actions and return values of the test fake are under the control of the test. Within Visual Studio, a test fake takes the form of either a test stub or a test shim) |
| étape de test | test step (An action to be taken when the test is run, and possibly the expected result from that action) |
