Please enable JavaScript.
Coggle requires JavaScript to display documents.
Foundation - Coggle Diagram
Foundation
fundamentals
what
objectives
why
reduce risks
increase
efficient
with least effort
effective
work correctly
QA
process
QC
similar terms
errors
ppl make mistakes
defects
errors may create defects
types
functional
non-functional
failures
false negative
false positive
root causes
test coverage
7 principles
1 - no bugs found >< bug free
2 - can't exhaustive test
3 - early testing
4 - defect cluster
8/2
5 - pesticide paradox
6 - context dependent
7 - no bugs >< meet business's needs
exit criteria
def of done
acception testing
who
user, customer
yes or no
forms
user
operational
contract & regulation
alpha & beta
process
planning & mornitoring
analysis & design
what
testable features
test conditions
how
test basis
UML ...
requirement spec
activities
ambiguties
omissions
inconsistencies
analysis
what to test
design
how to test
execution
static testing
what
no executing code
how
by tools
review process
planning
initiate
individual
issue communication & analysis
fixing & reporting
when
build and delivery
security
vs dynamic
find defects
not finding failure
software life
models
waterfall
need detailed req
test at the end
v-model
early testing
interative incremental
1 iteration
agile
constant customer's involvement
keys
ppl
value
flexible
smart planning
test levels
unit
how
stub
fake injection
driver
caller
intergration
component's interaction
system
accpetance
test types
functional
security
inter
non-functional
perf
load
single transaction many times
stress testing
tough cases
usability
easy to use
maintainability
reliability
portability
structural
whitebox
changes related
regression
backward
re-testing
maintenance testing
live env
test design
what
test conditions
test data
test cases
categories
white
what
structure based
techniques
statement
run all statements
at least one
coverage 100%
still weakest
decision
decision outcomes
x / total branches
black
software is a box
focus
input - output
spec
behavior
techniques
equivalence partitioning
1 value for each
types
valid
invalid
tested separatedly
failures masked
3 points
coverage
discrete
multiple conditions
boundary value
2-value
3-value
decision table
state transition
diagram
table
use case
scenario
system
actors
business level
experience based
what
similar system
types
error guessing
exploratory
mixed concurrently
checklist
high level