Organization Structures for Single Product and Multi Product Companies – Test Planning – Test

Management – Test Process – Test Reporting

UNIT IV
ORGANIZATION Organization Structures for
Single Product and Multi
STRUCTURES Product Companies
ORGANIZATIONAL
STRUCTURES
Every Organization has a structure
There are so many organizational structures and each one have
their advantages and disadvantages.
Broadly can be categorized into
STRUCTURE THAT IS USED
FOR SMALL PROJECTS.
ADVANTAGES
The development manager has good control over project
activities.
There will be less possibility of a communication gap between the
testing and development teams.
Also in meetings, it is good for deciding the deadlines for the
development manager as he/she has complete knowledge about
the testing and development work.
Teamwork will be efficient, because of minimal layers.
DISADVANTAGES
As there is no testing manager, there is a possibility that testing
will be considered late in the project.
There is another possibility that testing will get less importance to
the project. It can be considered late in the project.
Generally in small organizations for small projects, it happens that
the development team takes more time than mentioned and the
testing team has to suffer i.e. the testing team will have to test the
product by the deadline, so that the testing team gets less time to
test the product.
THE MOST COMMONLY USED
ORGANIZATIONAL
STRUCTURE:
THE MOST COMMONLY USED
ORGANIZATIONAL
STRUCTURE:
This is the most common type of organizational structure.
In this structure, the testers are reporting to the Test Managers
and the developers are reporting to the Development Manager.
Both the Test Manager and the Development Manager are
reporting to the Project Manager.
ADVANTAGES
Unlike the previous structure, here in this structure, there are
different managers for testing and development, hence both of
them can focus on their work. They will remain dedicated to their
work and there will be fewer distractions for them.
In this structure, the testing activities cannot be neglected or it
cannot be considered late in the project. This means that both
testing and development will get equal importance.
When it comes to making critical decisions, advantageously, the
testing team has independence.
DISADVANTAGES
There is a possibility of a communication gap because of multiple
levels.
TEST MANAGEMENT
TEST MANAGEMENT
Test management is a process of managing testing activities, such
as planning, execution, monitoring and controlling activities.
It involves crucial activities that cater to both manual and
automation testing
ROLE AND
RESPONSIBILITIES
Strategic Management : strategize the whole testing process by
defining its goals, initiatives, analysing the competitive
environment, identifying benchmarks etc.,
Operational Test Management: Deals with project management,
managing external relationships like determining types of external
relationships etc.,
Test team management: Involves solving testing issues, assigning
roles to responsible individuals, deciding tools, and other such
activities
REASONS
Improve software quality by setting up well-defined outlines.
Test data for teams are easily accessible for team working at
different locations
Manging software’s increasing complexities and attributes
Reduces coding and designing errors
Ensures effective and efficient usage of test resources
Helps complete projects within deadlines
TEST REASONS
1) Test Organization
Independent Testing
Tasks of Test Leader and Tester

2) Test Planning and Estimation

Test Planning
Test Approaches
Entry and Exit Criteria
TEST REASONS
3) Test Progress Monitoring and Control
Test Monitoring
Test Reporting and Control
Test Summary Report

4) Risks & Testing

Risk Probility / Likelihood & Impact
Project & Product Risks
Risk Based Testing Approach
TEST REASONS
5) Configuration Management
6) Incident Management
BEST PRACTICES OF TEST
MANAGEMENT
Start test management activities early
The process of software testing should be iterative
Testers should reuse test artifacts as it improves the efficiency of
testing
Utilize requirement based testing
Automate to save time
Coordinate and integrate with the development team
TEST MANAGEMENT TOOLS
qTest
QAComplete
PractiTest
Meliiora Testlab
TEST PLANNING
INTRODUCTION
A Test Plan is a detailed document that describes the test strategy,
objectives, schedule, estimation, deliverables, and resources
required to perform testing for a software product.
Test Plan helps us determine the effort needed to validate the
quality of the application under test. The test plan serves as a
blueprint to conduct software testing activities as a defined
process, which is minutely monitored and controlled by the test
manager.
DEFINATION
Test Plan is A document describing the scope, approach, resources,
and schedule of intended test activities.
IMPORTANCE OF TEST PLAN
Help people outside the test team such as developers, business
managers, customers understand the details of testing.
Test Plan guides our thinking. It is like a rule book, which needs to
be followed.
Important aspects like test estimation, test scope, Test Strategy are
documented in Test Plan, so it can be reviewed by Management
Team and re-used for other projects.
SEVEN STEPS TO WRITE A
TEST PLAN
1. Analyze the product
2. Design the Test Strategy
3. Define the Test Objectives
4. Define Test Criteria
5. Resource Planning
6. Plan Test Environment
7. Schedule & Estimation
8. Determine Test Deliverables
STEP 1) ANALYZE THE
PRODUCT
How can you test a product without any information about it? The answer is
Impossible. You must learn a product thoroughly before testing it.

The product under test is a banking website. You should research clients and
the end users to know their needs and expectations from the application

• Who will use the website?

• What is it used for?
• How will it work?
• What are software/ hardware the product uses?
You can use the following approach to analyze the site
STEP 1) ANALYZE THE
PRODUCT
STEP 2) DEVELOP TEST
STRATEGY
Test Strategy is a critical step in making a Test Plan in Software
Testing. A Test Strategy document, is a high-level document, which
is usually developed by Test Manager. This document defines:

• The project’s testing objectives and the means to achieve

them
• Determines testing effort and costs
Back to your project, you need to develop Test Strategy for testing
that banking website. You should follow steps below
STEP 2) DEVELOP TEST
STRATEGY
STEP 2.1) DEFINE SCOPE OF
TESTING
The components of the system to be tested (hardware, software,
middleware, etc.) are defined as "in scope"
The components of the system that will not be tested also need to
be clearly defined as being "out of scope."
STEP 2.2) IDENTIFY TESTING
TYPE
 STEP 2.3) DOCUMENT RISK
& ISSUES
Risk Mitigation
Team member lack the required Plan training course to skill up your members
skills for website testing.
The project schedule is too tight; Set Test Priority for each of the test activity.
it's hard to complete this project
on time
Test Manager has poor Plan leadership training for manager
management skill
A lack of cooperation negatively Encourage each team member in his task, and
affects your employees' inspire them to greater efforts.
productivity
Wrong budget estimate and cost Establish the scope before beginning work, pay
overruns a lot of attention to project planning and
constantly track and measure the progress
STEP 2.4) CREATE TEST
LOGISTICS
STEP 3) DEFINE TEST
OBJECTIVE
Test Objective is the overall goal and achievement of the test
execution. The objective of the testing is finding as many software
defects as possible; ensure that the software under test is bug free
before release.

To define the test objectives, you should do 2 following steps

1. List all the software features (functionality, performance,

GUI…) which may need to test.
2. Define the target or the goal of the test based on above
features
STEP 4) DEFINE TEST
CRITERIA
Test Criteria is a standard or rule on which a test procedure or test judgment
can be based. There’re 2 types of test criteria as following

Suspension Criteria
Specify the critical suspension criteria for a test. If the suspension criteria are
met during testing, the active test cycle will be suspended until the criteria
are resolved.

Test Plan Example:

If your team members report that there are 40% of test cases failed, you
should suspend testing until the development team fixes all the failed cases.
STEP 4) DEFINE TEST
CRITERIA
Exit Criteria
It specifies the criteria that denote a successful completion of a test
phase. The exit criteria are the targeted results of the test and are
necessary before proceeding to the next phase of development.
Example: 95% of all critical test cases must pass.
STEP 5) RESOURCE
PLANNING
Resource plan is a detailed summary of all types of resources
required to complete project task. Resource could be human,
equipment and materials needed to complete a project

The resource planning is important factor of the test planning

because helps in determining the number of resources (employee,
equipment…) to be used for the project. Therefore, the Test
Manager can make the correct schedule & estimation for the
project.
STEP 6) PLAN TEST
ENVIRONMENT
A testing environment is a setup of software and hardware on which the testing
team is going to execute test cases. The test environment consists of real business
and user environment, as well as physical environments, such as server, front end
running environment.

Here’re some recommended questions. Of course, you can ask the other questions
if you need.

• What is the maximum user connection which this website can handle at the
same time?
• What are hardware/software requirements to install this website?
• Does the user's computer need any particular setting to browse the website?
STEP 7) SCHEDULE &
ESTIMATION

Task Members Estimate

effort
Create the test Test Designer 170 man-
specification hour
Perform Test Tester, Test 80 man-hour
Execution Administrator
Test Report Tester 10 man-hour
Test Delivery 20 man-hour
Total 280 man-
hour
STEP 8) TEST DELIVERABLES

 Test plans document.  Test Scripts  Test Results/reports

  Simulators.  Defect Report
Test cases documents
  Test Data  Installation/ Test procedures guidelines
Test Design specifications.
 Test Traceability Matrix  Release notes
 Error logs and execution logs.
TEST PROCESS
THE FUNDAMENTAL OF TEST
PROCESS IN SOFTWARE
TESTING:
1. Test Planning and Control
2. Test Analysis and Design
3. Test implementation and execution
4. Evaluating exit criteria and Reporting
5. Test closure activities
TEST PLANNING AND
CONTROL
1. Deciding the scope and risk of testing
2. Deciding the overall approach of testing
3. Scheduling test analysis and design process
4. Assigning resources to different activities
TEST ANALYSIS AND DESIGN
Test Analysis and Design is a Fundamental Test Process which
creating test conditions & test cases.
TEST IMPLEMENTATION AND
EXECUTION
1. Creating test suites from test executions
2. Checking test environments, updating traceability between
test basis and test cases
3. Executing test procedures using test execution tools
4. Checking actual result with expected results
5. Reporting errors & creating Incident reports
EVALUATING EXIT CRITERIA
AND REPORTING
Evaluating exit criteria is a process defining when to stop testing.
TEST CLOSURE ACTIVITIES
Test closure activities are the last process in the fundamental test
process.

Things to be done…
1. Ensure that deliverable has been delivered or not
2. Closing incident report
3. Documenting all the systems
4. Archiving all the testware, test environment and
infrastructure.
TEST REPORTING
TEST REPORT
Test Report is a document which contains a summary of all test
activities and final test results of a testing project.

Test report is an assessment of how well the Testing is performed.

Based on the test report, stakeholders can evaluate the quality of

the tested product and make a decision on the software release.
THE TYPICAL BENEFITS OF A
TEST REPORT INCLUDE:
WHAT DOES A TEST REPORT
CONTAIN?
PROJECT INFORMATION
TEST OBJECTIVE
As mentioned in Test Planning tutorial, Test Report should include
the objective of each round of testing, such as Unit Test,
Performance Test, System Test …Etc.
TEST SUMMARY
Covers
1. The number of test cases executed
2. The numbers of test cases pass
3. The numbers of test cases fail
4. Pass percentage
5. Fail percentage
6. Comments
DEFECT
One of the most important information in Test Report is defect. The
report should contain following information

1. Total number of bugs

2. Status of bugs (open, closed, responding)
3. Number of bugs open, resolved, closed
4. Breakdown by severity and priority
REQUISITES FOR A GOOD
REPORT
Detail: You should provide a detailed description of
the testing activity, show which testing you have
performed. Do not put the abstract information into
the report, because the reader will not understand
what you said.
Clear: All information in the test report should be
short and clearly understandable.
Standard: The Test Report should follow the
standard template. It is easy for stakeholder to
review and ensure the consistency between test
reports in many projects.
Specific: Do not write an essay about the project
activity. Describe and summarize the test result
specification and focus on the main point.