DUST Search - So CCP has no way to internally test anything

Kristoff Atruin wrote:

Thumb Green wrote:

Kristoff Atruin wrote:

There is no such thing as a tool that reproduces a bug that the steps are not known for.

True, but there is a tool that allows them to watch the code while it's running and when something randomly happens that isn't supposed to they can stop the program and analyze that portion of the code to see what's up. Of course the problem might not be with that portion of the code itself but it's a starting point and if they don't find the problem there they can look into other portions of code that ties into that portion.

However it also extends beyond bugs into balance issues; take the current AV vs tank imbalance, how the fck did that slip by Q/A?

That tool is what I was talking about when I said "They help you once you've reproduced the problem and let you start to zero in on what is actually causing it". You can't step into the code where the bug is occurring if you can't make the bug happen. Without the steps to reproduce you're not going anywhere.

CCP: Is it the most asinine way possible to do this? Yes. Then that's how we're doing it.


Author	Thread Statistics \| Show CCP posts - 1 post(s)
Thumb Green Titans of Phoenix Legacy Rising 675	Posted - 2014.01.15 15:57:00 - [1] - Quote Ghost is right, a lot of bugs are seemingly random to us players; forge gun dry fire, RDV that just sits there not dropping the vehicle, RDV that yoyos the vehicle, rail turret installations that are constantly firing, dying from hitting the ground even though the inertia dampener was on, vehicles that exploding the moment they tough the ground after being dropped by the RDV, vehicles that fall through the ground after being dropped by the RDV, tanks turning the wrong way when the turret is turned too, gun that jumps while taking a short fall in ADS, splash damage not applying at all, splash damage applying to some people but not the person standing right there next too them, splash damage being the only thing applied in direct hits, tank reload bug (like the handheld weapon one we used to get), . Those are just the things I could think of off the top of my head and each one of them randomly happens and there's no way for me to figure out why because I don't have the proper tools for it. CCP says they have a Q/A team, well they better hire more people for it because we don't have the proper tools for the job and we're not beta testers anymore. CCP: Is it the most asinine way possible to do this? Yes. Then that's how we're doing it.
Thumb Green Titans of Phoenix Legacy Rising 675	Posted - 2014.01.15 16:10:00 - [2] - Quote Just remembered disconnects from internal errors and fetal errors, And on this Quote: gun that jumps while taking a short fall in ADS I meant to say "gun that jumps continuously after taking a short fall while in ADS". It's early for me, made quite a few mistakes in that post. I'll correct it, just stating that's what I meant since ghost quoted me and I can't edit his post CCP: Is it the most asinine way possible to do this? Yes. Then that's how we're doing it.
Thumb Green Titans of Phoenix Legacy Rising 675	Posted - 2014.01.15 16:32:00 - [3] - Quote Kristoff Atruin wrote: There is no such thing as a tool that reproduces a bug that the steps are not known for. True, but there is a tool that allows them to watch the code while it's running and when something randomly happens that isn't supposed to they can stop the program and analyze that portion of the code to see what's up. Of course the problem might not be with that portion of the code itself but it's a starting point and if they don't find the problem there they can look into other portions of code that ties into that portion. However it also extends beyond bugs into balance issues; take the current AV vs tank imbalance, how the fck did that slip by Q/A? CCP: Is it the most asinine way possible to do this? Yes. Then that's how we're doing it.
Thumb Green Titans of Phoenix Legacy Rising 675	Posted - 2014.01.15 16:42:00 - [4] - Quote Kristoff Atruin wrote: Thumb Green wrote: Kristoff Atruin wrote: There is no such thing as a tool that reproduces a bug that the steps are not known for. True, but there is a tool that allows them to watch the code while it's running and when something randomly happens that isn't supposed to they can stop the program and analyze that portion of the code to see what's up. Of course the problem might not be with that portion of the code itself but it's a starting point and if they don't find the problem there they can look into other portions of code that ties into that portion. However it also extends beyond bugs into balance issues; take the current AV vs tank imbalance, how the fck did that slip by Q/A? That tool is what I was talking about when I said "They help you once you've reproduced the problem and let you start to zero in on what is actually causing it". You can't step into the code where the bug is occurring if you can't make the bug happen. Without the steps to reproduce you're not going anywhere. Exactly but my point is that many of these bugs happen randomly with no way to reliably reproduce them at will. Thus the only way to find the problem is to watch the code when these bugs randomly happen. Most of them happen frequently enough if you play the game for more than an hour for Q/A to spot them but as a player I have no way of doing that. CCP: Is it the most asinine way possible to do this? Yes. Then that's how we're doing it.
Thumb Green Titans of Phoenix Legacy Rising 675	Posted - 2014.01.15 16:57:00 - [5] - Quote Kristoff Atruin wrote: The problem is you're expecting the tools to also help you get through that reproduction step. . No I'm not, because like I've said these bugs are happening randomly; there is no real reproduction step other than playing the game and waiting for these randomly occurring bugs to randomly occur. So what I expect them to play the game and when the bug randomly happens to stop the program and to look at whats happening in the code. Like I said they happen frequently enough during play that Q/A should be able to spot them. And again like I said before, it goes beyond just bugs into balance issue like the current AV vs tank imbalance. Q/A should have caught that bs way before 1.7 was deployed. CCP: Is it the most asinine way possible to do this? Yes. Then that's how we're doing it.