S.H.

JONDHALE POLYTECHNIC
DOMBIVLI(W)
MAHARASTRA STATE BOARD OF TECHNICAL EDUCATION
(2023-2024)

MICROPROJECT REPORT ON:

TEST CASE ON FEEDBACK SYSTEM

Submitted by: 1539.Atharva lames

1538.Devansh chapre
1513.Varun bhalerao

Under The Guidance Of

P.H. BHARAMBE

In the partial fullfillment for the award of diploma in

Computer Engineeering
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION

Certificate

This is to certify that Atharva Lamse(1539), Devansh

Chapre(1538), Varun Bhalerao(1513) of Fifth Semester of
Diploma in Computer Engineering of Institute
S.H.Jondhale Polytechnic(Code: 0044) has completed the
micro project satisfactorily in subject Software
Testing(Code- 22519) for the Academic year 2023 to
2024 as prescribed in the curriculum.

SUBJECT TEACHER HEAD OF DEPARTMENT PRINCIPAL

 Acknowledgement

We express our sincere gratitude to our Head of Department and our

Microproject guide Professor Mrs. P.H. Bharambe for their valuable

advice.

We also express our gratitude and thanks to all of our teachers and other

faculty members of department computers, S.H.Jondhale Polytechnic for

their sincere cooperation in completing this microproject.

Index
SR.NO CONTENT PAGENO

1.
Introduction

2.
Test Methodology

3.
TEST CASE

4.
CONCLUSION AND REFERENCE

Introduction

SOFTWARE TESTING :
Testing is defined as execution of a work product with intent to find a defect'. The
primary role of software testing is not to demonstrate the correctness of software
product, but to expose hidden defect so that can be fixed. The purpose of software
testing is Assurance of Quality .
Software testing is a process used to evaluate a software application's functionality
and quality. It involves executing the software to identify defects, ensuring it meets
specified requirements, and confirming it operates as expected. Testing helps
uncover bugs or issues early in the development cycle, ultimately leading to a more
reliable and robust software product.

Software Development Life Cycle Model:

Objective of Software Testing:

1. Finding Error: Testing is a process of executing a program with the intent

of finding an error. successful test is one that uncovers an undiscovered error.
2. Creating Good Test Cases: A good test case is one that has a high
probability of finding undiscovered error.
3. Quality Improvement: Testing should systematically uncover different
classes of errors in a minimum amount of time and with a minimum amount of
effort.
4. Satisfying Customer Requirements: A secondary benefit of testing is that
it demonstrates that the software appears to be working as stated in the
specifications.
5. Reliability and Quality: The data collected through testing can also provide
an indication of the software's reliability and quality. But, testing cannot show the
absence of defect -- it can only show that software defects are present.

Advantages of Software Testing

• Identifying bugs and errors
• Improving quality and user satisfaction
• Enhancing security and protecting data
• Saving time and resources
• Meeting industry standards and regulations
Disadvantages of Software Testing

• Time-consuming and costly  Limited testing scenarios

• Dependency on testers’ skills
• False sense of security
• Burden on developers

Terminologies:

1.Defect:
Definition: A flaw or imperfection in the software that can cause the software to
fail or not operate as intended.
Details: A defect is an issue that occurs within the code, design, or any other aspect
of the software, deviating from the specified requirements.

2.Failure:
Definition: The inability of the software or system to perform its intended
functions according to the specified requirements or user expectations. Details:
Failure occurs when a defect manifests itself and leads to incorrect or
unexpected behavior in the software during its usage.

3.Error:
Definition: A human action or mistake in the software development process that
leads to a defect or fault in the software.
Details: Errors are introduced by human actions and can lead to defects if not
identified and corrected during the development process.

4.Bug:
Definition: A term often used interchangeably with "defect," referring to a fault in
the software that causes it to produce incorrect or unexpected results.
Details: Bug is a general term used to describe defects or faults in the software that
may lead to failures or errors in the system.

5.Fault:
Definition: A flaw or defect in the software that can cause it to fail or produce
incorrect results when executed.
Details: A fault is a deviation in the software code, design, or requirements that,
when executed, may result in a failure or undesired behavior.

Levels of Software Testing:

• Unit Testing:
Definition: The lowest level of testing, where individual components or units
(e.g., functions, procedures, methods) of the software are tested in isolation.
Objective: To verify that each unit of the software works as designed and
behaves correctly.

• Integration Testing:
Definition: Testing conducted to validate the integration and interaction
between different units, modules, or components of the software.
Objective: To ensure that integrated components function as expected and
that errors at the interface are detected.

• System Testing:
Definition: The level where the entire software application is tested as a
complete and integrated system.
Objective: To validate that the software meets specified requirements and
functions correctly in its intended environment.

• Acceptance Testing:
Definition: The final level of testing, often performed by end-users or QA
teams, to verify that the software meets business requirements and is ready
for deployment.
Objective: To determine whether the software is acceptable for delivery to
the customer or end-use.

TEST CASE
Test Case is a detailed set of conditions, steps, and input data that are designed to
systematically verify or validate a specific aspect of a software application or
system. Each test case is a unique scenario or situation that represents a particular
test objective, helping in the identification of defects and the validation of
functionality.

Test Case Template

Test Case ID Test Designed By:

Test Case Priority(Low/Medium/High) Test Designed Date:
Module Name: Test Executed By:
Test Title: Test Execution Date:
Description:
Pre-Conditions:

Steps Test Steps Test Data Expected Actual Status

result result (PASS/FAIL)

Explaination:

1.Test Case ID: Unique ID for each test case.

2. Test Priority (Low/Medium/High): This is useful while test execution. Test
priority for business rules and functional test cases can be medium or higher
whereas minor user interface cases can be low priority. Test priority should be set
by reviewer.
3.Module Name: Mention name of main module or sub module.
4. Test Designed By: Name of tester.
5. Test Designed Date: Date when wrote.
6. Test Executed By: Name of tester who executed this test. To be filled after test
execution.
7.Test Execution Date: Date when test executed.
8. Test Title/Name: Test case title. For example, verify login page with valid
username and password.
9. Test Summary/Description: Describe test objective in brief.
10. Pre-condition: Any prerequisite that must be fulfilled before execution of
this test case. List all pre-conditions in order to successfully execute this test
case.
11. Test Steps: List all test execution steps in detail. Write test steps in the order
in which these should be executed. Make sure to provide as much details as you
can. Tip - to efficiently manage test case with lesser number of fields use this
field to describe test conditions, test data and user roles for running test. ut for
this test case. You can provide different data sets with exact values to be used as
an input.
13. Expected Result: What should be the system output after test execution?
Describe the expecte result in detail including message/error that should be
displayed on screen.
14. Actual result: Actual test result should be filled after test execution.
15. Status (Pass/Fail): If actual result is not as per the expected result mark this
test as failed . Otherwise updates as passed.

Test methodology
Test Levels: In the project Online Feedback System, there're 3 types of testing that
should be conducted
 • Integration Testing: (Individual software modules are combined and tested as a
group)
• System Testing: Conducted on a complete, integrated system to evaluate the
system's compliance with its specified requirements
• API testing: Test all the APIs create for the software under tested.
Suspension Criteria and Resumption Requirements: If the team members
report that there are 40% of test cases failed, suspend testing until the development
team fixes all the failed cases. Test Completeness:

❖ Specifies the criteria that denote successful completion of a test phase

❖ The run rate is mandatory to be 100% unless a clear reason is given.

❖ The pass rate is 80%, and achieving the pass rate is mandatory Project task and
estimation and schedule:

Task Member Estimate Effort

Create the test Test designer 12man-hour

specification

Perform Test Execution Tester, Test Administrator 10man-hour

Test Report Tester 6man-hour

Total 28man-hour

Test Deliverables: Test deliverables are provided below: Before

testing phase:
α Test plans document.
α Test cases documents
 α Test Design specifications.
Test Environment: It mentions the minimum hardware requirements
that will be used to test the Application. Following software's required in
addition to client-specific software.
1. Windows 8 and above
2. Office 2013 and above
Terms/Acronyms: Make a mention of any terms or acronyms used in
the project

Terms/Acronyms: Definition
API Application program interface
AUT Application under test

Test case design: A test case is a specification of the inputs, execution

conditions, testing procedure, and expected results that define a single test to be
executed to achieve a particular software testing objective, such as to exercise a
particular program path or to verify compliance with a specific requirement. Test
cases underlie testing that is methodical rather than haphazard. A battery of test
cases can be built to produce the desired coverage of the software being tested.
Formally defined test cases allow the same tests to be run repeatedly against
successive versions of the software, allowing for effective and consistent
regression testing.
Typical Written Test Case Format: - A test case is usually a single step, or
occasionally a sequence of steps, to test the correct behaviour/functionality, and
features of an application. An expected result or expected outcome is usually
given.

Test Cases
Test Case Test Scenario Test Steps Expected Pass/
ID Outcome Fail

TC -01 Valid feedback submission Fill out form Feedback Pass

with valid data submitted
 successfully
TC -02 Missing required fields Leave required Error: "Fill in all Pass
fields empty fields"

TC -03 Invalid email address Enter an invalid Error: "Invalid Pass

email email"
TC -04 Exceeding message character Enter a long Error: "Message Pass
limit message too long"
TC -05 Attachment upload Attach a valid Feedback Pass
file submitted
successfully

Test Case Test Scenario Expected Outcome Pass/Fail

ID

TC -001 Submit valid feedback Feedback submitted Pass

TC -002 Missing required fields Error: "Required fields" Pass

TC -003 Invalid email Error: "Invalid email" Pass

TC -004 Exceed message character limit Error: "Message too long" Pass

TC -005 Attachment upload Feedback submitted Pass

Conclusion
Software testing is the procedure of estimating and verifying that a
software productor application does what it is supposed to do. The
advantages of testing include averting bugs, lowering development
costs, and improving performance.

References: -
❖ https://chat.openai.com
❖ http://geeksforgeeks.com
❖ http://studco.com