QA case study

Case study in progress

Practice Software Testing — Manual Testing Case Study

API testing in progress

An independent QA portfolio project using the intentionally defective Practice Software Testing training application. Application exploration is complete, the test plan is complete and baselined, and manual test scenarios are prepared. Detailed manual test-case design, API test design, and Postman practice are in progress. Manual execution, defect reporting, execution evidence, metrics, and the final summary have not started.

Evidence and artifacts

Completed planning artifacts are available below. Evidence for detailed test cases, API testing, defect reports, execution results, and the final summary will be added as those phases are completed.

Download exploration notesDownload test planDownload test scenarios

Case study progress

The overall case study is not complete. Completed deliverables and remaining work are listed below.

Completed

  • Application exploration notes
  • Test plan
  • Manual test scenarios

In progress

  • Detailed manual test cases — 5 of 15 planned cases prepared
  • API test design and Postman practice

Not started

  • Manual test execution
  • Actual results and execution statuses
  • Defect reports
  • Screenshots and execution evidence
  • API request and response evidence
  • Test metrics
  • Final test summary
  • Recommendations
  • Lessons learned

01

Project overview

The normal reference application was explored to understand intended customer workflows and visible behaviour. Formal testing targets the intentionally defective with-bugs version and selected customer-facing functions. This independent QA portfolio project aims to produce traceable manual and API-testing evidence as test design, execution, and reporting are completed.

Tester
Yasmina Omar Barakat
Project type
Independent QA portfolio project

02

Application under test

Application type
E-commerce training application
Testing purpose
Structured QA practice using an intentionally defective version

03

Testing objectives

The test plan defines the following objectives for the planned testing cycle.

  • Verify selected customer-facing functions.
  • Validate positive and negative workflows.
  • Evaluate field validation and error handling.
  • Verify product search, filtering, and sorting.
  • Verify product details, comparison, favorites, and cart behaviour.
  • Evaluate registration, authentication, and checkout.
  • Test selected REST API endpoints using Postman.
  • Identify and document personally observed reproducible defects.
  • Produce traceable test cases, execution results, and supporting evidence.

04

Test environment

Operating system
Windows 10
Browser
Google Chrome 152.0.7977.65
Desktop resolution
2560 × 1440
Mobile environment
Chrome DevTools device emulation
Mobile viewport
iPhone 12 Pro — 390 × 844
API client
Postman
Test-case management
Microsoft Excel
Defect tracking
Jira

05

Scope

Selected areas in scope for the planned testing cycle:

  • Homepage, product catalogue, product-card content, and pagination.
  • Complete-name, partial-name, and no-result searches.
  • Category, brand, price-range, and combined filtering.
  • Product sorting and state persistence.
  • Product details, comparison, quantity selection, favorites, and cart.
  • Registration, field validation, login, authenticated navigation, password-recovery entry point, and sign out.
  • Cart contents, quantity updates, removal, totals, empty-cart behaviour, and refresh persistence.
  • Guest and authenticated checkout workflows.
  • Selected product and authentication API endpoints.
  • Positive, negative, validation, authorization, and nonexistent-resource API scenarios.

06

Out-of-scope items

  • Administrator functionality
  • Native mobile application testing
  • Real payment processing
  • Security and penetration testing
  • Performance and load testing
  • Database testing
  • Email-delivery verification
  • Google account authentication
  • Complete browser-compatibility testing
  • Complete coverage of every application feature and API endpoint
  • Test automation during the initial testing cycle

07

Risks and limitations

  • The shared public environment may reset or alter test data. Use unique fictional data and record execution dates and environments.
  • Limited formal requirements may make expected results uncertain. Record unclear behaviour as a requirement question rather than automatically reporting a defect.
  • The website or API may become unavailable. Suspend testing and resume when the service returns.
  • The intentionally defective environment contains expected failures. Report only personally observed and reproducible failures.
  • Device coverage is limited to selected desktop and emulated mobile viewports. Record the exact viewports and state coverage limitations in the final summary.
  • Browser coverage primarily applies to Google Chrome. State this limitation in the final summary.

08

Test approach

The following test types and techniques form the planned approach. Test execution has not started.

Planned test types

  • Functional testing
  • Negative testing
  • UI testing
  • Usability testing
  • Responsive testing
  • API testing
  • Confirmation testing
  • Regression testing

Planned test techniques

  • Equivalence Partitioning
  • Boundary Value Analysis
  • Positive and negative testing
  • Decision-table testing
  • State-transition testing
  • Error guessing
  • Exploratory testing
  • Use-case-based testing

09

Test scenarios

Manual scenarios prepared

Scenario status represents design readiness, not execution results. The workbook marks the manual, UI, functional, responsive, authentication, cart, and checkout scenarios as Ready; the API scenarios remain Draft. No scenarios have been executed in the formal testing cycle.

Total scenarios
27
Ready
23
Draft — API
4
  • Scenario ID
    TS-001
    Module
    Home Page
    Scenario title
    Verify that the home page loads successfully and displays the main navigation, product catalogue, search, filters, and sorting controls
    Test type
    Functional / UI
    Priority
    High
    Readiness status
    Ready
  • Scenario ID
    TS-003
    Module
    Search
    Scenario title
    Verify product search using complete, partial, and non-matching product names
    Test type
    Functional / Negative
    Priority
    High
    Readiness status
    Ready
  • Scenario ID
    TS-015
    Module
    Login
    Scenario title
    Verify login using valid, invalid, and missing credentials
    Test type
    Functional / Negative
    Priority
    High
    Readiness status
    Ready
  • Scenario ID
    TS-020
    Module
    Checkout
    Scenario title
    Verify the guest checkout workflow
    Test type
    Functional
    Priority
    High
    Readiness status
    Ready
  • Scenario ID
    TS-024
    Module
    Products API
    Scenario title
    Verify retrieving, searching, and filtering product data through the API
    Test type
    API / Functional
    Priority
    High
    Readiness status
    Draft

10

Detailed test cases

In progress

5 of 15 planned detailed manual test cases prepared. Final test-case evidence will be added after the planned first-cycle cases are completed and reviewed.

11

API testing

In progress

API test design and Postman practice are in progress. API request and response evidence has not started and is coming soon.

12

Defect reports

Not started

Defect reporting has not started. Reports will be added after failures have been personally observed and reproduced.

13

Screenshots and recordings

Not started

Screenshots, recordings, and supporting execution evidence have not started. Evidence is coming soon.

14

Test execution results

Not started

Manual test execution has not started. Actual results and execution statuses will be recorded during execution.

15

Test summary

Not started

Test metrics and the final test summary have not started. They will be added after execution and evidence review.

16

Recommendations

Not started

Recommendations have not started. They will be based on the completed testing work.

17

Lessons learned

Not started

Lessons learned have not started. They will be documented after the testing cycle.