ISTQB CTFL pdf studying

source of info needed to write test cases and for test analysis

specification that a tester must adhere to when testing a software program

set of actions performed on the system to see if it meets the requirements and functions correctly

formal specification of test cases

collection of test cases that are grouped for test execution purposes

metric that defines amount of testing performed by a set of test cases

finding or fixing errors in the source code of software

system error that doesn’t allow the intended action to be completed

mistake in coding

inability of a software to perform its required function

first point that started to cause a defect

process of inspecting and analyzing the test artefacts in order to create test conditions or test cases

occurs based on the results of test monitoring, taking correcting action based on test monitoring reports to improve quality and efficiency

data created or selected to satisfy execution conditions or input content of test cases

describes how testing should be done

process of performing test cases to identify problems

making test procedures and test data and possibly writing automated test scripts

process of evaluating and providing feedback on test proceedings that are in progress

reference to an object currently being tested in the software

specific goal of software testing for that software (kinda the reason why you’d want to find bugs)

mechanism that determines whether software executed correctly for a test case

define objectives for testing and an approach for meeting test objectives

formal specification of test cases to be applied to one or more target program modules

all of the materials to perform a test

being able to match a test case to a part of the software and vice versa so you can actually fix detected error

process of verifying that it meets the needs and requirements of stakeholders

products created throughout the testing process

what must be met before testing can be done

approach that is simultaneous learning, test design, and test execution

determine degree to which a product meets end user approval

initial phase of validating whether a product will perform as expected

opportunity for real users to use a product in production environment to help discover bugs

ensure that previously eradicated bugs have been fixed and to catch bugs that may have appeared in a new version

software that is commercially produced and sold in a retail store or online ready to use

process of ensuring that individual units of code interact together according to specifications

done after unit testing, black box test that tests one component of a program (more than a unit)

check if previously posted bugs are rectified or not in the system

tested against certain criteria specified in a contract

testing using functions that users might perform

define all risks associated with any kind of changes made to the product under test

testing where software modules are put together then tested as a group

happens after release to production and any changes have been made to fix bugs or add new features

tests the non-functional requirements like performance, usability, reliability

testing specifically for the operational readiness

testing to confirm that a recent change has not adversely affected the existing function

testing to see if software complies with software regulations

system is developed in a linear way of several discrete and successive phases with no overlap

testing both software and hardware to evaluate the overall system behaviour

level of testing that validates the complete and fully integrated software product

groups of test activities that are organized and managed together

development style where test activities occur after all other phases and all are sequential

type of testing performed informally and randomly after formal testing is completed

used to test dynamic behaviour of software

tool-driven analysis of the code or other work products

testing by manual examining of the work products, not executing the code

testing the extreme ends or beyond accepted input values

testing method to ensure that each possible outcome of all decision branches get tested

testing all possible combinations of inputs in a decision branch

software tester using their experience to guess what the errors will likely be in a program

grouping test cases which you’d expect to all have the same output

testing based on tester’s previous experience with the current and past similar softwares

tester trying different things to see what will happen to try to find errors that may be hard to capture in other types of testing

type of testing to test the change in state of the application with varying inputs

type of white box testing that ensures all statements of the source code are executed at least once

technique to help identify test cases that cover the entire system from start to finish

process for maintaining consistency in a product

method for identifying and resolving defects

conditions that must be met before you can start testing

criteria that must be met before testing can be ended

probability of risk occurring times impact if risk did occur