Please enable JavaScript.
Coggle requires JavaScript to display documents.
slide 12 Test management ( not completer) - Coggle Diagram
slide 12 Test management ( not completer)
test organization and independence
No independent testers ; developere test their own code
indedpendent testers within the development team
independent test team or group within the organization reporting to project management or executive management
bussiness organization or user community
from specilized area such as userbility testers , security testers or ceticfication testers.
independent testers orusource or external to the organization
development staff may participate in testing , especially at the lower level but there lack of objectivity often limited their effectiverness
independent testers may have the authority to require and define test process and rules
task of the test learders
sometimes called test manaer
role proforme by
project manger
a development manager
quelity assurance manger
manager of a test group
larger project contain
test leader
test manager
task
coordinate the test strategy and plan with project namgers and others
write the rewive stratergy for the prooject nad test policy
plan the test
initialte the specification , preparation , implementation and execution
monitor test result
adapt planning based on test result and progress
take action for instance
introduce suitable metric for measuring test progress
evaluating the quality of the testing and the product
select tools and environment
write test summery
tester
task
analyse requirement and specification
test speficificaiton
set up the test environment
prepare and acquire test data
evaluate the result and document the deviations from expected result
user required tools
measure preformance of components and systems
deploy test activity
test analysis
test design
specific test types
test automation
depend on the test level testers can keeping some degree of independence
test planning
test planning covers development and implementation projects and maintenance activities
documentaton
a master test plan
sepaate test planes for test level such as system testing and acceptance tseting
planning inluenced by
the test policy of the organization
the scope of testing
test objectives
risk
constaints
testablility
availability of resources
test planning activities
deteining the scope and resk identifying the objective of testing
test level and entry
testing activities
test what roles will perform the test activities
entry cirteria
exist criteria
test estimation
the metrics based approach
based on the similar project create the matrix
the expert based approach
error guessing
testing effort
characteristic of the product
characteristics of the development process
outcome of the testing
test strategy
Analytical approaches
direct to greater risk
model-based approaches such as stochastic testing using statistical information
methodical approaches
process or standard compliant approaches
dynamic and heuristic approaches
consultative approaches
test monitor
provide feedback and visibility about test activity
collect automatically and manually
use metrics
precentage of work done
case execurtion
environment preparation
test coverage of requirements
date of test milestone
testing cost , includinng the cost comapre to the benifit
reporting
summery of the test
exit criteria were met
recommendation and decision about the future
economic benefit of continued testing
outstanding risks and the level of confidence
project risk
organization
skill , trainging staff shortages
presonnel issues
political issues
problem with testers communicating their need and test result
failier inforamation
technical issues
requirement
testing enviroment
low quelity of designing
data conversion
supplier issues
failure of a third party
contractual issues
facing using well establish project management principles
product risk
potential failure areas in the software or system are known as product risk
failure prone software devliered
the potential that the softwear / hardware error
poor characteristic ( preformance )
functional error
MAIN KEY TO SUCCESS OF A PROJECT
approch :
incident
any significant unplanned event that occurs ducting testing or any other event
fault
software fault
expected result incorrect
test was not preformed correctly
code error
discrepancies between actual and expected outcome need to be logged as incidents
report
date of issues
expected and actual result
identification of the test item and environment
software of system life cycle process in which the incident was objserved
databse dumps including logs screen shots
stack holder intrest
severity of the impact on the system
urgency / priority to fix
states of indeiciend
conclution , reconemed
change history base on the action
globle issues