AJAX progress indicator
Search (clear)
  • Siehe Istergebnis.
  • Acronym for test-driven development.
  • A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and Graham], [IEEE 1028] See also peer review.
  • Eine Diskussion in einer Gruppe gleichgestellter qualifizierter Mitarbeiter, die sich darauf konzentriert, eine Übereinstimmung über technische Vorgehensweisen zu erreichen. [Gilb und Graham], [IEEE 1028] Siehe auch Peer Review.
  • Eine Folge von ausführbaren Anweisungen in einer Komponente.
  • Eine Menge von einem oder mehreren Testfällen. [IEEE 829]
  • A set or one of more test cases [IEEE 829].
  • The layer in a test automation architecture which provides the necessary code to adapt test scripts on an abstract level to the various components, configuration or interfaces of the SUT.
  • The process of analyzing the test basis and defining test objectives.
  • The implementation of the test strategy for a specific project. It typically includes the decisions made that follow the (test) project’s goal and the risk analysis, starting points regarding the test process, the test design techniques to be applied, exit criteria and test types to be performed.
  • (1) A person who provides guidance and strategic direction for a test organization and for its relationship with other disciplines. (2) A person who defines the way testing is structured for a given system, including topics such as test tools and test data management.
  • The use of software to perform or support test activities, e.g. test management, test design, test execution and results checking.
  • An instantiation of the generic test automation architecture to define the architecture of a test automation solution, i.e., its layers, components, services and interfaces.
  • A person who is responsible for the design, implementation and maintenance of a test automation architecture as well as the technical evolution of the resulting test automation solution.
  • A tool that provides an environment for test automation. It usually includes a test harness and test libraries.
  • A person who is responsible for the planning and supervision of the development and evolution of a test automation solution.
  • A realization/implementation of a test automation architecture, i.e., a combination of components implementing a specific test automation assignment. The components may include off-the-shelf test tools, test automation frameworks, as well as test hardware.
  • A high-level plan to achieve long-term objectives of test automation under given boundary conditions.
  • All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by way of formal amendment procedure, then the test basis is called a frozen test basis [after TMap].
  • See test environment.
  • A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement [after IEEE 610].
  • See test design technique.
  • The disproportionate growth of the number of test cases with growing size of the test basis, when using a certain test design technique. Test case explosion may also happen when applying the test design technique systematically for the first time.
  • The final verdict on the execution of a test and its outcomes, like pass, fail, or error. The result of error is used for situations where it is not clear whether the problem is in the test object.
  • A document specifying a set of test cases (objective, inputs, test actions, expected results, and execution preconditions) for a test item. [After IEEE 829] See also test specification.
  • See test suite.
  • Eine Anweisung von Testzielen und möglichen Testideen wie getestet werden soll. Test-Chartas werden oft im explorativen Testen verwendet. Siehe auch exploratives Testen.
  • A statement of test objectives, and possibly test ideas about how to test. Test charters are often used in exploratory testing. See also exploratory testing.
  • During the test closure phase of a test process data is collected from completed activities to consolidate experience, testware, facts and numbers. The test closure phase consists of finalizing and archiving the testware and evaluating the test process, including preparation of a test(...)
  • A test tool to perform automated test comparison of actual results with expected results.
Cookie Consent with Real Cookie Banner