CleanCity — End-to-End QA Case Study (Manual → Automation)

Role: QA Engineer (Manual Testing | Automation in Progress)
System Type: Web Application
Focus: Functional Testing • Exploratory Testing • Defect Reporting • Risk-Based Automation

---

Work In Progress

This repository represents an active QA case study based on structured, real-world testing practices.

The following artefacts are currently being finalized:

• Test execution reports
• Defect summaries with severity breakdown
• QA summary and sign-off
• Supporting evidence (screenshots and recordings)

The purpose is to demonstrate how QA work evolves from exploration → structured validation → reporting → release insight.

---

Overview

This project demonstrates how a QA Engineer approaches a system from first interaction through to structured testing and reporting.

The case study covers:

• System understanding through exploratory testing
• Feature breakdown and risk identification
• Structured test design (scenarios and test cases)
• Defect identification and documentation
• Selective introduction of automation for regression-prone areas

This is not a collection of documents.
It reflects a complete QA thinking process applied to a real system.

---

Testing Scope

In Scope

• Functional testing of core workflows
• Exploratory testing and behavior discovery
• Regression testing (manual baseline)
• Cross-browser validation (Chrome, Firefox, Edge)
• UI-level automation for stable, high-value flows

Out of Scope

• Backend/API testing
• Performance and load testing
• Security testing
• CI/CD integration
• Mobile testing

---

QA Strategy & Approach

Testing followed a risk-based approach, prioritizing:

• Core user journeys (system-critical flows)
• Data validation and persistence
• State transitions and UI feedback
• Error handling and usability risks

Execution Flow

1. Exploratory Testing

   • Understand system behavior
   • Identify inconsistencies and early risks

2. Feature Mapping

   • Break system into modules and flows

3. Risk Identification

   • Highlight high-impact failure areas

4. Test Design

   • Create structured scenarios and test cases

5. Execution

   • Validate behavior across flows and edge cases

6. Defect Reporting

   • Document issues with clear reproduction steps and impact

7. Regression Preparation

   • Identify stable flows for repeat validation

Automation is introduced only where it adds value, not by default.

---

Repository Structure

cleancity-qa-case-study/
├── app/                    # System Under Test (unmodified)
├── tests/
│   ├── manual/             # Test plan, cases, defects, exploratory notes
│   └── automation/         # Cypress and Jest suites
├── reports/                # Execution summaries and QA outputs (in progress)
└── README.md

---

Manual Testing

Manual testing focused on:

• Input validation and boundary conditions
• Data persistence and state consistency
• Filtering and conditional rendering
• Error handling and negative scenarios
• Basic accessibility and usability signals

Test cases were designed to be:

• Reproducible
• Traceable to observed behavior
• Clear and execution-focused

---

Sample Outputs (Quick View)

Key QA artefacts available in this repository:

• Exploratory Notes → tests/manual/exploratory_notes.md
• Test Plan → tests/manual/test_plan.md
• Test Cases → tests/manual/test_cases/
• Defect Report → tests/manual/defect_report.md

These demonstrate the transition from:

system exploration → structured validation → defect identification

---

Defect Reporting

Defects are documented with emphasis on:

• Clear reproduction steps
• Expected vs actual behavior
• Severity classification based on user and business impact

The goal is actionable reporting, not volume.

---

Test Automation (Selective)

Automation is applied to:

• Stable user flows
• Regression-prone functionality

Tooling

• Cypress — End-to-end UI testing
• Jest — Component and logic-level validation

Automation scope is intentionally limited to ensure:

• Stability
• Maintainability
• Real execution value

Details are documented in:
tests/automation/automation-scope.md

---

Reporting & Outcomes (In Progress)

The following outputs are being completed:

• Test execution reports
• Defect summary with severity distribution
• QA summary with risk evaluation
• Final QA sign-off

These artefacts demonstrate how testing results are translated into:

👉 clear release decisions and stakeholder communication

---

Notes

• This repository reflects QA execution only
• The system under test was not modified
• All findings are based strictly on observed behavior

---

Author

Mpumelelo Theophilas Nxazonke
QA Engineer | SDET (In Progress)
South Africa

---

License

MIT License
For educational and portfolio use only