Test Cases on Web Application
Micro-Project Report
Test Cases on Web Application
1.0 Rationale
Test cases are designed to verify that your application is operating as expected. Test case
writers design test cases so testers can determine whether an app or software system's feature is
working correctly. Applications must be tested thoroughly to find out how the system behaves
under all possible input conditions.
Web testing, or web application testing, is a software practice that ensures quality by testing that
the functionality of a given web application is working as intended or as per the requirements. Web
application testing allows you to find bugs at any given time, prior to a release, or on a day-to-day
basis.
2.0 Aims/Benefits of the Micro-Project
1. To learn how to design test cases.
2. To learn test cases.
3. To learn various levels of testing.
3.0 Course Outcomes Achieved
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 report on given application.
e) Test software performance measures using automated testing tools.
4.0 Actual Methodology Followed
4.1 Data Collected
Software Testing is a method to assess the functionality of the software program.
The process checks whether the actual software matches the expected requirements and
ensures the software is bug-free. The purpose of software testing is to identify the errors,
Department of Computer Engineering Page 3
Test Cases on Web Application
faults, or missing requirements in contrast to actual requirements. It mainly aims at
measuring the specification, functionality, and performance of a software program or
application.
Software testing can be divided into two steps:
Verification: It refers to the set of tasks that ensure that the software correctly implements
a specific function. It means “Are we building the product right?”.
Validation: It refers to a different set of tasks that ensure that the software that has been
built is traceable to customer requirements. It means “Are we building the right product?”.
Levels of Testing
As testing any application or software, the test engineer needs to follow multiple testing
techniques. In order to detect an error, we will implement software testing; therefore, all
the errors can be removed to find a product with more excellent quality.
Department of Computer Engineering Page 4
Test Cases on Web Application
Unit Testing:
Unit testing is the first level of software testing, which is used to test if software modules
are satisfying the given requirement or not.
Integration Testing:
The second level of software testing is the integration testing. The integration testing
process comes after unit testing.
System Testing
The third level of software testing is system testing, which is used to test the software's
functional and non-functional requirements.
Acceptance Testing
The last and fourth level of software testing is acceptance testing, which is used to evaluate
whether a specification or the requirements are met as per its delivery.
Online Feedback System using Software Testing: The online feedback system is a web-
based system that provides a way for colleges to allow students to give feedback to staff
online to improve their teaching. Students are required to give feedback using one standard
feedback form. In our project, the security is also maintained by the result of feedback
Department of Computer Engineering Page 5
Test Cases on Web Application
being only visible to the authentic users. This project also includes a time portal. This
system helps teachers to improve their performance by analyzing the feedback given by
students. The above features will be tested using Software testing different techniques in
this project. This system is not time-bound due to which students will give monthly
feedback.
ER diagram for Online Feedback System:
In this project, the Online Feedback System will be tested by employing different
parameters. Firstly SRS(Software Requirement Specification) will be made i.e. it includes
all the functional and non-functional needs. It will be more effortless to use SRS to test the
application and find bugs. A Test Plan with a standard format will be created for this
application. Test Cases will be designed to test the functionality of the software.
Functionality Requirement Specification:
Student Module:
First, the student has to register. Only registered Students will login by their username and
password. In the dashboard, all the contents of the student feedback forms will be shown.
Department of Computer Engineering Page 6
Test Cases on Web Application
There would be an option for student feedback. Students can tell their liking and disfavor
of the teachers by attending to every question.
Faculty Module:
Here faculty will first login to this section. The faculty will enter their user name and
password, if the faculties do not have an account they have to sign up in order to make an
account. As the details are filled the faculty dashboard appears in which they can fill self-
appraisal and peer appraisal. The faculty should first fill the self-appraisal in which they
have to rate themselves on some criteria. The peer faculty has to click on the peer appraisal
in order to fill the form as they click on peer appraisal.
Principal/H.O.D’s Module:
HOD user cannot sign up for the feedback system since she is the only one to access the
feature the login is pre-defined in the code itself. Once the HOD logins into her portal she
can perform various tasks like Giving authority appraisals also reviewing forms no one is
duly filled by faculty after verifying that which teacher have good feedback or which have
bad.
4.2 Design / Actual Procedure Followed
Test Plan for Online Feedback System
Test Plan Identifier: TP-02
This Test Plan Author: Mr. Roy
Introduction:
- Briefly describe the online feedback system.
- Identify the purpose and scope of testing.
Test Items:
User Registration
Feedback Submission
Feedback Categories
Search and Filter
User Permissions
Response Time
Department of Computer Engineering Page 7
Test Cases on Web Application
Features to Be Tested:
User Registration and Authentication
Feedback Submission
Usability Testing
Features to Be Not Tested:
Obsolete Technologies
Approach:
In Online Feedback System Load Testing is performed.
Item pass or fail criteria:
Pass
Test Deliverable:
If all features work properly then output pass. List all documents and artefacts to be
delivered as part of the testing process (e.g., test plan, test cases, test reports).
Environmental need:
Detail the hardware, software, and network configurations for testing.
Specify any tools or testing frameworks to be used.
Responsibilities:
Defect free Software product.
In Software product to concentrate is important.
Staff and Training Needs: Yes
For Test Plan Mrs Tannu R. R. sir has Help.
Schedule:
Day: Monday
Date: 30/09/2023
Time: 03:45 PM
Risk:
Power supply
Internet
Approval:
Department of Computer Engineering Page 8
Test Cases on Web Application
4.3 Implementation/Coding
<!DOCTYPE html>
<html>
<head>
<title>Feedback System</title>
</head>
<body>
<h1>Feedback Form</h1>
<form id="feedbackForm">
<label for="name">Name:</label>
<input type="text" id="name" required><br><br>
<label for="email">Email:</label>
<input type="email" id="email" required><br><br>
<label for="message">Message:</label>
<textarea id="message" rows="4" required></textarea><br><br>
<button type="submit">Submit Feedback</button>
</form>
<div id="confirmation" style="display: none;">
<p>Thank you for your feedback!</p>
</div>
<script>
Department of Computer Engineering Page 9
Test Cases on Web Application
// Function to handle form submission
[Link]("feedbackForm").addEventListener("submit",
function(event) {
[Link](); // Prevent default form submission behavior
// Get form values
var name = [Link]("name").value;
var email = [Link]("email").value;
var message = [Link]("message").value;
// Here, you can send the feedback data to a server using AJAX or fetch
API
// For this example, we'll simply display a confirmation message
[Link]("feedbackForm").[Link] = "none";
[Link]("confirmation").[Link] = "block";
});
</script>
</body>
</html>
Department of Computer Engineering Page 10
Test Cases on Web Application
4.4 Result & Analysis
Department of Computer Engineering Page 11
Test Cases on Web Application
5.0 Actual Resources Used
Sr. Name of Resource Specifications Qty. Remarks
No. /Material
1 Computer System Processor i3,16 GB RAM 1
2 Browser Google Chrome 1
3 Text Editor Microsoft Word 1
2010, Notepad, VS
Code
4 Printer Cannon 1
6.0 Output of Micro-Projects
Test Case Precondi Steps Expected Actual Status
Test Objective tion Result Result
Case
ID
TC1 Verify user Network [Link] Email User register User register Pass
registration should be [Link] successfully successfully
ON password
[Link] on
‘Register’
Department of Computer Engineering Page 12
Test Cases on Web Application
TC2 Verify user Network [Link] Email User register User provide Fail
registration should be [Link] successfully invalid or
ON password incomplete
[Link] on information
‘Register” so, User get
fails to
register
TC3 Verify that Network [Link] Email Email is not Email is not Pass
Email is not should be duplicate duplicate
duplicate ON
TC4 Verify user User [Link] Email User User Pass
login should be [Link] successfully successfully
registered password Login Login
[Link] on
‘Login’
TC5 Verify user User [Link] Email User User entered Fail
login should be [Link] successfully invalid
registered password Login Email and
[Link] on password
‘Login’ that’s why
login gets
fail.
TC6 Verify User 1. Do User fills all User fills all Pass
Feedback should be registration necessary necessary
submission registered 2. Enter all fields of fields of
fields in feedback feedback
feedback form form form
3. Click on
submit
TC7 Verify User 1. Do User fills all User not fill Fail
Feedback should be registration necessary all fields in
submission registered 2. Enter all fields of feedback
fields in feedback form so, it
feedback form form get fails
3. Click on
submit
TC8 Verify that User 1. Do User can User can Pass
user can view should be registration view its own view its own
their own registered 2. Enter all form form
submitted fields in
form feedback form
3. Click on
submit
4. See your
form
Department of Computer Engineering Page 13
Test Cases on Web Application
TC9 Verify that User 1. Do User can all User can all Pass
user can view should be registration forms with forms with
all submitted registered 2. Enter all permission permission
form by fields in of of
administrators feedback form administrator administrator
permission 3. Click on
submit
4. See your
form by
permission
TC10 Test that User 1. Do Forms Forms Pass
feedback is should be registration displayed displayed
displayed registered 2. Enter all with correct with correct
with correct fields in date and date and
date and time feedback form time time
3. Click on
submit
7.0 Skill Developed/ Learning outcome of this Micro-Project
1. Learn to make test cases properly.
2. Learn more about test plan report.
8.0 Applications of Micro-Project
1. Education
2. Customer service
3. Government services
Mr. Badhekar P. M.
(Subject Teacher)
************************
Department of Computer Engineering Page 14