I'm a Media Informatics student building a foundation in computer Science. What is most important to me is to learn concepts well and clean implementation. Reading the documentations first can take time but it brings clarity in the long run. Nevertheless the first implementation can be a little messy
| Domain / Area | Tools, Frameworks & Focus |
|---|---|
| β Testing & QA | JUnit 5, Jest, Playwright, Page Object Model, test pyramid, integration & E2E testing, coverage criteria (C0/C1/C2), McCabe complexity, Halstead metrics |
| π Systems & Networking | TCP/UDP sockets, HTTP fundamentals, raw-socket programming, reverse proxies, Docker networking |
| ποΈ Databases | PostgreSQL, relational data modeling, schema design |
| π Concepts | OOP, layered/MVC architecture, clean code, Linux shell scripting, processes & threads |
| π Documentation & Process | REST/HTTP, Jira (basic), structured technical writing (QM-Handbuch, Pflichtenheft) |
-
SauceDemo Test Automation Suite (Playwright/TypeScript) β End-to-end test suite using the Page Object Model, with GitHub Actions CI/CD to run tests automatically. Github-repo
-
TravelPlanner Test Suite (Java/JUnit 5) β 29-test suite for a Java desktop application, extracted into a standalone, documented repository. Github-repo
-
Quality Management Handbook β Defined and documented testable quality criteria (availability, security, usability, compatibility) for a project management platform as part of a team. Google Doc
-
Software Quality Metrics β Attractive Numbers Algorithm β Applied McCabe cyclomatic complexity and Halstead metrics; derived control-flow graphs and test cases for C0/C1/C2 coverage. Google-doc
- Arabic ye β Native Speaker
- English us β Fluent
- German π©πͺ β Advanced (B2)