Please enable JavaScript.
Coggle requires JavaScript to display documents.
slide 10 test designing - Coggle Diagram
slide 10 test designing
test condition
item or event
could be
verified
one or more test cases
tracebility
to trace
condition to
specification and requirement
benifit
analysis when the
requirement changes
test coverage (cases) request for one requirement
test designing
consiste
input values
pre conditon
input value setting
or environment condition
expected result
identify using requirement specification
ideally be
defined prior
to test designing and
execution
post condition
test implimentation
based on the test procedural specifies the sequence of action for the execution of a test
execution
tools
manual
automated
test execution schedule
order
when
whom
test designing techniques
purpose
identify test condition
test cases
test data
black box
functional
non functional
level
componenet
intergration
system
do not need any information about the internal structure
techniques
equivalence partitioning
input devide to similer behaviour
believe they work simillary
valid and invalid
select one input from each partitioning
can identify as
outputs
internal value
time - related value
all test level
boundary value analysis
checking boundary values
maximum
minimum
decision table testing :
good for business
state transition testing
exhibit different response depending on current conditions or previous
parts
states
transition
input or events
action
state table
show the relationship between highlight possible transition that are invalid
valid and invalid transition
not only software suitable for bussiness solution
user case testing
interaction between actor and the sytsem
can use in any level but most sutiabel for
system
and
aceptance
requirest pre and post condition to be work successfully
terminate with post conditional which are the observable result and final sates of the system after the user case has been completed
white box
test logical structure of the code
can messure against the test cases
techniques
statement testing cover
smallest area to executed
decision testing and coverage
advance veriosn of statement testing
decision coverage is stronger than statement coverage
experience based techniques
ERROR GUIESING
experience people drive the test case
knowledge of the testers developers user and other stakeholders about the software ei'st usage and it's environment is one source of information
knowledge can be another source
how to do it (
fault attack
)
list down possible defects
designing testing that attack these defects
based on
experience
common knowledge about why software fails
available defect and failure data
method
Exploratory testing
test designing
test execution
test logging and learning
key element
product exploration : what is the product suppose to do
test design how are we going to tackel the problem
test execution : do we thing it works
heuristics : guidedline rules on the what and hos ?
review able results do the result meet the requirement and can we provide it
choosing test techiniques
type of system
regulatory standards
customer requirement
level of risk
test objectives
documentation available
knowledge of the testers
time and budget
user case models and previous experience with types of defect found