top of page

Jedi: Survivor

Star Wars Jedi: Survivor is a third-person action adventure game taking place in the Star Wars universe. Players take the place of Cal Kestis, a Jedi survivor of order 66 as he explores the galaxy in search of a home, far away from the watchful eye of the empire. Players traverse metroidvania style levels with open-world elements and engage in deep soulslike combat.

My role

On Jedi: Survivor I took on the role of a Senior QA Analyst. Our team was small which meant I needed to take on a lot of responsibility. Took charge over multiple departments as an embedded analyst - combat (AI, player, encounters) and accessibility. I was also responsible for pushing for numerous changes to the testing pipeline that set us up for success both on Jedi and another project.

​

When I was brought onto the project, there wasn't much of a pipeline for testing both internally and externally. Everybody had their own way of running things and performing test requests. The first thing I did was get us all aligned on some standardized process so as a team we could move more efficiently, effectively, and be more unified as a team. I got us to begin housing suites of test cases on Testrail so we could have a repository to draw from and drastically speed up test plan creation for new features. Testrail also served as one of the key areas we drew data from for the QV team. After getting Testrail set up, I created a new process for test requests when working with our external partners, EARO. This new process allowed us extra visibility into the progress of our test requests and allowed us to find issues with the processes and features exponentially faster.

​

Since our team was small I had to oversee multiple pods as the sole embedded analyst. I was responsible for the combat and accessibility pods. As the embedded analyst I was involved in all different kinds of meetings for the pods (design, sprint planning, kickoffs) and would communicate that information back to the QA team and external partners. I also created multiple suites of test cases on Testrail. Each suite was designed in a way to be extremely modular with general test cases that could be copied over for multiple features and drastically speed up the test case creation process.  In addition to this, I created documentation for features as well as a tracker for features that testers could use to track the status of a feature.

​

I was entrusted with a lot of other tasks as well such as spearheading the release candidate process and creating the massive test plan that encompassed it. I also assisted the UI and combat teams by creating a level within the editor and using it to record all of the videos for the skill tree.

bottom of page