Please enable JavaScript.
Coggle requires JavaScript to display documents.
slide 8 testing thought the software life - Coggle Diagram
slide 8 testing thought the software life
software development models
variant of v models exist
common type of v - model uses foru test levels
component
integration
system
acceptance
interactive incremental development model
models may ne tested several test levels during each iteration
Regression testing is increasingly important on all iterations after the first one
verification and validation can be carried out on each increment
characteristic of good testing
every development activity is corresponding testing activity
each test level has test objectives specific to that level
the analysis and design of tests for given test level should begin during the corresponding development activity
testers should be involved in reviewing document as soon as draft are available in the development life cycle
component testing
? the testing on individual software componenets
minimum software item that can be tested in isolation
test basis
component requirenment
Detailed designing
code
Typical test objects
componenet
programs
data conversion / migrations
database modules
type
done in isolation form the rest of the system
most of the time develpment environment
component testing may including
functional
non funcitonal
use
debuggin tools
testing framework
automated test case
integration testing
testing preformed to expose defects in the interface and in the interactions between integrated component or system
test basis
software and system design
architecture
workflows
user cases
typical test objects
subsystems
database implimentations
infrastructure
interface
system configuration and configuration data
info
carried out after component testing
happens
between component
hardware componenet
system and hardware
base on the project system testing can be variang
greater the scope much difficult it becomes to isolate defects to specific component of system.
type
functional
non functional
focus on A and B working together not the functionalities of A and B
system testing
the process of test and integrated system to verify that
meet the specified requirenment
concerned with testing the behaviorist of whole system
test basis
System and software requirement specification
use cases
functional specification
risk analysis report
test objects
system user and operation manuals
system configuration and configuration data
system testing environment should correspond to the final target or production environment
type
functional
black box
decision making table
whitebox
non functional
acceptance testing
acceptance testing if formal testing with
user needs
requirenment
business process
basis
user reuqirenment
system requirenments
user cases
business processes
risk analysis report
typical test objets
business process on fully integrated system
operational and maintenance process
user procedures
forms
reports
configuration data
goal of the testing
establish confidence in the sytem
finding defect "IS NOT"
happens in varies time in life cycles
typical forms of acceptance testing
user acceptance testing
operational testing
testing of backup
disaster recorvery
user management
maintaining task
data load and migration tasks
contract and regulation acceptance testing
proformed againest
government regulation
legal regulations
industry safety regulation
