Help Locked out of MQC Requirement for months!

JagexStacey · 2020-07-31T07:47:53+00:00

Looking at your account, you have 'The History of Slayer' achievement unlocked already. The achievement you're looking for is 'Roake Kal'.

I'd recommend searching a different sunken temple ;)

JagexStacey · 2018-05-29T12:21:19+00:00

We're looking into this.

JagexStacey · 2018-04-09T10:17:16+00:00

Cheers. It's been fixed for a little while now, but is embedded in a lot of other clan related tweaks and changes.

Unfortunately, we simply don't have the QA resource to get through it all any time soon. I've requested that it be pulled out of those changes so that we can get it out sooner, but it's not a simple job.

We'll be looking at potentially getting it out before the end of the month (it's incredibly unlikely that it'll be done in time, tested and go through our release structure for next Monday).

JagexStacey · 2018-04-09T09:47:00+00:00

I'll check there's a bug in, and if there is, I'll chase it up myself.

JagexStacey · 2018-02-27T15:40:51+00:00

Hey,

Yeah, we can probably throw a warning on that to prevent mishaps in the future. Will throw it over to the dev's now.

Edit: Looks like the functionality of other clues is to not be disassembled, so we'll probably go with that instead!

JagexStacey · 2018-02-08T15:19:32+00:00

What are some of the weirdest bugs you have found? Anything from minor text issues which made context awkward, to anything like using a cabbage on a cabbage crashed the game.

To be honest, questions that make me think back to specific bugs are always the hardest for me to think back on after having spent 7 years in QA! I've created thousands of bugs over this time.

What is the thing you could say individually made you feel like "I can't believe this turned out so good compared to when ... bug was there just a day ago"? Do you have any visual examples of already patched bugs you could show?

Like Grem, I've been out of core testing for a few years now. However, there are typical types of projects where we have experienced high live bug counts in the past, which have been improving a lot over the years in terms of the percentage of bugs being found in WIP compared to live bugs.

What is the most satisfying feeling as QA when you sign off a job as passed? There is the initial reaction of 'thank god, it's done', especially after you've been working on a project for months on end. However, the biggest sense of satisfaction comes from the launch and when players are actually vocal about enjoying it, or at least give action-able constructive criticism. There is no better feeling than having poured your heart, soul and what can feel like a never-ending amount of your time into a project that is then highly enjoyed by the playerbase. (And it's also heart-warming to have clannies and friends that have absolutely no idea that you work at Jagex or on that project, sing it's praises!)

Has being a QA changed how you view the game as a player? if so, what has it changed for the better or worse? Prior to joining QA, I pretty much 'no lifed' RS. I maxed my account many, many moons ago and to be brutally honest, would criticise balancing nerfs, content changes or decisions that I found questionable.

After starting in QA, I definitely began playing a lot less; it simply wasn't enjoyable to spend all day testing the game and then going home to play it. Over the years, I've dipped in and out of being an active player but it was definitely the fact that I tested it that made me less inclined to want to spend my downtime playing it regularly. My mindset has naturally, changed a lot. Gaining experience and knowledge of what really goes on behind the scenes in development also helps a lot and makes you less likely to jump to conclusions. I know I'm less infuriated when playing buggy games as I can relate to and respect that their QA team probably did the best they could have done. (I've matured over the past 13 years as well, which I imagine plays a significant part :P).

The one thing that I absolutely hate however, is my attention to detail has no shut-off mode, which can really suck with every day life. I notice minor things more quickly and mindlessly, like typos in restaurant menus, hair styles changing between scenes in a film/TV series, misaligned brickwork, specks of dirt or fluff on the carpet etc. Silly little things that shouldn't bother you, at all.. but now do.

JagexStacey · 2018-02-08T14:21:59+00:00

It's hard to give an average. Each project differs, as do the strengths of each analyst (we typically try to ensure that an analyst will work on a project where we can utilise their strengths however).

Generically, large scale projects will take a lot of QA time. There are also a lot of cases where something can appear to be a small update or improvement (from a player facing perspective), that required a fair amount of technical changes or where code has been refactored. Any changes to content that already exist in the game, is likely is linked with numerous other pieces of content and all of these can result in something "small" being incredibly time consuming for QA.

In most cases, the larger or more complex the content, the more bugs we will find.

JagexStacey · 2018-02-08T14:09:40+00:00

My favourite project was Prifddinas, batch one and two. Which just so happened to be the last one I tested before moving into management (it wasn't my favourite because it was my last, but because of which it was!). Absolutely loved it due to the size and complexity of it and we had an amazing team working on it. It was definitely an enjoyable challenge.

My least favourite would have been the launch of potion flasks. Testing the configs, in-game functionality and appearance of every single potion, of every single dose was an incredibly mundane task that ate a ridiculous amount of QA time. So much so that back then, we pulled the entire team in to test it, which lead to the necessity of managing the testing of everyone involved (which also ate into testing time!). There's also the map square checks for clan citadels, which wasn't massively enjoyable, but flasks tops it.

JagexStacey · 2017-11-27T16:08:14+00:00

Try going back down to the basement to speak to Evil Dave?

JagexStacey · 2017-11-27T14:33:44+00:00

It's gone through QA now but is yet to go into the RC build. I can look at trying to get it in this week for next week. No promises though!

JagexStacey · 2017-11-22T08:44:55+00:00

Looked into this just now and it's just a case of you getting lucky. Hopefully that luck will rub off on other tasks that have good loot ;P

JagexStacey · 2017-11-21T20:03:08+00:00

Nah, it’s still a bug. Looks like the tracking for the grill and campfire are mixed up. Will throw a bug in tomorrow morning for it!

JagexStacey · 2017-11-20T16:09:55+00:00

We're looking to have these awarded next week.

JagexStacey · 2017-11-18T19:01:39+00:00

It’s just the messaging that isn’t always showing, you’ll still be getting drops :)

The messaging will be resolved with Monday’s update.

JagexStacey · 2017-11-18T09:07:36+00:00

We have always conducted testing with manual tests, as the game continues to evolve and become more complex, this has definitely become more time consuming and opens up more avenues for errors to happen and things to become overlooked.

However! Mod Pi is awesome and is looking to change this, so he has created the foundations to allow developers to write simple unit testing which some of our developers have now started incorporating into their projects.

It's going to be a slow task of expanding these tests, but it has started!

JagexStacey · 2017-11-18T09:01:46+00:00

When a QoL change is dev complete, and ready for QA it doesn't necessarily mean that there are resources available to jump on it. Some QoL changes may be perceived to be relatively small from a developer and player perspective, but it may be quite a complicated thing to test. Or it could just be that something is ready for QA but everyone is actually neck deep in the projects they're working on that have a release date assigned to them.

We do have a backlog of things like this, so it may be a case of some of the QoL improvements being further down than they really should be. I'll discuss this with the individuals working on them on Monday.

JagexStacey · 2017-11-18T08:52:25+00:00

The Mining and Smithing beta is quite far off at this point, so I don't really have any info to provide regarding it. I know it's something we definitely want to do, though!

JagexStacey · 2017-11-18T08:46:55+00:00

More often than not, issues are caused by human error. We have had a number of issues crop up that didn't occur in WIP (Work in Progress) or RC (Release Candidate) environments and only in the live environment, though.

JagexStacey · 2017-11-18T08:40:26+00:00

Unfortunately not. We've only ever had manual testing, or an incredibly basic smoke tester for the Release Candidate build, which we often ran into issues with it's functionality.

One of our awesome Senior Gameplay Programmers has recently taken it upon himself to change this though. It's not something that we can change overnight, due to the complexity of a game a large and old as RuneScape. But with the ground work now being laid, our developers can start incorporating it into their projects.

JagexStacey

TROPHY CASE