Thousands of testing hours - forgot to test under jkr?

They were too busy running him as lead with Kit Fisto and Eeth Koth by his side against the Tuskens.

This is the staggering part of this whole thing, although it’s not like it’s new. I continue to be amazed at what doesn’t get caught in testing. Certain bugs are to be expected, and they absolutely won’t catch everything. Same with team comps, I get that. But shouldn’t the expectation be to get the major points right. Or catch the obvious bugs. For example, who didn’t think to test B1 with the new droid “bonuses” in TW? Isn’t that the very first character you would look at as a tester and think hey, I wonder if I can screw something up there?

"Bulldog1205;c-1841023" wrote:
This is the staggering part of this whole thing, although it’s not like it’s new. I continue to be amazed at what doesn’t get caught in testing. Certain bugs are to be expected, and they absolutely won’t catch everything. Same with team comps, I get that. But shouldn’t the expectation be to get the major points right. Or catch the obvious bugs. For example, who didn’t think to test B1 with the new droid “bonuses” in TW? Isn’t that the very first character you would look at as a tester and think hey, I wonder if I can screw something up there?

Also great example.

We may be able to put together a manual for CG on the basics of testing.
If we could have those resources actually being productive, maybe this game would quickly perform much better.

Clearly they only run computations on expected revenue gains.

"Roopehunter;d-201958" wrote:
Erik just said that theyre putting thousands of hours of testing into every new character interaction.

Yeah, I just straight up don't believe that. Thousands of hours against what? Clearly not against "the most dominant team in the game" which probably ought to be, y'know, top of the list. Likewise, previous lolcounters of this magnitude have been found almost immediately by players, i.e. Nest holding off JKR teams until they tweaked JKR's kit specifically to prevent it.

They're just saying whatever they think will generate the least backlash.

Yeah, this puzzles me as well.

There are issues with Revan/Malak that are unanticipated, like running Nightsister Zombie in the leader spot to abuse Revan's Deathmark mechanic, or the bad Malak AI that keeps stealing 1 health from B1 rather than someone with actual health to steal. I understand missing stuff like this in the development phase, as they are outlier cases.

But for the life of me I can't comprehend a play tester not immediately plugging JKA into a JKR team to see how his kit interacts, nor can I understand missing the obviousness of the Palpatine/Vader leadership as a counter. I mean, I thought of the latter when Darth Revan's kit was revealed and he wasn't even in the game yet!

I don't have a lot of sympathy, as these problems are self-inflicted. The kits have become so complicated that it's difficult to design something that slides in somewhere between OP and useless. The JKR/Jolee interaction is forever going to dominate the course of this game unless it's remedied - the obvious solution is to limit Jolee's revive mechanic a bit, but the community uproar for messing with the kit is going to be ugly.

Someone earlier in this thread commented that they should slow down character releases and test them more; I'm not sure this is possible. The release cadence is already at its slowest and CG revenue is down significantly from last year; they desperately need to release something for people to buy. There's currently nothing for mid-spenders who couldn't or didn't want Malak. If you don't care about finishing top of arena, there's currently no game content that can't be finished using easily accessible F2P characters.

"Jarvind;c-1841055" wrote:

"Roopehunter;d-201958" wrote:
Erik just said that theyre putting thousands of hours of testing into every new character interaction.

Yeah, I just straight up don't believe that. Thousands of hours against what? Clearly not against "the most dominant team in the game" which probably ought to be, y'know, top of the list. Likewise, previous lolcounters of this magnitude have been found almost immediately by players, i.e. Nest holding off JKR teams until they tweaked JKR's kit specifically to prevent it.

They're just saying whatever they think will generate the least backlash.

They probably do commit thousands of hours to testing. Not all testing is team comps or dinner but humans. The large majority of their testing is probably automated and checks for functional bugs. It probably spits out a bunch of metrics for them to review as well. It probably even ran JKR + JKA vs DR + Malak. Without a human controller on either side it probably looked normal due to AI inefficiencies. The effort to setup and execute automation is significant, and the result reviews can be as well. Many teams include this in the "hours of testing" or as CG said, "man hours of testing."

Where you can reasonably criticize them is in the manual review and play testing they should have been doing in parallel. They clearly missed something here. And that doesn't mean they're lying about the thousands of hours of testing.

Source: I test complex software and distributed systems for a living.

"Star_Lord1718;c-1841009" wrote:
They were too busy running him as lead with Kit Fisto and Eeth Koth by his side against the Tuskens.

Same as the nest nerf, everybody beated her with jkr... Their testing team couldnt...

I'm not really sure what is worse. The fact that CG's testing team maybe doesn't know how to test new characters or that CG expects each person in the community to shell out $1,000 plus. And what's maybe worse than that is the game has made millions since its release and all we get in return is a few new characters each year. For the amount of cash CG expects each person to pay a year amounts to 6 new games and a new gaming console a year.

It's just PR BS. It's obvious they don't test anything. Focus is on monetizing the game. Then coding the latest money making scheme. Testing does not bring in cash.