Plan
What gets tested, on which build, and in what order. Written down, because a case that lives only in a tester's head cannot be run by anyone else.
Pelin Dragos
Quality assurance · GRC
Gaming QA · 5+ years · Funcom and EA Games
Feature ownership, from the plan to the report.
Feature testing from planning to reporting, including inter-map travel, instance systems and end-game content. My work at Funcom combined hands-on testing, coordination of QA assignments and mentoring junior testers.
The cycle
What owning a feature means, in 3 steps
Execute
Functional and regression passes on a running build, exploratory work where the requirements are silent, plus performance and game-cheat testing.
Report
Reproducible defect reports and a clear summary of test coverage, outstanding issues and team findings.
The record
Funcom feature ownership; EA Games FIFA responsibilities are on Software Testing
Funcom
- Owned test planning, execution and reporting for complex game features, including inter-map travel, instance systems and end-game content.
- Led a testing cycle for a major Conan Exiles update in which the team identified and documented more than 300 defects.
- Performed functional, regression, exploratory, performance and game-cheat testing to assess expected behaviour and product stability.
- Designed and developed an internal QA management tool for resource allocation and time tracking, with React, TypeScript, Python and PostgreSQL.
- Coordinated QA assignments, maintained process documentation in Confluence and mentored junior testers within Agile/Scrum workflows.
The defect count is the team's result for the cycle, not a personal total.
The tool I built
Supporting QA coordination
Internal QA tool
An internal application for QA resource allocation and time tracking, built with React, TypeScript, Python and PostgreSQL.
The concept is mine; the implementation belongs to the employer, so no code and no screenshots are published here.