A

Micro Project Report

on

" Prepare test case for web

application”
In the fulfillment of the requirement for
Diploma in Computer Engineering

Submitted by
Mr.Swaroop Santosh Vyawahare.
(2011710033)

Guided By
Prof.Bhad S.A

DEPARTMENT OF COMPUTER ENGINEERING

M.I.T POLYTECHNIC DHANORE, YEOLA.
M.S.B.T.E MUMBAI.
2022-2023

1
 MAHARASHTRA STATE BOARD OF TECHNICAL

EDUCATION,MUMBAI.

CERTIFICATE
This is to certify that Mr.Swaroop Santosh Vyawahare satisfactorily carried out
the investigation/experimentation and micro project work entitled “Prepare test case
for web application”. This work is being submitted for the award of diploma in Computer
Engineering. It is submitted in the partial fulfillment of the prescribed Syllabus M.S.B.T.E
Mumbai. For the academic year 2022-2023.

PROF. Bhad S.A PROF.Ghorpade M.S Principal

(Guided By) (H.O.D)

2
 Evalution sheet for micro project:-
Academic year:-2022-2023 Sub / Sub Code:-STE(22518)

Course & Course code:-CO5I

Name of Guide:-Bhad S.A

Semester:- 5th

Title of project:- Prepare test case

for web application

Pos:-

1.Use relevant manegerial skill for ensuring effective and efficient mangment.

2.communication: communication effectively in oral & written form.

Cos:-

1.Use basic managment principles to execute daily activires.

2.Use principles of planning and organizing for accomplishments of

task. 3.Use principles of directing and controlling for implementing the

plans.

4.Understand various previous industrial

act. Implements:-

Roll no Name Of Student Marks Out of Marks Out of Total Marks

(5)For # out of(10)
performance in
(5)For
group activity
performance in
oral
presentation

01 Swaroop Santosh
Vyawahare

Student signature Project Guide

Signature
3
 Weekly Progress Report
Sr Week Activity Performed Date signatur
.no e

1 1st Week Topic Discussion / /2022

2 2nd Week Topic Selection / /2022

3 3rd Week Collection of Data / /2022

4 4th Week Collection of Data / /2022

5 5th Week Analysis of Collected Data / /2022

6 6th Week Design of system / /2022

7 7th Week Development of algorithm / /2022

8 8th Week Making of flowchart / /2022

9 9th Week Coding / /2022

10 10th Week Coding / /2022

11 11th Week Coding / /2022

12 12th Week Testing / /2022

13 13th Week Compilation of Report / /2022

14 14th Week Compilation of presentation / /2022

15 15th Week Presentation of seminar / /2022

16 16th Week Final Submission / /2022

5
 Group Detail
Sr Name of student Seat no Enrollment no
No

1 Swaroop Santosh Vyawahare 376773 2011710033

Guide Name :Bhad S.A

6
 Index
Sr.No Title Page No

1 Introduction 7

2 Types of Test Case 12

3 Examples of Test Case 15

4 Conclusion 18

7
What is a Test Case?
A Test Case is defined as a set of actions executed to verify a particular feature or
functionality of the software application. A test case is an indispensable component
of the Software Testing LifeCycle that helps validate the AUT (Application Under
Test).

Typical Test Case Parameters:

• Test Case ID
• Test Scenario
• Test Case Description
• Test Steps
• Prerequisite
• Test Data
• Expected Result
• Test Parameters
• Actual Result
• Environment Information
• Comments
• Objectives
• Action
• Test Browser

8
Types of test cases

There are two types of test cases as mentioned below:

1. Formal test cases: Formal test cases are those test cases which
are authored as per the test case format. It has all the information
like preconditions, input data, output data, post conditions, etc.
It has a defined set of inputs which will provide the expected
output.
2. Informal test cases: Informal test cases are authored for such
requirements where the exact input and output are not known. In
order to test them the formal test cases are not authored but the
activities done and the outcomes are reported once the tests are
run.

Advantages of writing testcase

1. Test case is a written document which can be referred anytime

by anyone in the team to understand the end to end functionality
of any feature.
2. It saves time of the team members as no one has to sit and make
another person understand about the functionality of the feature.
3. Writing test case ensures the maximum coverage of the product
or application as per the customer requirement.
4. Writing test case helps in improving the software quality

Disadvantages of writing testcase

1. If any existing feature is changed then the related testcases needs

modification which is time consuming as one has to go through
the entire list of test cases and find those test cases which
requires modification.
2. If any feature becomes obsolete then the associated test cases
should be cleaned.

9
Test Case Best Practices
When writing test cases, consider these things:

• Keep the title short.

• Include a strong description.
• Be clear and concise.
• Include the expected result.

How to write good Test Case Example.

1. Test Cases need to be simple and transparent:

Create test cases that are as simple as possible. They must be clear and
concise as the author of the test case may not execute them.

Use assertive language like go to the home page, enter data, click on this
and so on. This makes the understanding the test steps easy and tests
execution faster.

2. Create Test Case with End User in Mind

The ultimate goal of any software project is to create test cases that meet
customer requirements and is easy to use and operate. A tester must
create test cases keeping in mind the end user perspective

3. Avoid test case repetition.

Do not repeat test cases. If a test case is needed for executing some other
test case, call the test case by its test case id in the pre-condition column

4. Do not Assume

Do not assume functionality and features of your software application while

preparing test case. Stick to the Specification Documents.

5. Ensure 100% Coverage

Make sure you write test cases to check all software requirements
mentioned in the specification document. Use Traceability Matrix to ensure
no functions/conditions is left untested.

10
6. Test Cases must be identifiable.

Name the test case id such that they are identified easily while tracking
defects or identifying a software requirement at a later stage.

7. Implement Testing Techniques

It's not possible to check every possible condition in your software

application. Software Testing techniques help you select a few test cases
with the maximum possibility of finding a defect.

• Boundary Value Analysis (BVA): As the name suggests it's the

technique that defines the testing of boundaries for a specified range
of values.
• Equivalence Partition (EP): This technique partitions the range into
equal parts/groups that tend to have the same behavior.
• State Transition Technique: This method is used when software
behavior changes from one state to another following particular
action.
• Error Guessing Technique: This is guessing/anticipating the error
that may arise while doing manual testing. This is not a formal
method and takes advantages of a tester's experience with the
application

8. Self-cleaning

The test case you create must return the Test Environment to the pre-test
state and should not render the test environment unusable. This is
especially true for configuration testing.

9. Repeatable and self-standing

The test case should generate the same results every time no matter who
tests it

10. Peer Review.

After creating test cases, get them reviewed by your colleagues. Your
peers can uncover defects in your test case design, which you may easily
miss.

11
 Test Case For web-application (www.cwipedia.in)

Test Action Input Test Expected Actual Status

Cas Browser Result Result
Data
e Id

TC1 Launch https://www.cwipedia.in/ Google should Cwipedi pass

Applicati Chrome open a home
on home page
page

TC2 Click On https://www.cwipedia.in/search/label/ Google Should Downloa pass

Downloa Windows Chrome Open d Page
d Download
As
section
expected

TC3 Click On https://www.cwipedia.in/search/label/ Google Should CSE pass

CSE MSBTE Chrome Open CSE page
Page

TC4 Click on https://www.cwipedia.in/search/label/ Google Should Java pass

Program Java%20Programming Chrome Open Java Program
ming>Ja Programm ming
va ing Page
Program
page
ming

TC5 Click on https://www.cwipedia.in/search/label/ Google Python pass

Should
Program Python%20Programming Chrome Program
open
ming>Py ming
Python
thon Page
programmi
ng
page

12
TC6 Click on https://www.cwipedia.in/search/label/ Google Should VB.net pass
Program VB.net Chrome Open page
ming>V VB.net
B.Net page

TC7 Click on https://www.cwipedia.in/p/aboutus.html Google Should About pass

about us Chrome open Us Page
About Us
page

TC8 Click on https://www.cwipedia.in/p/contactus- Should Contact pass

Contact demofont-familyarial.html Google Open Us
us Chrome Contact us
page

TC9 Click on https://www.cwipedia.in/p/termsand- Google Should Terms

Terms& conditions.html Chrome open And pass
Conditio Terms Conditio
n And n page
Condition
page

Conclusion

13
Writing test cases takes a little practice and knowledge of the software
that’s being tested. Well-written test cases can make your testing
process smoother, and save you time in the long run and you can
manage and organizes your test cases in an efficient way.

14