Scribd
Upload
43 views4 pages

SE prc8

Uploaded by

21DIT087 VIDHI SHAH
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
43 views4 pages

SE prc8

Uploaded by

21DIT087 VIDHI SHAH
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/ 4

Pratical 8

Design the following for the given project (which you selected for the subject
IT363 Project –II):

1. Test Cases

Test Case 1: User Registration

 Objective: Verify that a new user can successfully register.


 Conditions: User must provide a valid email, password, and necessary details.
 Inputs:
o Email: testuser@example.com
o Password: SecurePassword123
o Name: Test User
 Steps:
1. Navigate to the registration page.
2. Enter the email address.
3. Enter the password.
4. Enter the name.
5. Click on "Register."
 Expected Results:
o User is redirected to the login page.
o A confirmation email is sent to testuser@example.com.
o Registration is confirmed in the system.

Test Case 2: Login Functionality

 Objective: Ensure that users can log in with valid credentials.


 Conditions: User must have a registered account.
 Inputs:
o Email: testuser@example.com
o Password: SecurePassword123
 Steps:
1. Navigate to the login page.
2. Enter the email address.
3. Enter the password.
4. Click on "Login."
 Expected Results:
o User is successfully logged in and redirected to the home page.
o User's profile information is displayed.
Test Case 3: Placing an Order

 Objective: Verify that users can place an order.


 Conditions: User must be logged in.
 Inputs:
o Restaurant: Italian Bistro
o Menu Item: Margherita Pizza
o Quantity: 1
 Steps:
1. Navigate to the restaurant's menu.
2. Select Margherita Pizza.
3. Choose quantity 1.
4. Add to cart.
5. Proceed to checkout.
6. Enter delivery address.
7. Confirm order.
 Expected Results:
o Order is added to the cart.
o User can proceed to checkout.
o Order confirmation screen is displayed with order details.
o A confirmation email is sent to the user.

Test Case 4: Order Tracking

 Objective: Ensure users can track their orders.


 Conditions: User must have a pending order.
 Inputs:
o Order ID: 12345
 Steps:
1. Navigate to the "Orders" section.
2. Enter the Order ID or view recent orders.
 Expected Results:
o The order status is displayed (e.g., "In Transit", "Delivered").
o Estimated delivery time is shown.

Test Case 5: Updating User Profile

 Objective: Validate that users can update their profile information.


 Conditions: User must be logged in.
 Inputs:
o New Name: Updated User
o New Address: 123 New St, New City, NC
 Steps:
1. Navigate to the profile settings page.
2. Enter new name and address.
3. Save changes.
 Expected Results:
o Profile information is updated in the system.
o Confirmation message is displayed.
2. Test Suite

User Management Suite

 Test Case 1: User Registration


 Test Case 2: Login Functionality
 Test Case 5: Updating User Profile

Ordering Suite

 Test Case 3: Placing an Order


 Test Case 4: Order Tracking

3. Testing Strategy

Scope

 Testing will cover core functionalities including user registration, login, placing and
tracking orders, and profile management.

Testing Levels

 Unit Testing: Individual components/functions (e.g., authentication, order


processing).
 Integration Testing: Interaction between modules (e.g., user login and order
placement).
 System Testing: Entire application testing (end-to-end scenarios).
 Acceptance Testing: Ensure the application meets user requirements and business
goals.

Test Environment

 Hardware: Standard desktop and mobile devices.


 Software: Latest versions of browsers (Chrome, Firefox, Safari), Android and iOS
emulators.
 Database: Mock or test database for isolated testing.

Testing Tools

 Automated Testing: Selenium, Appium.


 Manual Testing: TestRail for test case management.
 Performance Testing: JMeter.

Roles and Responsibilities

 Test Manager: Oversee the testing process and ensure test coverage.
 Test Engineers: Create and execute test cases, report defects.
 Developers: Fix defects and assist in understanding test failures.

4. Unit Testing

Unit Testing on Login Functionality

 Objective: Verify the authenticateUser function.


 Test Case 1: Valid Credentials
o Input: Email: validuser@example.com, Password: CorrectPassword
o Expected Result: Function returns a valid user object and a success status.
 Test Case 2: Invalid Credentials
o Input: Email: invaliduser@example.com, Password: WrongPassword
o Expected Result: Function returns an error status and an appropriate error
message.
 Test Case 3: Empty Credentials
o Input: Email: , Password:
o Expected Result: Function returns a validation error indicating required
fields.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy