Sample Functional Requirements:

1. The application should receive input of 2 digits

2. It should perform arithmetic operations like +-*/

3. It should handle edge cases like divide by 0

4. It should have clear button

5. It should display output in text box

Sample Non Functional Requirements:

1. The calculator should provide near-instantaneous responses to user input, ensuring a

smooth and responsive user experience.
2. It should be able to handle a minimum of 100 simultaneous user sessions without a
significant decrease in performance.
3. The calculator should be compatible with popular web browsers (e.g., Chrome, Firefox,
Safari) and operating systems (e.g., Windows, macOS, Linux).

critical business test scenarios for basic calculator application

1. Verify that the calculator can perform basic arithmetic operations (addition, subtraction,
multiplication, and division) accurately.
2. Test with both positive and negative numbers.
3. Ensure the calculator handles invalid inputs gracefully (e.g., alphabetic characters, special
characters).
4. Verify that attempting to divide by zero results in an appropriate error message.

Non critical business test scenarios for basic calculator application

1. Test the calculator's ability to store and display a history of calculations.

2. Test the application's readability in both light and dark modes.
3. Test for auto-correct and auto-complete functionalities in case users make common typing
errors.
 Q1. Test scenario template

1. Business-Critical Test Scenarios:

 Essential Functions: These scenarios focus on critical functionalities that are
vital for the core business processes. Failure in these areas can have a
significant impact on the overall business operation.
 High-Impact Features: Test scenarios related to features that, if not
functioning properly, could result in financial loss, legal issues, or damage to
the organization's reputation.
 Security and Compliance: Testing scenarios related to data security, privacy,
and compliance with industry regulations are crucial, especially if the
application deals with sensitive information.
2. Non-Business-Critical Test Scenarios:
 Secondary Functions: Scenarios covering features that, while still important,
may not directly impact the core business processes. Failure in these areas
might be inconvenient but not catastrophic.
 User Experience: Testing scenarios related to the user interface, usability, and
overall user experience, ensuring a pleasant interaction but not directly
affecting critical business operations.
 Performance under Load: While performance is important, scenarios related
to extreme load or stress conditions might fall into this category if the impact
on business operations is not immediate.
Q2.

Severit
y: C –
Critical
Test ,M–
Scen Test Major,
ario Scenari Testcas Test S– Test Test Expecte Actua Sta Com
ID o e ID Case Small Steps data d O/p l O/p tus ments
TS1. Validate 1)
1 Gmail Open
Login gmail.
com
2)
Valid Enter
ate userna
with me
corre and Usern
ct pwd ame:
usern 3) Arun Lands Lands
ame Click Pwd: on on
and Login **aru Inbox Inbox Pas
TC1.1 pwd C button n** page Page sed
1)
Open
gmail.
Valid com
ate 2)
with Enter
Incor userna allow
rect me to
usern and Usern Display home
ame pwd ame: error page
and 3) Aruna msg Lands after
corre Click Pwd: "Invalid on wrong
ct Login **aru userid Inbox Fail creden
TC1.2 pwd C button n** or pwd" Page ed tials
TC1.3 Valid C 1) Usern Display
ate Open ame: error
with gmail. Arun msg
corre com Pwd: "Invalid
ct 2) **aru userid
usern Enter n or pwd"
ame userna
 me
and
pwd
and 3)
Incor Click
rect Login
pwd button
1)
Open
gmail.
Valid com
ate 2)
with Enter
Incor userna
rect me
usern and Usern Display
ame pwd ame: error
and 3) Aruna msg
Incor Click Pwd: "Invalid
rect Login **aru userid
TC1.4 pwd C button n or pwd"

Test case optimization technique.

1. Equivalence Partitioning:
 Identify input ranges that are expected to behave the same way.
 Create test cases that cover each partition, reducing redundancy and
increasing coverage.
2. Boundary Value Analysis:
 Focus on testing values at the edges of input domains.
 Test cases for minimum, maximum, and values just beyond the boundaries
can help uncover boundary-related defects.
3. Pairwise Testing:
 Instead of testing all possible combinations of input parameters, focus on
testing all possible pairs.
 Reduces the number of test cases significantly while maintaining a good level
of coverage.
4. Orthogonal Array Testing:
 Similar to pairwise testing, but extends to cover interactions among three or
more variables.
 Select an orthogonal array based on the number of parameters and their
possible values.
5. Risk-Based Testing:
 Prioritize test cases based on the perceived risk of failure in specific
functionalities or modules.
  Focus on critical and high-risk areas to ensure that testing efforts are
concentrated where they are most needed.
6. Code Coverage Analysis:
 Use tools to analyze code coverage during testing.
 Identify areas of the code that have not been exercised and create additional
test cases to cover those gaps.
7. Mutation Testing:
 Introduce small changes (mutations) to the code and see if the test cases can
detect these changes.
 Helps ensure that the test suite is sensitive to changes in the code.
8. Combinatorial Testing:
 Identify combinations of input parameters that are likely to cause defects.
 Use combinatorial test design tools to generate test cases covering various
combinations efficiently.
9. Use Case Prioritization:
 Prioritize test cases based on the importance of specific use cases in the
software.
 Ensure that critical functionalities are thoroughly tested before less critical
ones.
10. Regression Test Selection:
 Identify and execute only those test cases that are affected by recent code
changes.
 Minimize the time and resources required for regression testing while
ensuring that modified code is adequately tested.

Sample Requirements Traceability Matrix (RTM)

Requirement Description
Requirement (Business Requirement / User
ID Story) Design Element Test Case ID(s) Defect ID(s)
TC-001: DE-001:
Customers must be able to Successful Registration form
BR-001 register for an account. Registration form registration error
DE-002: Login form
Customers must be able to log TC-002: error (invalid
BR-002 in to their accounts. Login form Successful login credentials)
As a customer, I want to
browse products by category TC-003: Browse
so I can easily find what I'm Product category products by
US-001 looking for. navigation category N/A
As a customer, I want to view
detailed product information
including images, descriptions,
and prices before making a Product detail TC-004: View DE-003: Missing
US-002 purchase. page product details product image
US-003 As a customer, I want to add Shopping cart TC-005: Add TC-006: Remove
 items to my shopping cart so I
can purchase them later. functionality item to cart item from cart
As a customer, I want to TC-007: TC-008: Checkout
checkout and pay for my order Successful process with
using a secure payment Secure checkout checkout with different payment
US-004 gateway. process credit card methods
Inventory
The website must display management TC-009: Verify
product availability in real- system product
BR-003 time. integration availability N/A

Sample Defect Status Report for E-commerce

Website Project (Based on the RTM)
Target
Defect Date Assigned Resolution
ID Description Reported Status To Resolution Date
Registration form error
DE- (e.g., missing field 2024-03- Developer Under
001 validation) 05 Open A investigation 2024-03-10
Login form error (e.g.,
DE- invalid credentials 2024-03- In Developer Fix implemented,
002 message not clear) 07 Progress B testing in progress 2024-03-09
Image added,
DE- 2024-03- functionality
003 Missing product image 06 Fixed QA Tester verified 2024-03-07
Cannot add item to cart
DE- (e.g., functionality not To be Awaiting further
004 working) New assigned investigation 2024-03-08