2. Objective:
• Test organization
• Test Planning and Estimation
• Test Progress Monitoring and Control
• Configuration Management
• Risk and Testing
• Incident Management
3. Test organization
Test organization and Independence:
• Test Management is the project management of the test
projects.
• The effectiveness of finding defects by testing and
reviews can be improved by using independent testers.
• They may question the bugs and facts found during the
testing in an effective manner.
• The main drawback is that loosing of some responsibility
for development team.
4. Test organization
There are several level of testing levels:
i. Tests by the person who wrote the item.
ii. Tests by another person within the same team, like another
programmer.
iii. Tests by the person from some different group such as an
independent test team.
iv. Tests by a person from a different organization or company,
such as outsourced testing or certification by an external body.
5. Test organization
Profiles of Test Personnel
• Testing requires the persons with wide variety of skills and
communication.
• The roles in test process are:
– Test Manager/Lead
– Test designer
– Test automation Engineer
– Test administrator
– Testing engineer
– Technical Expert
6. Test organization
Test Manager/Lead:
• Heshe plans, monitors and controls the test project.
• Skills:
– S/w test and quality management
– Test planning and control
– Experience as project leader.
Test Designer:
• Designs the necessary test cases and sets up the order of
execution.
• Skills:
– Development and testing knowledge
– Knowledge on specification based techniques
– Knowledge on functional requirements
7. Test organization
Test Automation Engineer
• Evaluates the possibility and necessity of the test automation.
• Skills:
– Experience as a tester.
– Programming skills
– Excellent skills in operating the applied tools.
Test System Administrator:
• Set up the test environment so that it meets the system requirements
• Skills:
– System administration experience
– Knowledge on development and testing tools
– Installation and operations of various system softwares
8. Test organization
Tester
• Executes tests in accordance with the test case specifications.
• Skills
– Basic knowledge of software and testing knowledge
– Operation of testing tools.
– Experience in conducting tests.
Technical Expert
• Support the test team where necessary.
• Skills:
– Database administration
– Networking Experts
– Security experts
9. Test organization
• In addition to the above skills, test team members require:
– Willingness to question on facts.
– Strong understanding skills.
– Creativity.
– Fast learning skills.
– Skillful handling of complex situations
10. Test Planning and Estimation:
Test Planning:
• The test planning can be documented as Master plan or
separate test plans for separate test levels such as
system testing and acceptance testing.
• It is the important part of the quality assurance.
• The test plan document should follow some standards by
“Software Test Documentation”(IEEE std 829-1998).
• The different activities in test planning are:
– Test Strategy
– Resource Planning
– Priority of Tests
– Tool Support
11. Test Planning and Estimation:
Test Estimation:
• In this we will estimate the cost for testing and as the time
increases the cost of testing increases.
• The factors influencing test estimation are:
– Complexity of the project
– Time pressure
– Quality of test cases.
12. TEST PROGRESS MONITORING AND
CONTROL:
TEST PROGRESS MONITORING AND CONTROL:
• Test monitoring should be carried out on these considerations:
– Error based
– Defect detection rate
– Coverage test cases
– Cost-based metrics
• The results will be reported regularly.
13. CONFIGURATION MANAGEMENT:
CONFIGURATION MANAGEMENT
• It is the system of recording all the changes at a common place
and communicated using a defined process.
• IEEE 828 provides the standard for configuration management
system.
• It should be managed by using tools in case of larger projects,
they are:
– Cfengine
– Distelli
– CVS- Concurrent version system
• In smaller projects, tools may or may not be useful.
14. Risk and Testing
RISK
• A risk is a prediction of the possible damage or loss
incase of a negative outcome.
15. Risk and Testing
RISK Types
• There are two types of risks:
– Project risks
• An uncertain activity that can stop the project progress.
– Product risks
• The possibility that the software or the system may not behave as expected by the
customer
16. Risk and Testing
• Project risks can be classified as:
– Organizational risks
• Qualification, training to staff
• Personal problems between team/team members
• Insufficient cooperation between departments.
– Technical risks
• Wrong/incomplete requirements
• Complex test environment
– Environmental risks
• Contract issues with vendors
• Shortfall in the externally provided components like
time, quality, cost
17. Risk and Testing
• Product risks may occur from:
– Insufficient functionality of the product
– Poor data integrity and quality
– The product is not fit for the use
– The product causes damage to property.
18. INCIDENT MANAGEMENT:
INCIDENT MANAGEMENT:
• The deviation between the actual and expected outcomes will be
logged as incidents.
• Incidents may be raised during development, review, testing or use of
software product.
• A detailed report will be made for all these incidents known as
incident report.
• It may include:
– Severity of the impact on the system
– Urgency to fix
– Bugs priority area
– Status of the incident
– Expected and actual results
