Quality Assurance Team

This article lacks references. This page has unsourced or disputed statements. Please cite relevant sources. For more information, see here.

This article or section requires a cleanup. Reason: Chronicle isn't active anymore. It does not meet the RuneScape Wiki's quality standards; you can edit this page to improve it.

The Quality Assurance Team, or "QA", is a team of Jagex employees that ensures all new content in the game and on the website is of high quality, focusing on the stability and usability of the content. RuneScape QA serves three key games: RuneScape, Old School RuneScape, and Chronicle: RuneScape Legends.

Role

QA assure that the game runs smoothly and is high quality for the players. They test new updates to make sure that there are no bugs, but are also responsible for maintaining all of the content in the live game through investigating player reports, and submitting feedback for post-release changes based on player suggestions.

Testing

“	Of the handful of bugs that do make it into the game, the QA team have already found several hundreds of them before the content is launched.	”
— Mod Stacey

The Quality Assurance team tests new content after it has been developed and tries to find errors to help make the game better and easier to use.

Playing the game is only part of what the Quality Assurance team goes through during their part of the development process. Checklists make sure that the new content works right and meshes with the content already in the game. Each of these tests has to be done many different times under a number of different conditions.

Even after all of this testing, opening the content up to millions of players brings out problems that the QA team has missed. Players also work to fix the bugs by sending in feedback and bug reports – it would almost be impossible to fix all of the bugs on release, as there are hundreds of thousands of players for every QA team member.

Bug reports

Players can submit bug reports to the QA team in-game; however, more often than not, the QA team receive bugs that do not have enough information to investigate, due to lack of detail. It is also common for the QA team to receive reports that are not actual bugs, due to it often being player confusion.

Live maintenance

Live maintenance is the Quality Assurance's job in which they track what the players are saying about new content by reading the forums and checking bugs sent in by the bug tracker. They alert the developers to the problem and the developers work to fix the bug. Good and bad feedback helps the QA team to learn what the players that play RuneScape enjoy.

The Quality Assurance team also investigate all player bug reports, and submit reports to the development team for fixing. They classify bugs as Critical, Major or Minor which the development team use as an indicator for its urgency, so they can shift workload to ensure fixes are released in good time. The QA team confirm the bug fixes in their development and release build, before confirming it can go live to RuneScape players.

Teams

Scrum team

Jagex has several Scrum teams that focus on creating individual, unique pieces of content. The QA team are embedded within the development team, meaning that they work directly next to the developers, designers and artists to deliver content as a small focused team. They are involved in the content from beginning to end, contributing toward the design and development, before focusing on the testing and maintenance of content for years to come. Some QA members are skilled enough in code to create their own content, while being supervised by senior developers.

Release team

In 2014, Jagex formed a QA team that handle all of the releases before being handed to RuneScape players. Any content that is required for a release is packaged together into a single build, so that the Release QA team are able to confirm that all of the required content has come together safely, and has not conflicted with other areas of the game. They perform both manual, and automated tests to ensure build stability, and also confirm any bug fixes for existing content that are due to go out into the live game. This team plays a vital role within the development process, and it is this team that allows Scrum teams to focus on the next big thing, without having to worry about re-testing everything in a new build.

Members

In 2013 Jagex introduced a career path for the RuneScape QA team, allowing team members to progress from QA Tester, to Senior and Lead roles. This also included the creation of the Junior role, which is used to hire people that have limited, or no QA experience and are trained on the job. It is common for Jagex to place players into Junior roles as they have no previous QA experience.

RuneScape employees

Picture	Name	Nationality	Role	Employed in
	Mod Purpur	German	Senior Localisation Specialist (German)	2014
	Mod Chaose	N/A	RuneScape Content QA Analyst; QA Lore Specialist	2013
N/A	Mod Giara	N/A	RuneScape Content QA Analyst; Mobile Team
	Mod Grem	N/A	QA Tools Developer
N/A	Mod Jam	N/A	Quality Assurance Tester
	Mod James H	N/A	Lead QA Analyst (Growth Team)	22 May 2006
N/A	Mod Kitty	N/A	QA Analyst
N/A	Mod Kristy	N/A	QA Analyst
	Mod Noldor	N/A	Tech QA Analyst
N/A	Mod Sarah	American	QA Analyst
	Mod Stacey	N/A	RuneScape QA Team Leader
	Mod Veda	N/A	Junior QA Analyst	2017
	Mod Cel	N/A	QA Analyst
	Mod Breezy	N/A	Junior QA Analyst	July 2018
N/A	Mod Shrew	N/A	Junior QA Analyst	July 2018
N/A	Mod Iago	N/A	QA Analyst
N/A	Mod Pebble	N/A	QA Analyst	December 2017
	Mod Camel	N/A	QA Analyst

OldSchool RuneScape

Picture	Name	Nationality	Role	Employed in
	Mod Curse	N/A	Senior RuneScape Content QA Analyst
	Mod Roq	N/A	QA Analyst

Other

Picture	Name	Project	Nationality	Role	Employed in
	Mod Dolan	Unannounced MMO	N/A	Quality Analyst	2014
	Mod Dorando	Chronicle: RuneScape Legends	N/A	RuneScape Content QA Analyst team leader
	Mod Pingu	N/A	British	Systems Designer	2014

Former

Former members of the QA team include:

• Mod Daze
• Mod Manti
• Mod Meadows
• Mod Ramen
• Mod Wolf

Disruptions

Quality assurance provides a unique opportunity to make the game better, but it can also slow down the development process severely. If QA sees something that they don't like they will send it back to the developers. The developers will fix it, but that isn't the end of the process. The fixed material will go back the Quality assurance team to be looked at again. Depending on how perfect the team wants the material to be, this process can go on and on.

Mobilising Armies

This process can be seen first hand in a case such as Mobilising Armies. Mobilising Armies was revealed in a Behind the Scenes (Update:Future PvP Updates) on 15 August 2008, along with other future PVP updates, including Stealing creation. In November 2008, Jagex confirmed the release date to be in December. In December, Jagex revealed that they would release the minigame in early 2009. In the Update:Behind the Scenes - February (2009), Jagex revealed once again that they were postponing the release date to later in the year. It was then revealed in the forums that it would be sent to QA again as of 5 May 2009. After all the delays, it was eventually released in July of that year.

References

Navbox JSON: {"groups":[{"title":"''RuneScape''","contents":[{"text":"Mod Breezy","link":"Mod Breezy"},{"text":"Mod Cel","link":"Mod Cel"},{"text":"Mod Chaose","link":"Mod Chaose"},{"text":"Mod Dorando","link":"Mod Dorando"},{"text":"Mod Giara","link":"Mod Giara"},{"text":"Mod Grem","link":"Mod Grem"},{"text":"Mod Iago","link":"Mod Iago"},{"text":"Mod Jam","link":"Mod Jam"},{"text":"Mod James H","link":"Mod James H"},{"text":"Mod Kitty","link":"Mod Kitty"},{"text":"Mod Kristy","link":"Mod Kristy"},{"text":"Mod Noldor","link":"Mod Noldor"},{"text":"Mod Pebble","link":"Mod Pebble"},{"text":"Mod Purpur","link":"Mod Purpur"},{"text":"Mod Sarah","link":"Mod Sarah"},{"text":"Mod Shrew","link":"Mod Shrew"},{"text":"Mod Stacey","link":"Mod Stacey"},{"text":"Mod TomH","link":"Mod TomH"},{"text":"Mod Veda","link":"Mod Veda"}]},{"title":"''Old School RuneScape''","contents":[{"text":"Mod Curse","link":"Mod Curse"},{"text":"Mod Roq","link":"Mod Roq"},{"text":"Mod Wolf","link":"Mod Wolf"}]},{"title":"Former","contents":[{"text":"Mod Cocoa","link":"Mod Cocoa"},{"text":"Mod Cuppa","link":"Mod Cuppa"},{"text":"Mod Daze","link":"Mod Daze"},{"text":"Mod Dolan","link":"Mod Dolan"},{"text":"Mod Harrison","link":"Mod Harrison"},{"text":"Mod Manti","link":"Mod Manti"},{"text":"Mod Mary Day","link":"Mod Mary Day"},{"text":"Mod Meadows","link":"Mod Meadows"},{"text":"Mod Pingu","link":"Mod Pingu"},{"text":"Mod Ramen","link":"Mod Ramen"},{"text":"Mod Shogun","link":"Mod Shogun"}]}],"name":"Quality Assurance Team","title":"[[Quality Assurance Team]]"}

Navbox JSON: {"groups":[{"contents":[{"text":"Art & Graphics","link":"Art & Graphics Team"},{"text":"Audio","link":"Audio Team"},{"text":"Community Management","link":"Community Management Team"},{"text":"Content Development","link":"Content Development Team"},{"text":"Combat Council","link":"Combat Council"},{"text":"Engine Development","link":"Engine Development Team"},{"text":"Executive","link":"Executive Team"},{"text":"Game Design","link":"Game Design Team"},{"text":"Live Events","link":"Live Events Team"},{"text":"Localisation","link":"Localisation Team"},{"text":"Marketing","link":"Marketing Team"},{"text":"Ninja","link":"Ninja Team"},{"text":"Old School","link":"Old School Team"},{"text":"Player Support","link":"Player Support Team"},{"text":"Quality Assurance","link":"Quality Assurance Team"},{"text":"Social Media","link":"Social Media Team"},{"text":"System Engineering","link":"System Engineering Team"},{"text":"Video","link":"Video Team"},{"text":"Web","link":"Web Team"}]}],"name":"Jagex Teams","title":"[[Jagex Moderator#Teams|Jagex Moderator Teams]]"}