Skip to content

pawelbrudniak/idurar-e2e-qa-testing

Repository files navigation

πŸ§ͺ iDURAR E2E QA Testing Project

πŸš€ Overview

This repository demonstrates a real-world, end-to-end QA process performed on the iDURAR ERP/CRM system.

The project simulates real QA responsibilities in a production-like environment:

  • test analysis & planning
  • test design & execution
  • defect reporting
  • debugging & root cause analysis
  • system-level investigation

πŸ‘‰ Focus: practical QA skills + real defects + full traceability


πŸ† Key Achievements

  • πŸ”₯ Resolved multi-layer system failures blocking application startup and login
  • πŸ” Performed end-to-end debugging across:
    • frontend (React / Vite)
    • backend (Node.js / Express)
    • database (MongoDB)
    • infrastructure (Docker / VPS)
  • 🧠 Conducted root cause analysis, not just symptom reporting
  • 🐞 Identified critical defects affecting core functionality
  • πŸ”— Established traceability (Issue ↔ Bug Report ↔ Fix)

πŸ“Έ Screenshots / Evidence Preview

❌ Before Fix – Application Crash

White Screen Error

βœ… After Fix – Successful Login

Dashboard

πŸ‘‰ Full evidence available in /assets/evidence/


🐞 Key Bugs Found

πŸ”΄ BUG-FRONTEND-ROUTES-001 – Application crash after login

Summary:
Application crashed with a white screen after login due to undefined route components.

Impact:

  • Blocked access to the system
  • Critical functionality unavailable

Root Cause:
Routes referenced missing components:

  • Quote
  • QuoteCreate
  • QuoteRead
  • QuoteUpdate
  • PaymentMode
  • Taxes

Fix:
Removed invalid routes referencing non-existent components.

Links:


πŸ”΄ BUG-SETUP-001 – Setup script failure

Summary:
Application setup failed due to invalid and outdated model references.

Impact:

  • Blocked environment setup
  • Prevented all testing activities

Root Cause:

  • Missing models (PaymentMode, Taxes)
  • Invalid seed logic for Payment

Fix:

  • Removed obsolete model references
  • Cleaned setup script logic

πŸ” Login Flow Investigation (Case Study)

πŸ‘‰ πŸ“„ Login Investigation Report


πŸ“Š QA Workflow

πŸ‘‰ QA Board


🧠 QA Approach

  • risk-based thinking
  • traceability
  • exploratory testing
  • system-level debugging

🧩 Lessons Learned

  • πŸ” Real-world bugs often appear as chains of defects, not single issues
  • 🧠 Fixing one layer (backend) can reveal issues in another (frontend)
  • πŸ” Debugging requires understanding full system flow, not just UI
  • βš™οΈ Environment issues (Docker, ports, CORS) are common real blockers
  • πŸ“Š Proper documentation increases the value of QA work significantly

πŸ’Ό CV / Interview Angle

This project demonstrates:

  • end-to-end QA ownership
  • technical debugging skills
  • real defect analysis
  • ability to communicate findings clearly

🎯 What This Shows

  • independent problem solving
  • understanding of real QA workflows
  • technical awareness beyond UI testing
  • structured thinking

πŸ“Œ Note

This is a QA-focused project.

The goal is to:

  • evaluate system quality
  • identify real defects
  • simulate professional QA work
  • document findings clearly

πŸ”— References

About

πŸ§ͺ End-to-end QA testing of the iDURAR ERP/CRM system including test planning, test design, defect reporting, and quality evaluation πŸš€

Topics

Resources

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors