English | French |
alpha test | test alpha (A type of post-pixel blending operation which allows applications to control when pixels are written to the render target) |
automated test | test automatisé (A set of steps that a computer may run programmatically to test the functionality of the system) |
black box test | test boîte noire (A test that is based on a component's actual behavior, without regard to its implementation) |
build acceptance test | test d'acceptation de build (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) |
build verification test | test de vérification de build (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) |
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 | test d'analyse mémoire (échiquier) |
check-in test | test de vérification (A test run by a developer to determine whether his code has affected the general stability of the product) |
coded UI test | test codé de l'interface utilisateur (An automated test of the user interface of an application. A coded UI test exercises user actions and validates the expected results) |
coded Web test | test Web codé (A type of test that is typically created by converting an existing recorded Web test into C or Visual Basic code) |
database unit test | test unitaire de base de données (A unit test that validates whether a certain aspect of your database is working as you expect) |
declarative test | test déclaratif (An ordinary Web test that is generated by using the Web Test Recorder that is launched when a new Web test is created) |
functional test | test fonctionnel (A test that verifies that all of the functions of a feature are correctly implemented) |
generic test | test générique (A known Visual Studio test type that encapsulates an unknown test or tool and allows Visual Studio to treat it as a known type) |
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 | kit Microsoft Hardware Compatibility Test (HCT) |
Internet Explorer Compatibility Test Tool | Outil de test de de compatibilité d'Internet Explorer (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) |
iteration test | test d'itération (A test that is run after the build verification tests. These tests verify the functionality called for in the iteration plan) |
lab test | test de laboratoire (A procedure that is intended to detect and quantify substances or identify the nature of a disease) |
lab test | test en labo (A procedure that is intended to detect and quantify substances or identify the nature of a disease) |
laboratory test | test en laboratoire (A procedure that is intended to detect and quantify substances or identify the nature of a disease) |
load test | test de charge (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) |
Load Test Analyzer | analyseur de test de charge (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) |
Load Test Editor | éditeur de test de charge (The Visual Studio editor in which a .loadtest file is opened. It displays a tree structure of nodes) |
Load Test Monitor | moniteur de test de charge (A Visual Studio window that displays results during a load test run) |
load test scenario | scénario de test de charge (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) |
Load Test Wizard | Assistant Test de charge (A wizard that guides you through the process of creating a load test) |
manual test | test manuel (A test performed by a human) |
manual test template | modèle de test manuel (A template used by the system to give the tester a consistent experience when documenting a manual test) |
Object Test Bench | Banc de test d'objets (A Visual J feature that is designed for simple object-level testing) |
ordered test | test ordonné (A test that contains other tests, which are run in a specific order) |
Partner Test | test partenaire (A test, written by a Microsoft partner, that uses the test framework's extensibility interfaces) |
pending test | test en attente (A test that has been selected to run but is not yet in progress. Pending tests can be viewed in the Test Results window) |
penetration test | test de pénétration (A test that looks for attack paths that might be used to gain access to assets) |
performance test | test de performances (A procedure used to assess performance) |
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 | autotest de mise sous tension (POST) |
query-based test suite | suite de tests basée sur une requête (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) |
regression test | test de régression (A test that is run after the daily build to verify that compilation of source code has been built successfully) |
security test | test de sécurité (A test that looks for attack paths that might be used to gain access to assets) |
smoke test | test de détection de fumée (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) |
stress test | test de contrainte (A test that determines an application's breaking points and pushes the application past its upper limits as resources are saturated) |
system-under-test | système testé (A system that is being tested for correct operation) |
Test Access Port | accès TAP (A collection of boundary scan control signals that define a serial protocol for scan-based devices. There are five pins, TCK/clock, TMS/mode select, TDI/data in, TDO/data out, and TRST/reset) |
test adapter | adaptateur de test (The code assembly that is responsible for loading a particular type of test) |
test agent | agent de test (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) |
test agent controller | contrôleur d'agent de test (A background process that manages a set of machines with the test agent software installed) |
test approach | approche de test (The test goals, coverage, techniques, and data for the project and each of the iterations) |
test case | cas de test (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) |
test class | classe de test (Any class that is marked with the TestClass attribute) |
test condition | condition de test (In a database unit test, a set of frequently used validation functions that test whether a unit test returns the expected results) |
test configuration | configuration de test (A set of configuration variables that specify the correct setup required for testing an application) |
test deployment | déploiement de tests (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) |
test developer | développeur de tests (A tester typically assigned to authoring coded tests) |
Test Effectiveness | Rapport d'efficacité de test (A report that communicates the amount of code covered or exercised for a particular test run) |
test environment | environnement de test (An environment that corresponds as closely as possible to the production environment and within which system and user acceptance tests can be carried out) |
test fake | élément fictif de test (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) |
test file | fichier de test (A file used as part of a testing process to check the validity or correctness of a program or procedure) |
test harness | atelier de test (An application that loads test adapters and owns the process that executes tests) |
test list | liste de tests (A list of tests that can be selected and managed from Test Manager) |
Test List Editor | Explorateur de tests (The window in Visual Studio Team System that is used to manage, execute, and control large numbers of tests and test lists) |
test method | méthode de test (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) |
test metric | métrique de test (A unit of measure for testing) |
test metric threshold | seuil de métrique de test (A goal for the project, measured using a test metric) |
test mix | combinaison de tests (A formula that defines the probability of a virtual user running a given test in a load test scenario) |
Test mode | mode Test (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)) |
Test mode | mode Test (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)) |
Test Mode/Live Mode | Mode Test/Mode réel (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) |
test plan | plan de test (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) |
test point | point de test (A pairing of a test case and a test configuration) |
test project | projet de test (A project created specifically to hold test types) |
test result | résultat de test (The verdict from executing a test: pass, fail, or inconclusive) |
Test Results | Résultats des tests (A window which displays the current status of every test in the test run) |
Test Results window | fenêtre Résultats des tests (A window which displays the current status of every test in the test run) |
test run | série de tests (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 script | script de test (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) |
test settings | paramètres de test (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) |
test shim | modificateur de test (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) |
test step | étape de test (An action to be taken when the test is run, and possibly the expected result from that action) |
test stub | stub de test (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) |
test suite | suite de tests (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) |
test suite | suite de tests (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) |
test task | tâche de test (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) |
test type | type de test (A set of functionality and/or a template to help expose parts of the underlying test framework) |
Test View | Affichage des tests (A window that allows you to navigate to your tests for editing (authoring)) |
Test View window | fenêtre Affichage des tests (A window that allows you to navigate to your tests for editing (authoring)) |
unit test | test unitaire (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) |
validation test | test de validation (A test that ensures that the functionality called for in a scenario or quality of service requirement is working) |
Web Performance Test Editor | éditeur de test de performances Web (The Visual Studio editor in which a Web test is edited. It displays a tree structure of request nodes) |
Web Performance Test Result Viewer | Afficheur de résultats de test de performances Web (A Visual Studio window where Web tests are run and results are displayed) |
Web Test Recorder | Enregistreur de test Web (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) |