MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

LOKNETE GOPINATHJI MUNDE

INSTITUTE OF ENGINEERING EDUCATION &
RESEARCH, NASHIK.

MICRO PROJECT
Academic year: 2023-24

TITLE OF PROJECT

TEST MANAGEMENT AND TEST

PLANNING.

Program: Program code:

Course: Course code:

1
 CERTIFICATE

This is to certify that Mr./Ms. Manasi Sandesh Khairnar Roll No:

07 of Fifth Semester of Diploma in Computer Engineering of
Institute, LOKNETE GOPINATHJI MUNDE INSTITUTE OF
ENGINEERING EDUCATION & RESEARCH, NASHIK
(Code: 1477) has completed the Micro Project satisfactorily in
Subject – STE (22518)for the academic year 2023- 2024 as
prescribed in the curriculum.

Place: Nashik Enrollment No:

Date: Exam Seat No:

Subject Teacher Head of Department Principal

Seal of institute
2
 WEEKLY PROGRESS REPORT
MICRO PROJECT
-

SIGN OF
SR.NO. WEEK ACTIVITY PERFORMED DATE
GUIDE

Discussion and finalization of

1 1st topic

Preparation and submission

2 2nd of Abstract

3 3rd Literature Review

4th and 5th Collection of Data

4
5 6th and7th Collection of Data

Discussion and outline of

8th and 9th
6 Content

7 Formulation of Content
10th

Editing and proof Reading

11th and 12th
8 of Content

Compilation of Report &

9 13th Presentation

Seminar
10 14th

Viva voce
11 15th
Final submission of Micro
12 16th Project

Sign of the student Sign of the faculty

3
 INDEX
PAGE
SR.NO. NO.
CONTENT

Chapter 1 Acknowledgement

Chapter 2 Test planning

Chapter 3 Test management

References,conclusion
Chapter 4

4
 Acknowledgement
1. I am very thanking full to Loknete Gopinathji Munde
Institute of Engineering who has given me opportunity
to have project knowledge of Professional practices.
2. I am also thankful to the means for providing me the
information of Professional Practices which is the
base of the Project.
3. Lastly I am thankful to my subject teacher for proper
guidance and co-operative in preparation of the
project work.

5
 TEST PLANNING

What is a Test Plan? A Test Plan is a detailed document that catalogs

the test strategies, objectives, schedule, estimations, deadlines, and
resources required to complete that project. Think of it as a blueprint for
running the tests needed to ensure the software is working correctly –
controlled by test managers.

A test plan is a document that consists of all future testing-related

activities. It is prepared at the project level and in general, it defines
work products to be tested, how they will be tested, and test type
distribution among the testers. Before starting testing there will be a test
manager who will be preparing a test plan. In any company whenever a
new project is taken up before the tester involves in the testing the test
manager of the team would prepare a test Plan.
 The test plan serves as the blueprint that changes according to the
progressions in the project and stays current at all times.
 It serves as a base for conducting testing activities and coordinating
activities among a QA team.
 It is shared with Business Analysts, Project Managers, and anyone
associated with the project.

Objectives of the Test Plan

 Overview of testing activities: The test plan provides an overview

of the testing activities and where to start and stop the work.
 Provides timeline: The test plan helps to create the timeline for the
testing activities based on the number of hours and the workers
needed.
 Helps to estimate resources: The test plan helps to create an
estimate of the number of resources needed to finish the work.
 Serves as a blueprint: The test plan serves as a blueprint for all the
testing activities, it has every detail from beginning to end.
 Helps to identify solutions: A test plan helps the team members to
consider the project’s challenges and identify the solutions.

6
 Serves as a rulebook: The test plan serves as a rulebook for
following rules when the project is completed phase by phase.

Importance of Test Plan:

The following are some of the key benefits of making a test plan:
 Quick guide for the testing process: The test plan serves as a quick
guide for the testing process as it offers a clear guide for QA
engineers to conduct testing activities.
 Helps to avoid out-of-scope functionalities: The test plan offers
detailed aspects such as test scope, test estimation, strategy, etc.
 Helps to determine the time, cost, and effort: Test serves as the
blueprint to conduct testing activities thus it helps to deduce an
estimate of time, cost, and effort for the testing activities.
 Provide a schedule for testing activities: A test plan is like a rule
book that needs to be followed, it thus helps to schedule activities
that can be followed by all the team members.
 Test plan can be reused: The test plan documents important aspects
like test estimation, test scope, and test strategy which are reviewed
by the Management Team and thus can be reused for other projects.

Test Plan Components/ Attributes:

There is no hard and fast rule for preparing a test plan but it has
some standard 15 attributes that companies follow:

7
1. Objective: It describes the aim of the test plan, whatever the good
process and procedure they are going to follow in order to give quality
software to customers. The overall objective of the test is to find as
many defects as possible and to make software bug free. The test
objective must be broken into components and sub-components. In
every component following activities should be performed.
 List all the functionality, and performance to be tested.
 Make goals and targets based on the application feature.

2. Scope: It consists of information that needs to be tested with respect

to an application. The scope can be divided into two parts:
 In-Scope: The modules that are to be tested rigorously.
 Out Scope: The modules that are not to be tested rigorously.
Example: In an application A, B, C, and D features have to be
developed, but the B feature has already been designed by other
companies. So the development team will purchase B from that
company and perform only integrated testing with A, B, and C.

3. Testing Methodology: The methods that are going to be used for

testing depend on application to application. The testing methodology is
decided based on the feature and application requirements.
Since the testing terms are not standard, one should define what kind of
testing will be used in the testing methodology. So that everyone can
understand it.

4. Approach: The approach of testing different software is different. It

deals with the flow of applications for future reference. It has two
aspects:
 High-Level Scenarios: For testing critical features high-level
scenarios are written. For Example, login to a website, and book from
a website.
 The Flow Graph: It is used when one wants to make benefits such
as converging and merging easy.

5. Assumption: In this phase, certain assumptions will be made.

 The testing team will get proper support from the development team.

8
 The tester will get proper knowledge transfer from the development
team.
 Proper resource allocation will be given by the company to the
testing department.

6. Risk: All the risks that can happen if the assumption is broken. For
Example, in the case of wrong budget estimation, the cost may overrun.
Some reason that may lead to risk is:
 Test Manager has poor management skills.
 Hard to complete the project on time.
 Lack of cooperation.

7. Mitigation Plan: If any risk is involved then the company must have
a backup plan, the purpose is to avoid errors. Some points to
resolve/avoid risk:
 Test priority is to be set for each test activity.
 Managers should have leadership skills.
 Training course for the testers.

8. Roles and Responsibilities: All the responsibilities and role of every

member of a particular testing team has to be recorded.
Example:
 Test Manager: Manages the project, takes appropriate resources and
gives project direction.
 Tester: Identify the testing technique, verify the test approach, and
save project costs.

9. Schedule: Under this, it will record the start and end date of each and
every testing-related activity. For Example, writing the test case date
and ending the test case date.

10. Defect Tracking: It is an important process in software engineering

as lots of issue arises when you develop a critical system for business. If
there is any defect found while testing and that defect must be given to
the developer team. There are the following methods for the process of
defect tracking:

9
 Information Capture: In this, we take basic information to begin the
process.
 Prioritize: The task is prioritized based on severity and importance.
 Communication: Communication between the identifier of the bug
and the fixer of the bug.
 Environment: Test the application based on hardware and software.
Example: The bug can be identified using bug-tracking tools .

10
How to Write a Test Plan:

Below are the eight steps that can be followed to write a test plan:

1. Analyze the product: This phase focuses on analyzing the product,

Interviewing clients, designers, and developers, and performing a
product walkthrough. This stage focuses on answering the following
questions:
 What is the primary objective of the product?
 Who will use the product?
 What are the hardware and software specifications of the product?
 How does the product work?

2. Design the test strategy: The test strategy document is prepared by

the manager and details the following information:
 Scope of testing which means the components that will be tested and
the ones that will be skipped.
 Type of testing which means different types of tests that will be used
in the project.
 Risks and issues that will list all the possible risks that may occur
during testing.
 Test logistics mentions the name of the testers and the tests that will
be run by them.

3. Define test objectives: This phase defines the objectives and

expected results of the test execution. Objectives include:
 A list of software features like functionality, GUI, performance
standards, etc.
 The ideal expected outcome for every aspect of the software that
needs testing.

4. Define test criteria: There are two main testing criteria that govern
all the activities in the testing project:
 Suspension criteria: Suspension criteria defines the benchmarks for
suspending all the tests.
 Exit criteria: Exit criteria defines the benchmarks that signify the
successful completion of the test phase or project. These are expected
11
 results and must match before moving to the next stage of
development.

5. Resource planning: This phase aims to create a detailed list of all the
resources required for project completion. For example, human effort,
hardware and software requirements, all infrastructure needed, etc.

6. Plan test environment: This phase is very important as the test

environment is where the QAs run their tests. It is important that the test
environments are real devices, installed with real browsers and
operating systems so that testers can monitor software behavior in real
user conditions.
7. Schedule and Estimation: Break down the project into smaller tasks
and allocate time and effort for each task. This helps in efficient time
estimation. Create a schedule to complete these tasks in the designated
time with a specific amount of effort.

8. Determine test deliverables: Test deliverables refer to the list of

documents, tools, and other equipment that must be created, provided,
and maintained to support testing activities in the project.

12
 TEST MANAGEMENT

Test Management :

Test Management is a process where testing activities are managed to

ensure high-quality and high-end testing of software applications. This
method consists of tracking, organization, controlling processes and
checking the visibility of the testing process to deliver a high-quality
software application. It makes sure the software testing process runs as
expected.

Test Management Process :

It is a software process that manages the start to the end of all software
testing activities. This management process provides planning,
controlling, tracking, and monitoring facilities throughout the whole
group cycle, these process includes several activities like test case
design and test execution, test planning, etc. It also gives an initial plan
and discipline specifications for the software testing process.

Responsibilities:

 Works in collaboration with test analyst and technical test analyst to

select and customize the appropriate templates and also establish
standards.
 Provides all facilities to keep track and control the testing throughout
the project.
 Gives a clear concept of understanding the testing activity of the
prior upcoming project and also posts one
The test management process has two main parts of test
Management Process:

Planning :
 Risk analysis
 Test Estimation
 Test planning

13
Execution :
 Testing Activity
 Issue Management
 Test report and evolution

The activity of the test process :

1. Test plan –
Rough sketches serve as test plans to convey the process of testing.
Gives a clear vision of the complete testing process.

2. Test design –
Test design affords the implementation process of testing.

3. Test execution –

It shows the actual system results against the expected result during
test execution.

4. Exit criteria –
It gives the signal when to stop the test execution process.

5. Test reporting –
Test reporting picturizes the test process and result for the particular
testing cycle.

14
What is test infrastructure management in software testing?

Test Infrastructure refers to tasks, events, activities, and processes that

facilitate and support manual and automated testing. Better planned and
implemented infrastructure provides stability, reliability, and testing
continuity.

Every software requires an infrastructure to perform its actions.

Infrastructure testing is the testing process that covers hardware,
software, and networks. It involves testing any code that reads
configuration values from different things in the IT framework and
compares them to intended results.

It reduces the risks of failure. This testing incorporates testing exercises,

and procedures to guarantee that IT applications and the fundamental
infrastructure are tuned to deliver on execution, adaptability, unwavering
quality, accessibility, performance, and scalability. The aim is to test
infrastructure between test environments, test tools, and office
environments.

15
 CONCLUSION:

We have successfully done this micro project on the topic the test
management and test planning . Accordingly we learnt what kind
of processes it follows while planning and managing the
software.
Lastly thanking our subject teacher for guiding us and helping us
in understanding the same.

16
 REFERENCES

1) WWW.GOGGLE.COM.

2)TECH KNOWLEDGE TEXTBOOK (STE).

17