doom eternal.jpg
black ops 4.jpg
doom eternal.jpg

Doom Eternal


SCROLL DOWN

Doom Eternal


Doom Eternal by id Software


On DOOM Eternal, I was a QA Tester.

My daily duties included finding, reporting, and closing issues, as well as completing test plans, playthroughs, dev tasks and others alike.

In addition to this, I also took on Lead responsibilities. 

For instance, I managed the distribution of regressions across the largest QA team, reviewed and critiqued bugs written by new hires, and provided my years of Quality Assurance experience to all those who needed assistance, answers, opinions, or clarity.

All of this was done in a fast-paced, team-based environment where the shift in areas of focus, especially for our team, changed frequently. We received multiple builds daily and carried out tasks assigned to us by our leads. I wrote reports, collaborated on group assignments, and personally assisted development when necessary. 

We used Jira for our bug database, Microsoft Office for test plans and reports, and Slack for communication. We tested on PC (Win64), Xbox One, and PlayStation 4.

Overall, I contributed to and was a part of the newest entry in the legendary DOOM franchise.

black ops 4.jpg

Black Ops IIII


Black Ops IIII



On Call of Duty: Black Ops IIII, I was a QA Tester.

As a QA Tester, my job was, as you might guess, to find bugs.

When a bug was found, I replicated it multiple times, and reported it into the database with a summary of the issue, a precise description of how to reproduce the issue, how frequently it occurred, a photo and/or video that demonstrates the issue, and any other test-related details. Once development had resolved the bug, I verified to ensure that that was actually true.

All of this was done in a fast-paced, team-based environment where the shift in areas of focus changed frequently. We received multiple builds daily and carried out tasks assigned to us by our leads. I wrote reports, completed individual tasks, collaborated on group assignments, and assisted developers when necessary.

We used Jira for our bug database and Microsoft Office for communication. We tested on both the PlayStation 4 and Xbox One.

Overall, I contributed to and was a part of the newest entry in the Call of Duty franchise.

Kissy Ghost


Kissy Ghost


Kissy Ghost by Dog Dad Games


On Kissy Ghost, I was the Quality Assurance Lead.

As QA Lead, I organized and supervised testing sessions. Before each testing session, I was in touch with the development team to see what specific aspects/mechanics of Kissy Ghost they wanted tested.

During each testing session, I not only supervised, but participated in finding bugs with the rest of the QA team. Every bug we found we then worked to duplicate and only after duplicating it did we report it to our bug-tracking database, which in this case, was Hansoft. We also verified whether a bug was indeed fixed and if so, I resolved it on Hansoft. 

After each testing session, I sent a report to my superior summarizing what the QA team had accomplished. In addition, I communicated to the development team what new bugs we found, what fixed bugs have been verified as fixed, and what bugs were thought to be fixed, but actually were not.

Overall, I helped ensure qualitative results that in turn produced a quality game.