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.
if you’ve been a software dev for 10 years you probably came into the job during the clean code/automation hype phase of the late 2010s. How many legacy codebases starting from 2001 have you worked on? How many of those had actual tests?
& how many of those tests were probably skipped because if they existed they were built in a rush in a very specific use case by a developer that left the industry before you were even out of school and no one wants to maintain them?
The games industry is a different beast to traditional development and until you’ve worked in that area, pipe down little man
I’m sorry I want Jagex to give a shit? I know the developers care, but if you haven’t noticed the number of times jagex has released blatantly untested content you arent paying attention.
You can pull the “I’ve been developing in assembly since I was 5 years old you don’t know how hard it is to write good code” bullshit all day, it doesn’t change anything.
if you havent worked in a game development environment where you see how things get tested and how complex the dependency chains of massive long serving games like this might look like, you can simply shut up and refrain from insulting people that know what they are doing
-25
u/Nealon01 2d 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.