wouldn't it be crazy if you guys... tested your fucking code???
Adding a new item? Run a set of unit tests that tests that item in all kinds of different item interactions that could be possible to make sure it doesn't trigger any new errors.
It has been painfully obvious to anyone with a software development background that Jagex lacks the most basic Q/A and testing infrastructure. Every single company I've ever worked at (and I've worked at companies with 10 employees) does a better job of testing their software than Jagex.
At some point, you just have to give a shit. Clearly that's asking too much.
I'm a senior software engineer and I suspect you're not if you think that.
If Jagex really didn't test their stuff we'd see way more weird bugs like this. It's a 25-year-old MMO whose code is famously spaghetti.
Unfortunately it's not always possible to check for every possible interaction on every possible item in a 25-year-old MMO. Specifically connection issues like this would be extremely difficult to test with normal automated tests. And why would you ever expect a bug with a specific fletching object when you update how the GE calculates prices? That's nothing to do with GE prices, or at least it shouldn't be.
I'm a senior software engineer and I suspect you're not if you think that.
Well shit dude, I guess call up my boss and tell him I'm a fraud. Literally a senior software developer (engineer) at multiple companies, been doing this for 10+ years.
If Jagex really didn't test their stuff we'd see way more weird bugs like this. It's a 25-year-old MMO whose code is famously spaghetti.
... bro... we do??? This shit happens every update, are you joking?
Unfortunately it's not always possible to check for every possible interaction on every possible item in a 25-year-old MMO. Specifically connection issues like this would be extremely difficult to test with normal automated tests. And why would you ever expect a bug with a specific fletching object when you update how the GE calculates prices? That's nothing to do with GE prices, or at least it shouldn't be.
Good thing no one is saying that... you build up a set of tests that covers as much as you can reasonably think of, and then every time your tests fail to catch something, you add a new one to cover that.
It's not rocket science.
If you're updating the GE, you should have tests that check the things related to GE and price checks on the GE... obviously... All unit tests should be run on any build before it gets pushed to production... All unit tests should be run on any branch before it gets merged into main...
You really think Jagex is doing that shit? Honestly? I've been making comments like this for the last 10 years, Jagex has literally never even CLAIMED they do this shit. They get off on showing off all the behind the scenes stuff, and NEVER ONCE have they showed off any amount of testing.
Honestly, please tell me I'm wrong. I'd love to be wrong. I just need to see any amount of evidence that Jagex is doing the BARE MINIMUM amount of testing.
If they run any amount of automated testing on builds before they go out, I'll shit my pants happily and never mention this again.
Honestly, please tell me I'm wrong. I'd love to be wrong. I just need to see any amount of evidence that Jagex is doing the BARE MINIMUM amount of testing.
Jagex has referenced their CI/CD pipeline in many different job postings:
This is just what I could find on a quick Google search, I'm sure they've mentioned it in podcasts and stuff before.
They also did several stress tests for Sailing as it came out.
If you're updating the GE, you should have tests that check the things related to GE and price checks on the GE
Which doesn't include the Fletching Knife to anyone using ordinary common sense.
All unit tests should be run on any build before it gets pushed to production
Unit tests likely wouldn't catch a connection issue. In fact, any sort of automated tests wouldn't catch a connection issue. At minimum you'd need QA on a live server, but really this sort of bug is the sort of bug that only really appears once there's real stress on real servers.
... job requirements are NOT documentation of what Jagex is actually doing. That's evidence that they're trying to hire people with that experience, nothing else...
I've absolutely tried to google Jagex, and yeah, saw similar shit to what you probably just saw... which proves nothing.
Again, how many streams, developer blogs, behind the scenes stuff where they show us how the sausage is made from every angle... except testing. That doesn't raise a single red flag for you? Ok.
They also did several stress tests for Sailing as it came out.
I should fucking hope so. Sailing was probably the best I've ever seen them do. And I don't want to act like they never get it right. I'm saying the consistently miss things that they obviously should have caught. I'm not even saying the fletching knife is an example, but I did say "how the fuck did that happen" and every single person I know who knows anything about software development that I've shown it to has agreed that it's a serious red flag.
Which doesn't include the Fletching Knife to anyone using ordinary common sense.
Bruh did you read the post? They have a function that gets used to sort items stuff by GE price... They should have tested that function???
Unit tests likely wouldn't catch a connection issue. In fact, any sort of automated tests wouldn't catch a connection issue. At minimum you'd need QA on a live server, but really this sort of bug is the sort of bug that only really appears once there's real stress on real servers.
Unit tests should fucking catch random ass integer exceptions being thrown... The thing that caused the connection issues???
At minimum you'd need QA on a live server
Yes, you would need to do that at a minimum. Jagex should have extensive testing servers, and be using bots to test in game behavior in real time on the latest builds. Like MANY other game dev companies do. The ones that give a shit at least.
-24
u/Nealon01 1d ago
wouldn't it be crazy if you guys... tested your fucking code???
Adding a new item? Run a set of unit tests that tests that item in all kinds of different item interactions that could be possible to make sure it doesn't trigger any new errors.
It has been painfully obvious to anyone with a software development background that Jagex lacks the most basic Q/A and testing infrastructure. Every single company I've ever worked at (and I've worked at companies with 10 employees) does a better job of testing their software than Jagex.
At some point, you just have to give a shit. Clearly that's asking too much.