Hearthpwn

Testing.  How is it they always seem to do absolutely none of it!?

In how many tech companies have you ever worked? Do you know how they work and how they manage their business? Cascade flow died in the 90s buddy lol.

It's hard to believe a studio like Blizzard would not have some sort of an automatic build system and on top of it a lot of automated tests. It's not hard creating automatic game tests with predetermined decks and random cards being played.

I don't think it's so easy to automate a game like this one. Fullstack dev here with 10 years of experience. They probably have unit tests. But that thing you said it's not so easy given the complexity of the game and the endless combinations.

They probably released this as a hotfix. Since it's the same minion than in normal mode, they modified the minimum for it being able to work in Battlegrounds. I highly doubt that they'd run full integration tests for something as simple as that. As I said before, people think that QA it's very important, but in big tech companies with hundreds of devs, it's pretty normal to release code only with testing of the devs, given low scope or heavy deadlines. This is done here, in Amazon, Google, any big tech company. QA tends to lose more money than what it saves you, since it can delay releases days or weeks, and it's only important in flows where you could lose lots of money (in this case, dust, cardpacks and store)... For big companies, it's more profitable and easy to send code quickly and let the users do the testing. If you think this is wrong, you probably should read more about tech companies.

This shit happens. It'd be stupid if a bug like this and many more happened during an expansion release. But in a small update as this one, it's pretty understandable.

I think you guys should value more the work these folks do. We're in the best moment of Hearthstone. They release more fun content  than ever, they respond quickly to bugs, nerfs or buffs (something people asked for and never did before), and they listen to the community (streamers and random guys like us). Just remember how it was a few years ago, with garbage expansions and delays of MONTHS for nerfs that were OBVIOUS (I'm looking at you Quest Rogue)

if (count(micro_mummy) == 3):

    crash_game = False

deploy

You can still get the triple with Rafaam, enemy's Macaw triggers Shredder' deathrattle and you'll kill the Mummy as Rafaam 3 times in same BG and it crashes the game. Please fix this also.

Small indie company 

Quote from Lexandur >>

Imagine having a budget to test your own product KEKW

That IS how every company on the globe works though...

Thanks guys for the fast solution

I love it when people complains without any knowledge of software development. Like if 0-bug software existed lol. Bugs (stupid, small and big ones) exist in Blizzard, Amazon, Google, any bank, ANY SOFTWARE. If you think it doesn't, you're purely ignorant.

Of course but testing stage exists and if you introduce only one minion and its bugged its ridiculous.

If this error only occurs in production build as they said, it's possible that they don't find it easily, since test and local environments tend to use different builds.

And also, testing stage exists. Yeah. But in most companies, depending of deadlines or scope of what's being touched, it can be removed from the flow and relegated for devs only. Or it can be performed without doing a full iteration of all test-cases, in which case, it's possible that they forget to test one specific case. This isn't rare, it's pretty common. I mean, they probably said "it's just one minion, don't test all shit or it'll be delayed an additional week". Most of the times this is OK. Sometimes it isn't. Cost-benefit. Are you gonna delay all of your releases just for covering the random weird bug that sometimes can happen? NO. If you think they should. Guess what buddy, you don't know NOTHING about software development and tech companies lol.

And also, a QA team of 5, 10, 20, even 100 testers. Even with automated test and unit tests. Won't EVER be as effective for finding shit and random bugs than having all of your clients testing it for you lol.

As a programmer myself, yeah that's pretty goddamn accurate. Programming isn't an exact science. A code could work one day, and get messed up by another line of code down the line. How HS hasn't broken down in spaghetti code hell is beyond me.

People like to talk trash without knowing anything. Most big tech companies tend to reduce QA and replace it with automatic tests, and only do heavy QA on things that can make you lose money, since QA time tends to lose more money than what you win by finding those bugs before the release. When you have a BIG team, it's more profitable to release quickly and apply hotfixes than trying to get your software extremely "pulished" (something impossible, as I said previously).

In Hearthstone's case, they probably test A LOT things like the shop, dust and card packs, since it's what it means BIG money loss for them. A bug on certain minion won't make them lose money, unless ALL minions are broken (and for a very very very long period, something impossible) Obviously, new minions and spells are probably tested a lot during development, since they're new. After that, I highly doubt it that they do full iterations on everything on every release.

For the mummy, since it's an existing minion in Hearthstone, they probably reuse code. And they won't test it heavily unless they're 100% new minions.

Truth hurts 'ey?

Why so many downvotes? it's true xD And they are doing with horrible packs. Worse expansions that u can count on one hand's fingers the amount of legendaries u need from each one.

I bet it has something to do with the reborn effect.

Small indie company...