MICRO PROJECT

Academic year
2020-21

Prepare Test Plan and Design Test Cases to perform

Black Box Testing of TataCLIQ

Program: Computer Engineering Program code: CO5I

Course: Software Testing Course code: 22518

 MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

Certificate

This is to certify that Mr. /Ms. DIMPLE RATHORE, SAGAR SURESH, OMKAR SHINDE,

SAIF SYED Roll No. 49, 50, 51, 52 of fifth. Semester of Diploma in Computer Engineering of

Institute, VES POLYTECHNIC (Code:0004) has completed the Micro Project satisfactorily in

Subject Software Testing (22518) for the academic year 2020- 2021 as prescribed in the

curriculum.

Place: Mumbai Enrollment No: 1800040289, 1800040290,

1800040292, 1800040293

Date: ……………………… Exam Seat No: ………………………….

Subject Teacher Head of the Department Principal

INDEX
Academic year: 2020-21 Name of the faculty: Mrs. Shubhangi Chintawar

Program code: CO5I-B Course & course code: STE (22518)

Roll No.: 49, 50, 51, 52 Enrollment No.:1800040289, 1800040290, 1800040292, 1800040293

Name of the candidate: DIMPLE RATHORE, SAGAR SURESH, OMKAR SHINDE, SAIF SYED

Sr. No Content Page No.

1 Project Proposal

2 Action plan

3 Resource required

4 Introduction

5 Actual Procedure

6 Output

7 Skill developed

8 Evaluation sheet
 Annexure – I

Micro-Project Proposal

Prepare Test Plan and Design Test Cases to perform Black Box Testing of TataCLIQ

1.0 Aim/Benefits of the Micro-Project

This Micro-Project aims at:
1. Prepare a test case for the given application.
2. Apply specified testing level for the given application.
3. Identify the resources requirement of the given application.
4. Prepare test plan for the given application.
5. Prepare defect reports for the given application.

2.0 Course Outcomes Addressed

A: Apply various software testing methods. [ ✔ ]
B: Prepare test cases for different types and levels of testing. [ ]
C: Prepare test plan for an application [ ✔ ]
D: Identify bugs to create defect reports for given application. [ ]
E: Test software for performance measures using automated testing tools. [ ]

3.0 Proposed Methodology

Software Testing Life Cycle (STLC) discusses the STLC steps, stages and phases a software
undergo during the testing process. Though, there is no fixed standard of the software or application
undergoing STLC, and it varies from region to region throughout the world.
4.0 Action Plan
Sr. Details of activity Planned Planned Name of Responsible
No. Start date Finish date Team Members

1 Finalization of project Title and ALL TEAM MEMBERS

Scope

2 Application Overview ALL TEAM MEMBERS

3 Test Planning ALL TEAM MEMBERS

4 Test case development ALL TEAM MEMBERS

5 Test Environment setup ALL TEAM MEMBERS

6 Test Execution ALL TEAM MEMBERS

7 Test Reporting ALL TEAM MEMBERS

8 Demonstration of project and final ALL TEAM MEMBERS

submission

5.0 Resources Required

Sr. No. Equipment Name with Broad Specification Remark if any

1 Computer (i3-i5 preferable), RAM minimum 2 GB and onwards, HDD ✔

free Space 1GB or More

2 Windows 7 or latest/LINUX version 5.0 or later ✔

3 Any automated testing tool (Freeware like selenium)

Name of Team Members with Roll Nos.

1. DIMPLE RATHORE - 49
2. SAGAR SURESH - 50
3. OMKAR SHINDE - 51
4. SAIF SYED - 52
Mrs. Shubhangi Chintawar
Name and Signature of Course Teacher
 Annexure – II

Micro-Project Report

Prepare Test Plan and Design Test Cases to perform Black Box Testing of TataCLIQ

1.0 Rationale
Software testing helps in finalizing the software application or product against business and user
requirements. It is very important to have good test coverage in order to test the software application
completely and make it sure that it’s performing well and as per the specifications. While
determining the test coverage the test cases should be designed well with maximum possibilities of
finding the errors or bugs. The test cases should be very effective.

2.0 Aim/Benefits of the Micro-Project

This Micro-Project aims at:
1. Prepare a test case for the given application.
2. Apply specified testing level for the given application.
3. Identify the resources requirement of the given application.
4. Prepare test plan for the given application.
5. Prepare defect report for the given application.

3.0 Course Outcomes Addressed

A: Apply various software testing methods. [ ✔ ]
B: Prepare test cases for different types and levels of testing. [ ]
C: Prepare test plan for an application [ ✔ ]
D: Identify bugs to create defect reports for given applications. [ ]
E: Test software for performance measures using automated testing tools. [ ]

4.0 Literature Review

White Box Testing:
White Box Testing is based on the knowledge about the internal logic of an application’s code.
It is also known as Glass box Testing. Internal software and code working should be known for
performing this type of testing. Under these tests are based on the coverage of code statements,
branches, paths, conditions, etc.
Black Box Testing
Internal system design is not considered in this type of testing. Tests are based on the requirements
and functionality.
Unit Testing:
Testing of an individual software component or module is termed as Unit Testing. It is typically
done by the programmer and not by testers, as it requires detailed knowledge of the internal program
design and code. It may also require developing test driver modules or test harnesses.

Integration Testing:
Testing of all integrated modules to verify the combined functionality after integration is termed
as Integration Testing.
Modules are typically code modules, individual applications, client and server applications on a
network, etc. This type of testing is especially relevant to client/server and distributed systems.

System Testing:
Under the System Testing technique, the entire system is tested as per the requirements. It is a
Black-box type Testing that is based on overall requirement specifications and covers all the
combined parts of a system.

Regression Testing:
Testing an application as a whole for the modification in any module or functionality is termed as
Regression Testing. It is difficult to cover all the system in Regression Testing, so
typically Automation Testing Tools are used for these types of testing.

Static Testing:
Static Testing is a type of testing which is executed without any code. The execution is performed on
the documentation during the testing phase.
It involves reviews, walkthrough, and inspection of the deliverables of the project. Static Testing
does not execute the code instead of the code syntax, naming conventions are checked.

5.0 Actual Procedure Followed.

1. Application overview

2. Test Planning

3. Test case development

4. Resource requirement and Test Environment setup

5. Test execution

6. Test reporting
6.0 Actual Resources Used
Sr. No. Equipment Name with Broad Specification Remark if any

1 Computer (i3), RAM minimum 2 GB and onwards ✔

2 Windows XP/windows 7 ✔

3 Automation tool

7.0 Outputs of the Micro-Projects

(Students are expected to attaché printout of Defect Reports for Micro project topic)
8.0 Skill Developed / learning out of this Micro-Project
1. Defect tracking and reported the bugs
2. Creating Test cases and Test Scenarios
3. Applying Testing Tools and Technologies.
4. Documentation of Project
5. Time management
6. Technical Writing
7. Team work
8. Problem solving

9.0 Application of this Micro-Project

It is used to apply techniques, strategies, methods for testing the product to identify defects and its
reporting.
 Annexure – III

Suggested Rubric for Assessment of Micro-Project

Sr. Characteristic to Poor Average Good Excellent
No. be assessed ( Marks 1 - 3 ) ( Marks 4 - 5 ) ( Marks 6 - 8 ) ( Marks 9- 10 )

Relevance to the Relate to very Related to some Take care of at-least Take care of more
1
course few LOs LOs one CO than one CO

Literature Not more than At-least 5

About 10 relevant
review two sources relevant At –least 7 relevant
2 sources, most
/information very old sources, at least sources, most latest
latest
collection reference 2 latest

Completion of the
Completed less Completed 50 Completed 60 to Completed more
3 Target as per
than 50% to 60% 80% than 80 %
project proposal

Sufficient and
Data neither appropriate Sufficient and
Enough data
organized nor enough data appropriate enough
Analysis of Data collected and
4 presented well generated but data generated which
and representation sufficient and
not organized is organized and but
presenting data.
and not not used.
presented well.

Well assembled
Just assembled Well assembled and
Quality of with proper
Incomplete and some code functioning parts.
Prototype/Model functioning parts..
5 Programming is not But no creativity in
Creativity in
code functioning design and use of
design and use of
well. graphics function
graphics function

Nearly
Very short, Detailed, correct and
sufficient and
Details about clear description of Very detailed,
correct details
methods, and methods and correct, clear
about methods,
6 Report Preparation conclusions description of
and conclusion. Conclusions.
omitted, some methods, and
but clarity is not Sufficient Graphic
details are conclusions.
there in Description.
wrong
presentation.
 Major Includes major
information is information but Includes major Well organized,
Presentation of the not included, not well information and well includes major
7
micro project information is organized and organized but not information ,well
not well not presented presented well presented
organized. well

Replied to
Could not
considerable
reply to Replied properly to Replied most of
number of
8 Defense considerable considerable number the questions
questions but
number of of question. properly
not very
question.
properly
 Annexure – IV

Micro Project Evaluation Sheet

Name of Student: DIMPLE RATHORE, SAGAR SURESH, OMKAR SHINDE, SAIF SYED
Enrollment No: 1800040289, 1800040290, 1800040292, 1800040293
Name of Program: COMPUTER ENGINEERING Semester: Fifth
Course Title: SOFTWARE TESTING Course Code: 22518

Title of the Micro-Project: Prepare Test Plan and Design Test Cases to perform Black Box Testing
of TataCLIQ

Cos addressed by Micro Project: (Tick appropriate COs)

A: Apply various software testing methods. [ ✔ ]
B: Prepare test cases for different types and levels of testing. [ ]
C: Prepare test plan for an application [ ✔ ]
D: Identify bugs to create defect reports for given application. [ ]
E: Test software for performance measures using automated testing tools. [ ]

Poor Average Good Excellent

Sr. Characteristic to be
Sub Total
No. assessed (Marks1-3 ) (Marks 4-5 ) (Marks 6-8) (Marks9-10)

(A) Process and Product Assessment (Convert Above Total marks out of 6 Marks)

1 Relevance to the course

Literature Review /
2
information collection

Completion of the Target

3
as per project proposal

Analysis of Data and

4
representation

Quality of
5
Prototype/Model

6 Report Preparation

(B) Individual Presentation / Viva (Convert above total marks out of 4 marks)

7 Presentation
 8 Viva

MICRO PROJECT EVALUATION SHEET

Process and Product

Roll Total Marks
Assessment Individual Presentation / Viva (4 Marks)
No. 10
(6 Marks)
49

50

51

52

Comments/Suggestions about team work/leadership/inter-personal communication (if any)  

…………………………………………………………………………………………………….
  …………………………………………………………………………………………………….
…………………………………………………………………………………………………….
…………………………………………………………………………………………………….

Name and designation of the Teacher: Mrs. Shubhangi Chintawar (Lecturer)

Dated Signature: