I don't always test my code, but when I do, I do it in production!

CCP does not internally test. Or if they do, it's very minimal. Why should they? We test all of this for them.

I'm patient, I will point out bugs and try not to berate them too badly, but they need to hire double the QA staff and make these buggy patches stop.

I'd rather they hire more developers, implement unit testing, and figure out how to get a test-server going (even if it's on the PC running in an emulator).

I'd rather they hire more developers, implement unit testing, and figure out how to get a test-server going (even if it's on the PC running in an emulator).

It's actually a really good patch relative to some of the previous ones. The not having full HP thing isn't really game breaking... Some mix up with skills and whatnot is annoying but I wouldn't go as far as to say the patch is a joke. Let's think of all the good things.

Cloaks working, new suits which from my experience seem to be balanced, new weapons that aren't ridiculously OP, no game breaking bugs. Give it a few days and they'll iron out some of these little bugs.

CCP does not internally test. Or if they do, it's very minimal. Why should they? We test all of this for them.

I'm patient, I will point out bugs and try not to berate them too badly, but they need to hire double the QA staff and make these buggy patches stop.

They don't seem willing to keep footing the investment dollars to do that for a game with 5k concurrent players.

I can appreciate this. My point was that if CCP was going to spend the money to hire new people, spending it on developers would be wiser than QA.

CCP does not internally test. Or if they do, it's very minimal. Why should they? We test all of this for them.

I'm patient, I will point out bugs and try not to berate them too badly, but they need to hire double the QA staff and make these buggy patches stop.

but this patch is a joke ^^

Honestly how is it possible that even the easiest things have not been seen.
You want examples? Sure.

1.) When I spawn I have not full shield/armor in view. THAT IS SO EASY TO SEE!!
2.) The skills have still the old texts.

I am pretty sure that I will find more after some matches, but those I have found in seconds!

Maybe I want to much but .. those bugs are so obvious :(

CCP Needs to Implement a Test Server Connection Port for the PS3's...

If we Where able to connect with Singularity(CCP test Server, Where DUST started off Originally.)And test the patches this big list would of been supplied to CCP weeks ago.


It's Time to start Looking into Allowing Some Dusters(Maybe the ones with boosters active) To Gain Access to the Singularity Server to run Testing for CCP.

The Proof that the Q&A team isn't even trying is everywhere.

They don't even need a QA team. Set up a test server and give the CPMs access. They already give direct feedback, now you have guys invested in pushing the game forward testing your **** for no extra cost besides server space.

1.9 should be devoted to bug fixes. this includes ancient bugs such as getting stuck in the terrain, getting stuck on objects, and doing something about the scanned equipment from a vehicle causes massive frame rate lag. give me the option to turn scan equipment off. all the "cool stuff" in the world can't make up for bugs a new player is not going to care about how great many things have been added to dust all he sees is a laggy/buggy game for his NPE.

I can appreciate this. My point was that if CCP was going to spend the money to hire new people, spending it on developers would be wiser than QA.

As a developer I disagree that hiring more coders versus testers would help this game. Lack of useful QA is why there are 28 items on the current known issues list, many of which were identified before release by examining the SDE. You need quality developers with oversight by a QA team that knows what they are doing. The only reason most of the current issues could have made it to release is by programmers doing a half-assed job committing code that was never checked.

Bugs happen in all programs. Nasty bugs make it to production in an MMO because its hard to test some things. Most of the issues that made it to release for Uprising 1.8 and have already been identified are easy to check. Clearly, that didn't happen. QA needs to happen.

but this patch is a joke ^^

Honestly how is it possible that even the easiest things have not been seen.
You want examples? Sure.

1.) When I spawn I have not full shield/armor in view. THAT IS SO EASY TO SEE!!
2.) The skills have still the old texts.

I am pretty sure that I will find more after some matches, but those I have found in seconds!

Maybe I want to much but .. those bugs are so obvious :(

The problem is likely not the programming itself. Their internal dev server could be working perfectly without most of these bugs. They're using a tagging system where they assign properties to things in the database. What is likely happening is that without a test server, they can't test the process of deploying an update. That means they can't pick up on the fact that steps to update the database values are using the wrong values, or are missing etc, because on the dev server the changes weren't deployed. They were done by hand by a developer trying to figure out how to get something to work the way he wants. Then when deployment time comes around nobody knows that the required changes aren't included in the build. This is why sometimes dropsuits show up after a patch with old skins and other bugs that CCP can fix without requiring us to download anything. They just adjust the data on their side and the problem is fixed.

They might be able to get around this by doing deployments internally to another server first and then running through test cases, but there may also be some oddness with the PSN deployment part that they can't replicate internally.

Source: Been a professional software developer for 10 years and I've seen these kinds of things happen time and time again in project after project, until we put in a rigorous process for creating a build package that a non-developer could deploy and redeploy without bugs slipping through. Even when you do that it's very normal to have to create the build package a few times before everything that is needed is included.

What I'm saying is they *might* be able to do this internally, but we can't know that they can. PSN could be adding a whole big pile of monkeywrenches into implementing that plan. The usefulness of that staging server depends on it being identical to the production environment. If it isn't, the testing wouldn't be nearly as useful.