C.

Ramachandran
IT-B

Mobile Application Testing Domain

A) Design Test Cases & Test Scenarios for core e-commerce functionalities, e.g.,
shopping cart, payment gateway, checkout process, etc
1. Shopping Cart
Test Scenarios:
 Adding Items to Cart
 Removing Items from Cart
 Updating Item Quantity
 Cart Persistence (Session Management)
 Cart Calculation (Subtotal, Tax, Total)
 Discount Code Application
 View Cart from Different Pages
Test Cases:
1. TC-001: Add Item to Cart
o Precondition: User is logged in.
o Steps:
1. Navigate to a product page.
2. Click on "Add to Cart."
o Expected Result: Item is added to the cart, and a confirmation
message appears.
2. TC-002: Remove Item from Cart
 o Precondition: At least one item is in the cart.
o Steps:
1. Navigate to the shopping cart.
2. Click on "Remove" next to an item.
o Expected Result: The item is removed from the cart, and the cart
updates accordingly.
3. TC-003: Update Item Quantity
o Precondition: At least one item is in the cart.
o Steps:
1. Navigate to the shopping cart.
2. Change the quantity of an item.
3. Click on "Update."
o Expected Result: The cart updates with the new quantity and
recalculates totals.
4. TC-004: Apply Discount Code
o Precondition: User has a valid discount code.
o Steps:
1. Navigate to the shopping cart.
2. Enter the discount code and click "Apply."
o Expected Result: Discount is applied, and the new total reflects
the discount.
2. Payment Gateway
Test Scenarios:
 Different Payment Methods (Credit/Debit, PayPal, etc.)
 Handling Failed Transactions
 Refund Process
 Transaction Confirmation
Test Cases:
 1. TC-005: Successful Payment with Credit Card
o Precondition: Valid credit card details.
o Steps:
1. Proceed to checkout.
2. Select credit card as payment method.
3. Enter valid card details.
4. Click "Pay Now."
o Expected Result: Payment is processed successfully, and a
confirmation page is displayed.
2. TC-006: Payment Failure with Invalid Card
o Precondition: User has an invalid credit card.
o Steps:
1. Proceed to checkout.
2. Select credit card as payment method.
3. Enter invalid card details.
4. Click "Pay Now."
o Expected Result: Payment fails, and an error message is
displayed.
3. TC-007: PayPal Payment Processing
o Precondition: Valid PayPal account.
o Steps:
1. Proceed to checkout.
2. Select PayPal as payment method.
3. Log in to PayPal and approve payment.
o Expected Result: Payment is completed, and a confirmation page
is shown.
3. Checkout Process
Test Scenarios:
  Guest Checkout vs. Registered User Checkout
 Address Validation
 Order Summary Accuracy
 Mobile vs. Desktop Checkout Experience
Test Cases:
1. TC-008: Checkout as Guest
o Precondition: User has items in the cart.
o Steps:
1. Click "Checkout" as a guest.
2. Enter shipping and billing information.
3. Choose payment method and complete the purchase.
o Expected Result: Order is processed, and a confirmation email is
sent.
2. TC-009: Address Validation During Checkout
o Precondition: User is on the checkout page.
o Steps:
1. Enter an incomplete or invalid address.
2. Attempt to proceed with the order.
o Expected Result: An error message prompts the user to correct the
address.
3. TC-010: Order Summary Verification
o Precondition: User is on the checkout page.
o Steps:
1. Review the order summary before finalizing the purchase.
o Expected Result: The order summary correctly reflects items,
quantities, prices, and totals.
B) Design Test plan & Test Strategy documents for core e-commerce
functionalities, e.g., shopping cart, payment gateway, checkout process, etc
1. Introduction
 Purpose: Define the objectives and scope of testing for core e-commerce
functionalities.
 Scope: Testing of shopping cart, payment gateway, and checkout process.
 Audience: Project stakeholders, QA team, developers.
2. Objectives
 Verify that all functionalities work as intended.
 Ensure a seamless user experience.
 Validate performance and security aspects.
3. Test Scope
 In-Scope:
o Shopping cart functionalities
o Payment processing
o Checkout flow
 Out-of-Scope:
o Non-core features (e.g., user profile management, product reviews)
4. Test Approach
 Types of Testing:
o Functional Testing
o Usability Testing
o Performance Testing
o Security Testing
o Compatibility Testing
 Testing Methods:
o Manual Testing
o Automated Testing (for regression)
5. Test Environment
 Hardware: Different devices (mobile, tablet, desktop)
 Software: Supported browsers, OS versions, and mobile platforms
 Tools: Test management tools (e.g., JIRA, TestRail), automation tools
(e.g., Selenium, Appium)
6. Test Schedule
 Milestones:
o Test Planning: [Start Date] to [End Date]
o Test Design: [Start Date] to [End Date]
o Test Execution: [Start Date] to [End Date]
o Reporting: [Start Date] to [End Date]
7. Resources
 Team Members: List of QA engineers, developers, and stakeholders
 Training Needs: Identify any necessary training for team members
8. Risk Management
 Potential Risks:
o Delays in development affecting testing timelines
o Changes in requirements mid-cycle
o Device fragmentation leading to compatibility issues
 Mitigation Strategies: Regular communication, agile methodologies,
early involvement in requirement discussions.
9. Test Deliverables
 Test Plan Document
 Test Cases
 Test Execution Reports
 Defect Reports

Test Strategy Document

1. Introduction
 Purpose: Outline the overall testing strategy for e-commerce
functionalities to ensure quality and performance.
 Scope: Focus on shopping cart, payment gateway, and checkout process.
2. Test Objectives
 Ensure core functionalities meet business and technical requirements.
 Validate user experience and system performance under load.
 Identify and resolve security vulnerabilities.
3. Testing Methodology
 Agile Testing: Adopt an iterative approach with continuous feedback.
 Shift-Left Testing: Involve testing in early stages of development to
catch issues sooner.
4. Test Levels
 Unit Testing: Conducted by developers for individual components.
 Integration Testing: Ensure components work together, especially
payment gateways and back-end systems.
 System Testing: Validate end-to-end functionalities including user
interactions.
 User Acceptance Testing (UAT): Conducted by business stakeholders to
validate the system against business requirements.
5. Types of Testing
 Functional Testing: Validate all e-commerce features against
requirements.
 Performance Testing: Test system behavior under various load
conditions.
 Security Testing: Identify vulnerabilities and ensure compliance with
security standards.
 Compatibility Testing: Verify functionality across different devices,
browsers, and OS versions.
6. Automation Strategy
 Criteria for Automation: Identify high-volume, repetitive test cases for
automation (e.g., regression tests).
 Automation Tools: Specify tools like Selenium for web applications,
Appium for mobile applications.
  Test Data Management: Use consistent and varied data sets for accurate
test results.
7. Defect Management
 Defect Life Cycle: Define the process for logging, tracking, and
resolving defects.
 Prioritization: Classify defects based on severity and impact on
functionality.
8. Reporting and Metrics
 Test Metrics: Track test case execution status, defect density, and test
coverage.
 Reporting: Regular status updates to stakeholders, including test results
and defect summaries.
9. Conclusion
 Summarize the importance of a structured approach to testing e-
commerce functionalities, highlighting the goals of ensuring quality,
performance, and user satisfaction.

C) Write SQL queries to validate database data integrity during integration testing

Check for Primary Key Constraints

To ensure that all primary keys are unique and not null:
sql
Copy code
SELECT id, COUNT(*)
FROM your_table
GROUP BY id
HAVING COUNT(*) > 1;
2. Check for Foreign Key Constraints
To verify that all foreign key references exist in the parent table:
sql
Copy code
SELECT fk.id
FROM child_table AS fk
LEFT JOIN parent_table AS p ON fk.parent_id = p.id
WHERE p.id IS NULL;
 3. Check for Not Null Constraints
To ensure that required fields are not null:
sql
Copy code
SELECT *
FROM your_table
WHERE required_column IS NULL;
4. Check for Unique Constraints
To validate that unique columns do not contain duplicates:
sql
Copy code
SELECT unique_column, COUNT(*)
FROM your_table
GROUP BY unique_column
HAVING COUNT(*) > 1;

D) Utilise HTML and CSS knowledge to verify and validate web elements during
functional testing
E) HTML Verification
F) a. Element Presence
G) Ensure that all required elements are present in the DOM.
H) Example Check:
I) javascript
J) Copy code
K) // Verify that the login button exists
L) const loginButton = document.querySelector('#login-button');
M) if (!loginButton) {
N) console.error('Login button is missing.');
O) }
P) b. Element Attributes
Q) Check that elements have the correct attributes (e.g., id, class, data-* attributes).
R) Example Check:
S) javascript
T) Copy code
U) // Verify that the input field has the correct placeholder
V) const emailInput = document.querySelector('input[type="email"]');
W) if (emailInput.placeholder !== 'Enter your email') {
X) console.error('Email input placeholder is incorrect.');
Y) }
Z) c. Correct HTML Structure
AA) Validate that the structure matches the expected hierarchy.
BB) Example Check:
CC) javascript
DD) Copy code
EE) // Verify the HTML structure of a card component
FF) const card = document.querySelector('.card');
GG) if (!card || !card.querySelector('.card-title') || !
card.querySelector('.card-content')) {
HH) console.error('Card structure is incorrect.');
 II) }

E) Conduct Acceptance testing based on client/business requirements and user

stories
Understand Requirements and User Stories
 Gather Documentation: Collect all relevant requirements documents,
user stories, and acceptance criteria.
 Identify Key Stakeholders: Engage with business analysts, product
owners, and end-users to clarify requirements.
2. Define Acceptance Criteria
For each user story, ensure that acceptance criteria are clearly defined. These
criteria will serve as the basis for your testing.
Example User Story:
 As a user, I want to add items to my shopping cart so that I can purchase
them later.
Acceptance Criteria:
 The user can add items to the cart from the product page.
 The cart updates the total amount correctly when items are added.
 The user can view the cart contents from any page.
3. Create Acceptance Test Cases
Develop test cases based on the acceptance criteria. Each test case should
include:
 Test Case ID
 Test Description
 Preconditions
 Test Steps
 Expected Result
F) Perform Load/stress Testing using Java-based tools to assess system performance
under different user loads
Select a Tool
Apache JMeter
 An open-source tool designed for performance testing.
 Allows for load testing, functional testing, and stress testing.
Gatling
 A powerful load testing framework that uses Scala but integrates well
with Java.
 Focuses on high performance and is easy to use.
2. Set Up the Testing Environment
 Install JMeter:
1. Download the latest version from the Apache JMeter website.
 2. Extract the files and set up the environment.
 Install Gatling:
1. Download the latest version from the Gatling website.
2. Extract the files and set up the environment.
3. Design Test Scenarios
Identify the key scenarios you want to test, such as:
 Load Testing: Determine how the system behaves under expected user
loads (e.g., 100, 500, 1000 users).
 Stress Testing: Identify the breaking point by pushing beyond the
expected load (e.g., 2000, 3000 users).