Scribd
Upload
33 views11 pages

Group2 DPDD Assignment

This document outlines test cases for an e-commerce application. It includes: 1. Functional test cases like unit testing of components like payments and user authentication. System testing to check end-to-end workflows. 2. Non-functional test cases including performance testing of APIs and page loading, resource utilization testing under varying loads, and maintainability testing of the codebase. 3. Examples of test scenarios and steps for different test cases like error handling, resource usage, and code modifications. Expected results ensure a smooth and stable application experience.

Uploaded by

Pralav Rishu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
33 views11 pages

Group2 DPDD Assignment

This document outlines test cases for an e-commerce application. It includes: 1. Functional test cases like unit testing of components like payments and user authentication. System testing to check end-to-end workflows. 2. Non-functional test cases including performance testing of APIs and page loading, resource utilization testing under varying loads, and maintainability testing of the codebase. 3. Examples of test scenarios and steps for different test cases like error handling, resource usage, and code modifications. Expected results ensure a smooth and stable application experience.

Uploaded by

Pralav Rishu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

NARSEE MONJEE INSTITUTE OF MANAGEMENT STUDIES

SVKM’S School of Business Management

Digital Product Design and Development

Assignment

FTMBA, Trimester 5, 2022-24


Date: 19th Nov 2023

Submitted To: Dr Preeti Khanna


Submitted By: Group 2

NAME ROLL NUMBER

Spandan Chatterjee C039

Sagar Srivastava C039

Ketan Das E044

Saransh Gupta E045

Arpit Jain E051


User Flow
Information Architecture

Low fidelity Prototype


Figma Design Link:

https://www.figma.com/file/hjNe0l2watYrOnUK9sQ67h/DPDD?type=design&node-i
d=206-281&mode=design

Test cases

Functional testing

→ Unit Testing - Test each component of the development code. Components comprises
of payment gateways, search bars, Cart management, Login/Sign Up, Correct
categorization of the products. Here the tester will be going through all the procedures
that a customer will be going through whether a buyer or a seller. All the components
hence should be working with respect to all the edge cases as well as the regular inputs

Here we are following Bottom up approach where priority modules will be tested first and
major design flaws can then be hence fixed. The examples of the unit test cases will be -:

Test Case 1: Cart Functionality

Scenario: As a user, when I add items to my cart, I want the cart to reflect the correct
items and quantities.

Test Case: Add Items to Cart

Steps:

● Select a product and click on "Add to Cart."


● Verify the cart icon or section.

Expected Result:

● Cart should display the added item with the correct quantity.

Test Case 2: Error Handling

Scenario: As a user, encountering errors can be frustrating, so I expect the app to handle
them gracefully.

Test Case: Error Scenarios

Steps:

● Intentionally enter invalid credentials during login.


● Try adding an out-of-stock item to the cart.
● Attempt to process payment with incorrect details.

Expected Result:

● App should display appropriate error messages and guide users on corrective
actions.
→ System Testing - This testing will be done to check the basic input and its desired
output throughout the app, here a full journey will be followed from one unit to another
and hence overall system gets tested. We can also say that in this testing different unit
tests will be carried out but not in an isolated manner but rather in a chain or sequential
order.

→ Sanity Testing - Here we will be checking the logical reasoning behind the overall
working of the app. For example we will be checking that when a seller registers then the
GST number entered should be in the required format or the mail id entered should be
authentic instead of a made up GST number or a mail id.

Test Case 1:Authentic Information

Scenario: As a user, encountering errors can be frustrating, so I expect the app to handle
them gracefully.

Test Case: Made up information

Steps:

● Intentionally enter invalid credentials during sign up.


● Try registering
● Attempt to process request multiple times by tweaking digits or letters

Expected Result:

● App should display appropriate error messages and guide users on corrective
actions.

Non Functional Testing

In these test cases we will be focusing on the overall quality of the app instead of the
working or the logical reasoning of our outputs. These test cases will focus on the loads
potential of the app, performance under optimal and dismal conditions etc.

→ Performance Testing

1. API Response Time Testing

Scenario: Evaluate the response times of APIs used within the app.
​ Test Case: API Response Time Assessment
● Steps:
● Execute API requests (product retrieval, authentication) and measure
response times.
● Test APIs under varying loads.
● Expected Result:
● APIs should provide responses within acceptable time frames, ensuring
smooth app functionality.
●

2. Resource Utilization Test

Scenario: Monitor app resource consumption under varying loads.

​ Test Case: Resource Utilization Assessment


● Steps:
● Measure CPU, memory, and network usage under normal and high
loads.
● Assess resource utilization during peak usage periods.
● Expected Result:
● The app should efficiently utilize resources without causing excessive
strain, ensuring stability under varying loads.

3. Page Load Time Testing

Scenario: Evaluate the speed at which pages load across the application.

​ Test Case: Page Load Time Assessment


● Steps:
● Measure the time taken for critical pages (product details, cart,
checkout) to load.
● Test across different devices and network speeds.
● Expected Result:
● Pages should load within a reasonable timeframe across devices and
network conditions, enhancing user experience.

→ Maintainability Testing

Test Case for Maintainability Testing:

Objective: Evaluate system maintainability by assessing code readability, ease of


modifications, and documentation quality.

Test Steps:
● Select a target module for modification.
● Review code documentation and clarity.
● Assess code readability and adherence to standards.
● Introduce a simple modification and evaluate impact.
● Check for modularity and separation of concerns.
● Utilize maintainability tools for assessment.
● Validate version control operations (rollback, revert).
● Document observations and recommendations.

Expected Results:

● Comprehensive, clear codebase documentation.


● Easy modifications with minimal system impact.
● Identification of maintainability issues by tools.
● Successful version control operations.
● Documented observations and recommendations.

You might also like