¡GoConqr estrena diseño! Cuéntanos qué te parece.

Regístrate gratis

Fichas

ISTQB Glossary Keywords

Jannik Fritz ISTQB Certificarion Alemán 105 fichas

Fichas del conjunto (105)

  1. 1Acceptance testingFormal testing with respect to user needs, requirements and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other suthorized entity to determine whether or not to accept the system
  2. 2Ad hoc reviewingA review technique carried out by independent reviewers informally, without a structured process
  3. 3Alpha testingSimulated or actual operational testing conducted in the developer´s test environment, by roles outside the development organisation
  4. 4Beta testingSimulated or actual operational testing conducted at an external site, by roles outside the development testing
  5. 5Black box test techniqueA procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system without reference to its internal structure.
  6. 6Boundary value analysisA black-box test technique in which test cases are designed based on boundary values
  7. 7Checklist based reviewingA review technique guided by a list of questions or required attributes
  8. 8checklist based testingAn experience-based test technique whereby the experienced tester uses a high-level list of items to be noted, checked or remembered or a set of rules or criteria against which a product has to be verified
  9. 9Commercial off the shelf (COTS)A software product that is developed for the general market i.e. for a large number of customers in identical format.
  10. 10Component integration testingTesting performed to expose defects in the interfaces and interactions between integrated components
  11. 11Component testingThe testing of indicidual hardware or software components
    (unit testing)
  12. 12Configuration managementA discipline applying technical and administrative direction and surveillance to identify and document the functional and pyhsical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status and verify compliance with specified requirements
  13. 13Confirmation testingDynamic testing conducted after fixing defects with the objective to confirm that failures caused by those defects do not occur anymore
  14. 14Contractual acceptance testingAcceptance testing conducted to verify whether a system satisfies its contractual requirements
  15. 15CoverageThe degree to which specified coverage items have been determined to have been exercised by a test suite expressed as percentage
  16. 16Data-driven testingA scripting technique that stores test input and expected results in a table or spreadsheet, so that a single control script can execute all of the tests in the table. Data-driven testing is often used to support the application of test execution tools such as capture/playback tools.
  17. 17DebuggingThe process of finding, analyzing and removing the cause of failures in software.
  18. 18Decision coverageThe coverage of decision outcomes
    (If-statements)
  19. 19Decision table testingA black-box test technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes)
  20. 20Defect managementThe process of recognizing and recording defects, classifying them, investigating them, taking action to resolve them and disposing of them when resolved.
  21. 21Dynamic testingTesting that involves the execution of the software of a component or system
  22. 22Entry criteriaThe set of conditions for officially starting a defined task
    (definition of ready)
  23. 23Equivalence partitioningA black-box test technique in which test cases are designed to exercise equivalence partitions by using one representative member of each partition.
  24. 24ErrorA human action that produces an incorrect result
  25. 25Error guessingA test technique in which tests are derived on the basis of the tester´s knowledge of past failures, or general knowlegde of failure modes.
  26. 26Exit criteriaThe set of conditions for officially completing a defined task
  27. 27Experience-based test techniqueA procedure to derive and/or select test cases based on the tester´s experience, knowledge and intuition.
  28. 28Exploratory testingAn approach to testing whereby the testers dynamically design and execute tests based on their knowledge, exploration of the test item and the results of previous tests
  29. 29FailureAn event in which a component or system does not perform a required function within specified limits
  30. 30Formal reviewA form of review that follows a defined process with a formally documented output
  31. 31Functional testingTesting conducted to evaluate the compliance of a component or system with functional requirements
  32. 32Impact analysisThe identification of all work products affected by a change, including an estimate of the resources needed to accomplish the change
  33. 33Informal reviewA type of review without a formal (documented) procedure
  34. 34InspectionA type of formal review to identify issues in a work product, which provides measurement to improve the review process and the software development process
  35. 35Integration testingTesting performed to expose defects in the interfaces and in the interactions between integrated components or systems.
  36. 36Keyword-driven testingA scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested. The keywords are interpreted by special supporting scripts that are called by the control script for the test
  37. 37Maintenance TestingTesting the changes to an operational system or the impact of a changed environment to an operational system
  38. 38Non-functional testingTesting conducted to evaluate the compliance of a component or system with non-functional requirements
  39. 39Operational acceptance testingOperational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff focusing on operational aspects, for example, recoverability, resource-behavior, installability and technival compliance
  40. 40Performance testing toolA test tool that generates load for a designated test item and that measures and records its performance during test execution
  41. 41Perspective-based readingA review technique whereby reviewers evaluate the work product from different viewpoints
  42. 42Product riskA risk impacting the quality of a product
  43. 43Project riskA risk that impacts project success
  44. 44QualityThe degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations
  45. 45Quality assurancePart of quality management focused on providing confidence that quality requirements will be fulfilled
  46. 46Regression testingTesting of a previously tested component or system following modification to ensure that defects have not been introduced or have been uncovered in unchanged areas of the software as a result of the changes made
  47. 47Regulatory acceptance testingAcceptance testing conducted to verify whether a system conforms to relevant laws. policies and regulations
  48. 48ReviewA type of static testing during which a work product or process is evaluated by one or more individuals to detect issues and to provide improvements
  49. 49RiskA factor that could result in future negative consequences
  50. 50Risk-based testingTesting in which the management. selection. prioritization and use of testing activities and resources are based on corresponding risk types and risk levels
  51. 51Risk levelThe qualitative or quantitative measure of a risk defined by impact and likelihood
  52. 52Role-based reviewingA review technique where reviewers evaluate a work product from the perspective of different stakeholder roles
  53. 53Root causeA source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed
  54. 54Scenario-based reviewingA review technique where the review is guided by determining the ability of the work product to address specific scenarios
  55. 55Sequential development modelA type of development life cycle model in which a complete system is developed in a linear way of several discrete and successive phases with no overlap between them.
  56. 56State transition testingA black-box test technique using a state transistion diagram or state table to derive test cases to evaluate whether the test item successfully executes valid transitions and blocks invalid transitions
  57. 57Statement coverageThe percentage of executable statements that have been exercised by a test suite
  58. 58Static analysisThe process of evaluating a component or system without executing it, based on its form, structure, content or documentation
  59. 59Static testingTesting a work product without code being executed
  60. 60System integration testingTesting the comnbination and interaction of systems
  61. 61System testingTesting an integrated system to verify that it meets specified requirements
  62. 62Technical reviewA formal review type by a team of technically-qualified personnel that examines the suitability of a work product for its intended use and identifies discrepancies from specifications and standards
  63. 63Test analysisThe activity that identifies test conditions by analyzing the test basis
  64. 64Test approachThe implementation of the test strategy for a specific project
  65. 65Test automationThe use of software to perform or support test activities, for example, test management, test design, test execution and results checking
  66. 66Test analysisThe body of knowledge used as the basis for test analysis and design
  67. 67Test caseA set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions
  68. 68Test completionThe activity that makes test assets available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to relevant stakeholders
  69. 69Test conditionAn aspect of the test basis that is relevant in order to achieve specifiy test objectives
  70. 70Test controlA test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned
  71. 71Test dataData created or seleted to satisfy the execution preconditions and inputs to execute one or more test cases
  72. 72Test designThe activity of deriving and specifying test cases from test conditions
  73. 73Test environmentAn environment containing hardware, instrumentation, simulators, software tools and other support elements needed to conduct a test
  74. 74TThe calculated approximation of a result related to various aspects of testing (for example, effort spent, completion date, costs involved, number of test cases, etc.), which is usable even if input data may be incomplete, uncertain or noisy
  75. 75Test executionThe process of running a test on the component or system under test, producing actual result(s)
  76. 76Test execution scheduleA schedule for the execution of test suites wihtin a test cycle
  77. 77Test execution toolA test tool that executes tests against a designated test item and evaluates the outcomes against expected results and postconditions
  78. 78Test implementationThe activity that prepares the testware needed for test execution based on test analysis and design.
  79. 79Test levelA specific instantiation of a test process
  80. 80Test management toolA tool that provides support to the test management and control part of a test process. It often has several capabilities, such as testware management, scheduling of tests, the logging of results, progress tracking, incident management and test reporting
  81. 81Test managerThe person responsible for project management of testing acitvities and resources, and evaluation of a test object. The individual who directs, controls, administers, plans and regulates the evaluation of a test object
  82. 82Test monitoringA test management activity that involves checking the status of testing activities, identifying any variances from the planned or expected status and reporting status to stakeholders
  83. 83Test objectThe component or system to be tested
  84. 84Test objectiveA reason or purpose for designing and executing a test
  85. 85Test oracleA source to determine expected results to compare with the actual result of the system under test
  86. 86Test planDocumentation describing the test objectives to be achived and the means and the schedule for achieving them, organized to coordinate testing acitivites
  87. 87Test planningThe activity of establishing or updating a test plan
  88. 88Test procedureA sequence of test cases in execution order, and any associated actions that may be required to set up the initial preconditions and any wrap-up activities post execution
  89. 89Test progress reportA test report produced at regular intervals about the progress of test activities against a baseline, risks, and alternatives requiring a decision
  90. 90Test strategyDocumentation that expresses the generic requirements for testing one or more projects run within an organization, providing detail on how testing is to be performed, and is aligned with the test policy
  91. 91Test suiteA set of test cases or test procedures to be executed in a specific test cycle
  92. 92Test summary reportA test report that provides an evaluation of the corresponding test items against exit criteria
  93. 93Test techniqueA procedure used to derive and/or select test cases
  94. 94Test typesA group of test activities based on specific test objectives aimed at specific characteristics of a component or system
  95. 95TesterA skilled professional who is involved in the testing of a conponent or system
  96. 96TestingThe process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects
  97. 97TestwareWork products produced during the test process for use in planning, designing, executing, evaluating and reporting on testing
  98. 98TraceabilityThe degree to which a relationship can be established between two or more work products
  99. 99Use case testingA black-box test technique in which test cases are designed to execute scenarios of use cases
  100. 100User acceptance testAcceptance testing conducted in a real or simulated operational environment by intended users focusing on theis needs, requirements and business processes
  101. 101ValidationConfirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled
  102. 102VerificationConfirmation by examination and through provision of objective evidence that specified requirements have been fulfilles
  103. 103WalkthroughA type of review in which an author leads members of the review through a work product and the members ask questions and make comments about possible issues
  104. 104White-box test techniqueA procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system
  105. 105White-box testingTesting based on an analysis of the internal structure of the component or system

Información

Descripción
These are glossary definitions from the ISTQB syllabus. These keywordsare specifically mentioned as keywords in the learning Chapters.
Creado por
Jannik Fritz
Visitas
164
Etiquetas
istqb
Valoración

Escríbenos

¿Sobre qué es tu mensaje?

¿Qué te parece el nuevo diseño?

¿Te gusta?