Skip to content
View pawelbrudniak's full-sized avatar
🟒
Prevent defects β†’ Deliver quality
🟒
Prevent defects β†’ Deliver quality

Block or report pawelbrudniak

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
pawelbrudniak/README.md

πŸ§ͺ PaweΕ‚ Brudniak – QA Engineer (in progress)

I focus on real-world software testing, not just theory.

Currently building:

  • end-to-end testing projects
  • real bug reports and investigations
  • production-like QA workflows

🎯 Goal: Become a QA Engineer who understands systems, not just test cases


πŸš€ Featured QA Projects

πŸ§ͺ iDURAR E2E QA Testing

πŸ‘‰ Full QA process on ERP/CRM system

  • test plan
  • test cases
  • bug reports
  • API testing (Postman)
  • data validation (DB)
  • real issues & fixes

πŸ”— https://github.com/pawelbrudniak/idurar-e2e-qa-testing


🧩 ng-diagram QA Testing

πŸ‘‰ Testing Angular library from QA perspective

  • documentation validation
  • setup & environment issues
  • integration testing
  • developer experience analysis

πŸ”— https://github.com/pawelbrudniak/ngdiagram-qa-testing


πŸ› οΈ Tools & Skills

  • API Testing β†’ Postman
  • Database β†’ PostgreSQL / MongoDB
  • Bug Tracking β†’ GitHub Issues (JIRA-like workflow)
  • Test Design β†’ Test Cases, E2E Flows
  • Environment β†’ Docker, VPS
  • Version Control β†’ Git, GitHub

🧠 Testing mindset

  • risk-based thinking
  • root cause analysis
  • real bug investigation
  • system understanding over checklist testing

πŸ” How I approach testing

I treat testing as a process, not a task:

  1. Understand the system
  2. Identify risk areas
  3. Design realistic scenarios
  4. Execute and observe behavior
  5. Report defects with context
  6. Investigate root cause

I focus on:

  • real user flows
  • system behavior
  • failure analysis

πŸ“ˆ Currently focusing on

  • ISTQB Foundation Level certification
  • building real QA portfolio projects
  • improving API & database testing
  • understanding system architecture

🧩 Lessons Learned

  • setup scripts often fail due to outdated code
  • many bugs come from missing dependencies
  • real systems are inconsistent and incomplete
  • testing requires investigation, not assumptions

πŸ“¬ Let's connect

I’m open to:

  • Junior QA roles
  • QA internships
  • real-world testing opportunities

Pinned Loading

  1. idurar-e2e-qa-testing idurar-e2e-qa-testing Public

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

  2. ngdiagram-qa-testing ngdiagram-qa-testing Public

    🧩 QA case study of ng-diagram Angular library: testing documentation, setup, integration, and developer experience.

  3. api-testing-postman-collection api-testing-postman-collection Public