How paularybicka0114/portfolio works
This repository is a personal QA portfolio, not a software application: its only listed file is README.md. The reader’s path is from the portfolio overview to evidence of experience and skills, then to linked sample test plans, cases, bug reports, and reports. The README also presents courses, certificates, tools, and learning resources. There is no runtime workflow or implementation layer to map; links between portfolio sections and sample artifacts are documented in the README.
Main entry points: README.md Portfolio page
Components 13
Portfolio
- Portfolio page
README.md - Profile
README.md
Skills and experience
- QA experience
README.md - QA tools
README.md - Technical skills
README.md - Soft skills
README.md
Work and learning evidence
- Testing samples
README.md - Allegro artifacts
README.md - Generic Shop artifacts
README.md - Courses
README.md - Certificates
README.md - Books and blogs
README.md
Other components
- Portfolio reader
Connections 12
- Portfolio reader → Portfolio page: reads
README.md - Portfolio page → Profile: presents
README.md - Portfolio page → QA experience: presents
README.md - Portfolio page → QA tools: lists
README.md - Portfolio page → Technical skills: presents
README.md - Portfolio page → Soft skills: presents
README.md - Portfolio page → Testing samples: links
README.md - Testing samples → Allegro artifacts: links
README.md - Testing samples → Generic Shop artifacts: links
README.md - Portfolio page → Courses: lists
README.md - Portfolio page → Certificates: lists
README.md - Portfolio page → Books and blogs: lists
README.md