A
MICRO-PROJECT
OF
SOFTWARE TESTING
“CREATE A TEST CASE FOR CALCULATOR
APPLICATION”
Submitted in V - semester for partial fulfillment of requirement for
the Diploma in computer engineering of Maharashtra State Board
of Technical Education
Submitted by
Bhavik Jangade Shiban Nandi
Amarpreet Nagi Swapneel Verma
Guided by
Mrs.Shrutika Wanjari
(Assistant Professor)
DEPARTMENT OF COMPUTER ENGINEERING
G.H. RAISONI COLLEGE OF ENGINEERING & MANAGEMENT,
NAGPUR
2024-2025
PART A
Create a test case for Calculator Application
1.0 Brief Introduction
A test case is a set of conditions or variables under which a test will determine
whether a calculator application satisfies the requirements or works correctly. In
that context of calculator application, test cases are essential to ensure that the
application perform arithmetic operation accurately that consistently.
2.0 Aim of the Micro – Project
This microproject aims at:
1. Create a test case for Calculator Application
3.0 Action Plan
Planned Name of
Sr. Planned
Details of activity Finish Responsible
No. Start date
date Team Members
Bhavik Jangade
1 Project Survey 11-9-2024 17-9-2024
2 Gathering Information 18-9-2024 23-9-2024 Shiban Nandi
3 Set up and Configuration 25-9-2024 7-10-2024 Amarpreet Nagi
4 Create Report 9-10-2024 16-10-2024 Swapneel Verma
4.0 Resources Required
S.
No.
Name of Resource / Material Specification Quantity Remark
Computer(Pentium
1 Hardware: Computer System 4th gen), RAM 1 ---------
4GB,HDD 500GB
2 Operating System Windows /LINUX 1 ----------
PART B
Create a test case for Calculator Application
1.0 Brief Description
A test case for a calculator application is a detailed description of the steps to be
taken to validate the functionality of the calculator. It outlines the inputs, expected
results, and execution conditions to ensure that the calculator works as expected.
The purpose of a test case is to identify defects or bugs in the calculator
application and to ensure that it meets the required specifications and user
expectations. A well-written test case should be clear, concise, and unambiguous,
and should cover all the possible scenarios and edge cases. It encompasses a range
of scenarios including different mathematical operations like addition,
subtraction, multiplication and much more.
2.0 Aim of the Micro – Project
This microproject aims at:
1. Create a test case for Calculator Application
3.0 Actual Procedure Followed.
1. Project survey is done by Bhavik Jangade.
2. Gathering information by Shiban Nandi.
3. Set up and configuration is done by Amarpreet Nagi.
4. Creating report is done by Swapneel Verma.
4.0 Actual Resources Used
S. Name of Resource /
Specification Quantity Remark
No Material
.
Computer i3, i5
Hardware: RAM minimum 2GB
1 Computer System and onwards
1 -------
2 Operating System Windows 1 -------
/LINUX
CREATE A TEST CASE FOR CALCULATOR APPLICATION
Introduction:
A test case for a calculator application is a crucial aspect of software testing that
ensures the calculator works accurately, efficiently, and meets the user's
expectations. It is a detailed description of the steps to be taken to validate the
functionality of the calculator, covering various scenarios, edge cases, and user
interactions.
The primary goal of a test case for a calculator application is to identify defects
or bugs, and to verify that the calculator performs mathematical operations
correctly, handles different input types, and provides the expected results. A well-
designed test case helps to build confidence in the calculator's functionality,
reliability, and usability.
In the context of a calculator application, test cases can be used to validate various
aspects, such as:
• Basic arithmetic operations (addition, subtraction, multiplication, and
division)
• Advanced mathematical functions (trigonometry, logarithms,
exponentiation, etc.)
• Error handling (division by zero, invalid input, etc.)
• User interface and user experience (button clicks, display formatting, etc.)
By creating and executing test cases, developers and testers can ensure that the
calculator application meets the required specifications, is free from defects, and
provides a seamless user experience.
The purpose of a test case is to identify defects or bugs in the calculator
application and to ensure that it meets the required specifications and user
expectations. A well-written test case should be clear, concise, and unambiguous,
and should cover all the possible scenarios and edge cases.
Testing a calculator application involves verifying the accuracy and reliability of
its operations. By systematically documenting test cases, you ensure that all
functionalities are thoroughly tested and that the application meets user
expectations.
What is test Case?
A test case is a detailed set of instructions and conditions that are designed to
test a specific aspect of a software application, system, or component. The
primary purpose ofa test case is to verify that the software behaves as expected
and to ensure that it meets the specified requirements and criteria.
A test case typically includes the following components:
1.Test Case Identifier: A unique identifier or name for the test case to distinguish
it fromother test cases.
2.Test Objective: A clear and concise statement describing what the test case is
meant toachieve or verify. It should specify the expected outcome.
3.Preconditions: Conditions or requirements that must be met before the test
case can beexecuted. This may include data setup, system configurations, or
specific states of the software.
4.Test Steps: A series of step-by-step instructions to be followed during the
execution ofthe test case. These steps describe the actions to be taken by the
tester.
5.Input Data: The specific data or inputs that should be provided to the
software undertest as part of the test case.
6.Expected Results: The anticipated outcomes or responses that should be
observed after executing the test case. This should include what the system
should do, display, or return.
7.Actual Results: A space to record the actual outcomes or results observed
when thetest case is executed. Testers compare this with the expected results
to identify discrepancies.
8.Pass/Fail Criteria: The criteria used to determine whether the test case has
passed orfailed. This is typically based on a comparison between actual and
expected results.
9.Test Environment: Information about the testing environment, including the
hardware,software, and configurations used for the test.
10.Test Data: Any additional data, files, or parameters that need to be
supplied for the test.
Structure of a Test Case
A well-structured test case typically includes the following components:
1.Test Case ID: A unique identifier to reference the test case.
2.Test Case Title: A brief title that summarizes the purpose of the test.
3.Description: A detailed explanation of what the test case is designed to
verify.
4.Preconditions: Any setup or conditions that must be met before executing
the test case (e.g., user must be logged in).
5.Test Steps: A sequential list of actions that need to be taken to execute the
test (e.g., input values, click buttons).
6.Test Data: Specific data values needed for the test (e.g., usernames,
passwords).
7.Expected Result: The anticipated outcome of the test based on the input
and actions performed.
8.Actual Result: The outcome observed during the execution of the test,
which is recorded after testing.
9.Status: Indicates whether the test case passed or failed based on the
comparison of expected and actual results.
10.Comments/Notes: Any additional information, observations, or context
relevant to the test case.
Why test case is important?
Test cases play a critical role in the software development and testing lifecycle,
serving as essential tools for validating the functionality and reliability of
applications. Their importance can be understood through various aspects,
including quality assurance, cost-effectiveness, efficiency, and stakeholder
communication. Below is a detailed exploration of why test cases are vital.
1. Ensuring Software Quality
One of the primary purposes of test cases is to ensure that the software meets the
specified requirements and functions correctly. By systematically verifying each
feature through well-defined test cases, organizations can identify defects early
in the development process. This focus on quality leads to:
• Reduced Defects: Comprehensive testing helps uncover bugs and issues
before the software is released, leading to a more stable product.
• Improved User Satisfaction: High-quality software that functions as
expected enhances user experience, fostering trust and loyalty.
2. Structured Testing Process
Test cases provide a structured approach to testing. This structure ensures
consistency and thoroughness in the testing process:
• Repeatability: Test cases can be reused across different testing cycles, such
as regression testing, to ensure that existing functionalities remain
unaffected by new changes.
• Coverage: They help in identifying areas of the application that need
testing, ensuring that all functionalities are assessed.
• Systematic Approach: With clear steps, test cases guide testers through the
testing process, making it easier to follow and document findings.
3. Communication and Collaboration
Test cases serve as a common language among different stakeholders, including
developers, testers, and project managers. They facilitate:
• Clear Understanding: Well-documented test cases clarify what needs to be
tested, reducing misunderstandings among team members.
• Traceability: Test cases can be linked to specific requirements, ensuring
that all necessary functionalities are validated and allowing stakeholders to
track progress easily.
• Feedback Mechanism: They provide a basis for discussion and feedback
among team members, fostering collaboration and continuous
improvement.
4. Cost-Effectiveness
Investing time in creating and executing test cases can lead to significant cost
savings in the long run:
• Early Defect Detection: Identifying and fixing defects during the early
stages of development is generally less expensive than addressing them
after deployment. Test cases help in catching these issues sooner.
• Reduced Maintenance Costs: A well-tested application is less likely to
require extensive maintenance or updates due to bugs, which can be costly.
• Efficiency in Testing: Automated test cases can be executed repeatedly
without additional effort, optimizing resource allocation and reducing the
time spent on manual testing.
5. Risk Management
Effective use of test cases is a key strategy for managing risks associated with
software deployment:
• Identifying Critical Areas: Test cases help prioritize testing efforts based
on critical functionalities, ensuring that high-risk areas are thoroughly
validated.
• Mitigating Failure Consequences: By ensuring that potential failure points
are tested, organizations can mitigate the risks of software malfunctions in
production, which can have severe consequences.
6. Regulatory Compliance
In many industries, software applications must comply with specific regulatory
standards. Test cases are crucial for:
• Documentation: Providing evidence that the software has been thoroughly
tested and meets compliance requirements, which can be essential for
audits and regulatory reviews.
• Traceability: Linking test cases to regulatory requirements ensures that all
compliance-related functionalities are validated.
7. Continuous Improvement
Test cases contribute to a culture of continuous improvement within the
development and testing teams:
• Learning Tool: They serve as valuable references for understanding the
system's behaviour, helping testers learn from past issues and avoid
repeating mistakes.
• Process Improvement: Analysing test case execution results can provide
insights into testing processes, leading to refinements in testing
methodologies and strategies.
TEST CASE FOR CALCULATOR APPLICATION
Sr. Test Test case Steps Input Expected Status
No case Objective Data result Actual
ID
result
1 TC-1 To add two 1)Key in valid 120+100 220(Addition about 220 PASS
integer and integers from- 10 digits will be
display result 999999999999 expressed in
on calculator. to exponential form)
+99999999999
2) key in
operator+
3) Key in second
operand a valid
integer form
9999999999999
To +99999999
999
2 TC-2 To subscribe 1)Key in valid 120-100 20(Subtraction 20 PASS
to integers integers from- about 10 digits will
and display 999999999999 be expressed in
the result on to exponential form)
10-digit +99999999999
calculator
2) key in
operator-
3) Key in second
operand a valid
integer form
9999999999999
To 99999999
999
3 TC-3 To multiply 1)key in valid 100*400 40000(Multiplication 40000 PASS
two integer integers from- about 10 digits will
and display 999999999999 be expressed in
result on to exponential form)
calculator. +99999999999
2) key in
operator X
3) Key in second
operand a valid
integer form
9999999999999
To 99999999
999
4 TC-4 To divide two 1key in valid 100/25 40(division about 10 40 PASS
integer and integers from- digits will be
display result 999999999999 expressed in
on calculator. to exponential form)
+99999999999
2) key in
operator /
3) Key in second
operand a valid
integer form
9999999999999
To 99999999
999
5 TC-5 To clear the Press C Symbol 0 should be Symbol PASS
screen appear on screen 0 appear
on screen
6 TC-6 To delete Press< - One digit should be One digit PASS
digit one by (backspace) deleted from right is deleted
one hand side from
right
hand side
Conclusion
Testing a calculator application is a crucial step in ensuring its reliability and
accuracy. Through the execution of various test cases, we can validate the
calculator's functionality and identify any defects or errors. The test cases covered
arithmetic operations, trigonometric functions, and error handling, providing
comprehensive coverage of the application's features.
The test cases were designed to simulate real-world scenarios, including valid and
invalid input, to ensure the calculator's robustness. The results of the testing phase
revealed that the calculator application performed accurately and efficiently,
producing correct results for all valid inputs.
However, some errors were detected, including division by zero and invalid input
handling. These issues were addressed through debugging and code refactoring,
resulting in a more stable and reliable application.
The testing process highlighted the importance of thorough testing in ensuring
the quality of a software application. By identifying and addressing defects early
on, we can prevent errors from propagating to the end-user, thereby enhancing
the overall user experience.
In summary, the test cases for the calculator application demonstrated the
application's accuracy, efficiency, and reliability, while also revealing areas for
improvement. By incorporating these test cases into the development cycle, we
can ensure the delivery of a high-quality calculator application that meets the
user's expectations.
References
• https://artoftesting.com/hospitalmanagement
• https://www.softwaretestingo.com/hospital-management-system-
test- cases/
• https://mscw.ac.in/NAAC/Criteria1/Samples-of-
ProjectWork_Fieldwork/Computer_Science/software_Engineering/
Software%20Engineering/Hospital%20Managment%20Project
%20SE- converted.pdf
• https://sampletestcases.com/hospital-management-system-test-cases/
• https://www.exceldemy.com/test-cases-for-atm-machine-in-excel-sheet/
