ISTQB Glossary A-b

16 Questions

ISTQB Quizzes & Trivia


Questions and Answers
  • 1. 
    The exit criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.
  • 2. 
    A white-box test design technique in which test cases are designed to execute branches.
  • 3. 
    A basic block that can be selected for execution based on a program construct in which one of two or more alternative program paths is available, e.g., case, jump, go to, if-then-else.
  • 4. 
    A black-box test design technique in which test cases are designed based on boundary values.
  • 5. 
    An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge, for example the minimum or maximum value of a range.
  • 6. 
    Testing, either functional or non-functional, without reference to the internal structure of the component or system.
  • 7. 
    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.
  • 8. 
    Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers, to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes. It is often employed as a form of external acceptance testing for off-the-shelf software in order to acquire feedback from the market.
  • 9. 
    A superior method or innovative practice that contributes to the improved performance of an organization under given context, usually recognized as "best" by other peer organizations.
  • 10. 
    The degree to which a component or system is operational and accessible when required for use. Often expressed as a percentage.
  • 11. 
    A path by which the original input to a process (e.g., data) can be traced back through the process, taking the process output as a starting point. This facilitates defect analysis and allows a process audit to be carried out.
  • 12. 
    An independent evaluation of software products or processes to ascertain compliance to standards, guidelines, specifications, and/or procedures based on objective criteria, including documents that specify: (1) the form or content of the products to be produced, (2) the process by which the products shall be produced, (3) how compliance to standards or guidelines shall be measured.
  • 13. 
    Simulated or actual operational testing by potential users/customers or an independent test team at the developers' site, but outside the development organization. It is often employed for off-the-shelf software as a form of internal acceptance testing.
  • 14. 
    The behavior produced/observed when a component or system is tested.
  • 15. 
    User or any other person or system that interacts with the system under test in a specific way.
  • 16. 
    Formal 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 authorized entity to determine whether or not to accept the system.