ISTQB CTFL pdf studying

test basis

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

test conditions

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

test cases

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

test procedures

formal specification of test cases

test suites

collection of test cases that are grouped for test execution purposes

coverage

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

debugging

finding or fixing errors in the source code of software

defect

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

error

mistake in coding

failure

inability of a software to perform its required function

root cause

first point that started to cause a defect

test analysis

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

test control

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

test data

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

test design

describes how testing should be done

test execution

process of performing test cases to identify problems

test implementation

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

test monitoring

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

test object

reference to an object currently being tested in the software

test objective

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

test oracle

mechanism that determines whether software executed correctly for a test case

test planning

define objectives for testing and an approach for meeting test objectives

test procedure

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

testware

all of the materials to perform a test

traceability

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

validation

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

work products

products created throughout the testing process

exit criteria

what must be met before testing can be done

exploratory testing

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

acceptance testing

determine degree to which a product meets end user approval

alpha testing

initial phase of validating whether a product will perform as expected

beta testing

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

change related testing

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

COTS

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

component integration testing

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

component testing

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

confirmation testing

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

contract acceptance testing

tested against certain criteria specified in a contract

functional testing

testing using functions that users might perform

impact analysis

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

integration testing

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

maintenance testing

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

non functional testing

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

operational acceptance testing

testing specifically for the operational readiness

regression testing

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

regulatory acceptance testing

testing to see if software complies with software regulations

sequential development model

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

system integration testing

testing both software and hardware to evaluate the overall system behaviour

system testing

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

test level

groups of test activities that are organized and managed together

waterfall

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

ad hoc testing

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

dynamic testing

used to test dynamic behaviour of software

static analysis

tool-driven analysis of the code or other work products

static testing

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

boundary value analysis

testing the extreme ends or beyond accepted input values

decision coverage

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

decision table testing

testing all possible combinations of inputs in a decision branch

error guessing

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

equivalence partitioning

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

experience-based test technique

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

exploratory testing

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

state transition testing

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

statement coverage

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

use case testing

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

configuration management

process for maintaining consistency in a product

defect management

method for identifying and resolving defects

entry criteria

conditions that must be met before you can start testing

exit criteria

criteria that must be met before testing can be ended

risk level

probability of risk occurring times impact if risk did occur

risk based testing