Software Developer Engineer in Test
Key responsibilities:
Key responsibilities:
- Creating automated test harness
- Mentoring a small team of QA engineers
- Writing automated test code
- Creating a framework used to write automated tests for game UI
- Creating tools aiding QA teams
New World is a massive multiplayer online role playing game created by Amazon’s Game Studios, released in the latter half of 2021. The game is strongly focused on player-versus-player, featuring complex PvP mechanics and player-centric economy. Clans, housing, world events, gathering and crafting are all used to facilitate this. Created with Amazon’s Lumberyard proprietary engine it was first available only on Windows. The game received a healthy meta score of 70 at launch, but due to troubled post-release development its user score has later diminished.
On this title I was employed as a Software Developer Engineer in Test outsourced via Lionbridge corporation. Along with a small team of QA engineers we worked on an automated test harness used to run and visualize test results. I was also creating the automated test code and other various tools external to the game itself, but utilized by the in-house as well as outsourced QA teams.
Eventually, given my previous experience in the matter, I ended up working on a framework for conducting UI automated tests. Since the UI in Lumberyard was built in Lua the framework was also utilizing this scripting language with which I fortunately had a prior experience. The framework would hook into the game to obtain UI elements states’, positions and allow to manipulate them. I left the company due to receiving a better offer soon after successfully finishing first batch of automated tests utilizing this framework.
The project scope was enormous and although I’m grateful for being able to experience it, it wasn’t always a smooth ride. Due to the teams being split between Poland and the US we had to partake in multiple daily meetings both early in the morning and late at night, which tend to create a very disjointed daily flow. In-house engine although capable lengthen the process of obtaining required functionalities. This along with extended feedback process in my opinion noticeably hindered the efforts of the QA teams.
On this title I was employed as a Software Developer Engineer in Test outsourced via Lionbridge corporation. Along with a small team of QA engineers we worked on an automated test harness used to run and visualize test results. I was also creating the automated test code and other various tools external to the game itself, but utilized by the in-house as well as outsourced QA teams.
Eventually, given my previous experience in the matter, I ended up working on a framework for conducting UI automated tests. Since the UI in Lumberyard was built in Lua the framework was also utilizing this scripting language with which I fortunately had a prior experience. The framework would hook into the game to obtain UI elements states’, positions and allow to manipulate them. I left the company due to receiving a better offer soon after successfully finishing first batch of automated tests utilizing this framework.
The project scope was enormous and although I’m grateful for being able to experience it, it wasn’t always a smooth ride. Due to the teams being split between Poland and the US we had to partake in multiple daily meetings both early in the morning and late at night, which tend to create a very disjointed daily flow. In-house engine although capable lengthen the process of obtaining required functionalities. This along with extended feedback process in my opinion noticeably hindered the efforts of the QA teams.