Quality Assurance Portfolio

1. Quick QA
2. Trello Pages – 2024

Quick QA

A project I started to practice testing while helping indie/solo developers with some free testing through demos they have uploaded to Steam. Contact me if you’re looking for a tester or if you have a demo on Steam that you would like to add to this project.

Trello Pages – 2024

Rulers of Verra – Worked on this project for four testing sessions (2-5 hours each).

Viking Survival – Worked on this project for seven testing sessions (2-5 hours each).

Software Testing

Daily Schedule:

1. Check play tester discord channel for bugs/suggestions reported.
2. Look if update has been put through to start installation.
3. Check to see if developer has made any notes to Complete Bug List, Bug Report Request, Questions card, and in Discord.
4. Test game
   • Retest bugs not retested
   • Test for new bugs
5. Check play tester discord channel for bugs/suggestions reported.
6. Check to see if developer has made any notes to Complete Bug List, Bug Report Request, Questions card, and in Discord.
7. Update: Trello bug list, bug reports, Trello bug report request card, Trello cards, & daily bug report

Viking Survival

First Five Days
Context: Collaborating with indie developer and starting from scratch.

Developer requested play testers to test game, but there wasn’t a dedicated QA section or analyst. Starting from scratch I decided to first look through the information he had already had and breakdown them into categories in which I would ask questions that I felt would be useful for test creation and finding bugs.

I prioritized the bugs based on what he was requesting as higher priority and sent out daily Bug Summary Reports gathering the information from his play tester discord channel along with my own findings.

Next I utilized the information I had to create a complete bug list card on Trello. Adding checklists to allow the developer an easy way to label and work through bugs as needed.

Then I went into a Bug Report Request card. I thought it would be a good idea for him to be able to request a specific bug report. Time is limited and as I had limited time, I wanted to ensure we had a way to fast track what he needed, while I was working through the list of bugs (Mostly in the order of: highest to lowest priority)

I was able to go through bugs after the latest patch and retest accordingly. I would record my screen using QuickTime and take note of the Activity Monitor.

Additionally I had a card specifically for suggestions from the play testers for the developer to access when wanted.

Conflicts & Outcomes:

1. Working remotely with a stranger from a different country can have it’s hold ups when it comes to communication, but I have tried to remain persistent yet not overwhelming and we have agreed to scheduling a weekly meeting to discuss the bugs, what is not a bug, and additional information from both of us as needed.
2. Starting from scratch allowed me to create my own process and work through the steps as I learned. Patience was given by the developer and time was all I needed to progress. I readjusted my expectations as I was not an employee, the deadline is in the next few months, and because there was nothing set up yet, I wanted to ensure a good foundation was set as I worked on testing for bugs. I have formatted my bug reports to allow for an easy transfer to test creation when time is allotted for that.
3. I am on another project creating background art for a game developer student. It is the first time I am doing this so I am also trying to learn that, create it, and collaborate with him along with doing this site. The balancing has been good thus far. I am taking breaks while my iPad charges to do additional QA work, but I have dedicated time slots for both projects to ensure I am providing both of them the same amount of dedication and progression.
4. As I am relatively new to the professional QA scene the confidence I had in reaching out to do this was low at the time, but remembering the amount I have learned through Udemy, hands on at my previous job, and the never ending problem solving brain of mine, I pushed forward and discussed my expectations for the project and what he could expect from me including the hardware that I bring to it. I stated that I would be treating this like a job and I have been doing this regularly working 5-7 hours a day.