CTAL-TTA-Glossar
Als Karteikarten üben →Durchsuche 65 lehrplanbasierte Begriffe und Definitionen nach Kapitel.
Fragen und Glossar derzeit auf Englisch; deutsche Inhalte folgen.
65 Begriffe
- accountability Kap. 4
- A security sub-characteristic used as a basis for specifying security tests.
- adaptability Kap. 4
- A portability sub-characteristic concerned with an application functioning in its intended target environments.
- analyzability Kap. 4
- A maintainability sub-characteristic concerned with how readily code can be analyzed.
- anomaly Kap. 3
- A potentially problematic sequence or use of code or data identified by static analysis.
- API testing Kap. 2
- Testing the application programming interface, with attention to its input parameters, returned results, and interactions.
- atomic condition Kap. 2
- A single condition within a decision predicate that evaluates to true or false.
- authenticity Kap. 4
- A security sub-characteristic used as a basis for specifying security tests.
- availability Kap. 4
- The extent to which a system is available to users and other systems under normal operating conditions.
- capacity Kap. 4
- A performance efficiency sub-characteristic concerned with maximum limits under specified operating conditions, such as transactions per unit of time or simultaneous users.
- capture/playback Kap. 6
- A tool capability that records manual interactions with graphical objects and replays them as an automated script.
- coexistence Kap. 4
- The ability of unrelated systems to run in the same environment without adversely affecting each other.
- compatibility Kap. 4
- A quality characteristic that includes coexistence and interoperability.
- confidentiality Kap. 4
- A security sub-characteristic used as a basis for specifying security tests.
- control flow Kap. 2
- The sequence of steps followed through code or another structured process.
- control flow analysis Kap. 3
- Static analysis of the steps followed through a program, commonly represented by a control flow graph.
- cyclomatic complexity Kap. 3
- A positive integer representing the number of independent paths in a strongly connected control flow graph.
- data flow analysis Kap. 3
- Static analysis that gathers information about how variables are defined, used, and destroyed.
- data-driven testing Kap. 6
- An automation approach that keeps test data separate from a script so one script can run with different inputs and expected results.
- decision testing Kap. 2
- A white-box technique that exercises the outcomes of decisions in code.
- definition-use pair Kap. 3
- A control flow path between a variable definition and a subsequent use of that variable.
- dynamic analysis Kap. 3
- Analysis that requires executing code to find defects or observe behavior while it runs.
- emulator Kap. 6
- A mobile testing tool that models device hardware and uses the same runtime environment as the physical device.
- fault injection Kap. 6
- The deliberate supply of incorrect inputs or creation of defect scenarios to check how software copes.
- fault seeding Kap. 6
- The deliberate modification of code under test to check the effectiveness of tests.
- fault tolerance Kap. 4
- The ability of a system to continue operating when failures occur.
- installability Kap. 4
- A portability sub-characteristic tested through the software and procedures for installing it in its target environment.
- integrity Kap. 4
- A security sub-characteristic used as a basis for specifying security tests.
- keyword-driven testing Kap. 6
- An automation approach that separates test actions and data from scripts by using descriptive keywords.
- maintainability Kap. 4
- The ease with which code can be analyzed, changed, tested, modularized, and reused.
- maturity Kap. 4
- The degree to which a system meets reliability requirements under normal operating conditions.
- memory leak Kap. 3
- Allocated memory that a program does not release when it is no longer needed.
- model-based testing (MBT) Kap. 6
- A technique using a model, such as a finite state machine, to describe intended runtime behavior.
- modifiability Kap. 4
- A maintainability sub-characteristic concerned with how readily code can be changed.
- modified condition/decision testing Kap. 2
- A white-box technique that uses pairs of tests to show that each atomic condition can independently affect a decision outcome.
- modularity Kap. 4
- A maintainability sub-characteristic that can be tested by static analysis.
- multiple condition testing Kap. 2
- A white-box technique that exercises combinations of atomic conditions within decisions.
- non-repudiation Kap. 4
- A security sub-characteristic used as a basis for specifying security tests.
- operational profile Kap. 4
- A pattern of system use, typically describing users, operations, and their frequencies or probabilities.
- performance efficiency Kap. 4
- A quality characteristic comprising time behavior, resource utilization, and capacity.
- portability Kap. 4
- The degree to which software can be transferred into or adapted to a target environment, or can replace another entity.
- product risk Kap. 1
- A risk concerning the product, assessed using factors such as technology and code complexity, code changes, defect history, and interface or integration issues.
- project risk Kap. 1
- A risk that may affect the project's success, such as conflicting technical requirements or high rates of technical requirements change.
- quality characteristic Kap. 4
- An aspect of product quality used to plan and organize technical testing, such as reliability or security.
- recoverability Kap. 4
- The ability of a system to recover from failure, measured by recovery time or data loss.
- reliability Kap. 4
- The ability of software to perform specified functions under specified conditions for a specified period.
- reliability growth model Kap. 4
- A statistical model that uses a reducing frequency of failures to predict mean time between failures.
- replaceability Kap. 4
- The ability of a software component to replace an existing component in a system.
- resource utilization Kap. 4
- A performance efficiency sub-characteristic concerned with resource usage during operation.
- reusability Kap. 4
- A maintainability sub-characteristic that may be evaluated through architectural reviews.
- review Kap. 5
- An examination of a work product to understand what is written, identify what is missing, and verify technical correctness and consistency.
- risk assessment Kap. 1
- The evaluation of identified risks to estimate their likelihood and impact.
- risk identification Kap. 1
- The activity of identifying pertinent risks, drawing on stakeholders' views, expert interviews, brainstorming, and experience.
- risk mitigation Kap. 1
- Actions that reduce or respond to identified risks, including designing and executing tests and using contingency measures.
- risk-based testing Kap. 1
- A testing approach in which identified and assessed risks guide the test strategy and test activities.
- safety integrity level Kap. 2
- A relative level of risk reduction defined by IEC 61508 for a safety-related system.
- security Kap. 4
- A product quality characteristic with confidentiality, integrity, non-repudiation, accountability, and authenticity as sub-characteristics.
- simulator Kap. 6
- A mobile testing tool that models a mobile platform runtime environment and runs a dedicated application build.
- statement testing Kap. 2
- A white-box technique focused on exercising executable statements in code.
- static analysis Kap. 3
- Evaluation of software without executing it, performed by a tool or a person.
- technical review Kap. 5
- A review in which the Technical Test Analyst contributes a technical perspective on a work product.
- test execution Kap. 6
- The running of tests, which can be supported or automated by test tools.
- testability Kap. 4
- A maintainability sub-characteristic concerned with how readily code can be tested.
- time behavior Kap. 4
- A performance efficiency sub-characteristic concerned with response or processing time.
- white-box test technique Kap. 2
- A test technique applied to code or another structure, with coverage measured against that structure.
- wild pointer Kap. 3
- A pointer that is no longer accurate and must not be used.