Can’t get dev to reproduce bugs

Bubbles_CS

Tongue in cheek title for the bug forum, but it is a serious issue that so many reported bugs can’t be fixed. I stopped reporting bugs because of this issue. I can’t guess why bugs are so infrequently reproducible by dev, but you really do have to fix this issue so that literally hundreds of other reported bugs in the game can be resolved.

Tremayne

I would hazard a guess that the main reason for this issue is that the test rig used by the devs is not comparable to the production environment (the app). 

The devs can’t test reported bugs consistently in the app so they have created a secondary environment (the test rig) which most likely has a functionality which enable the devs to quickly test specific cards during development (I have heard rumours about a PW which has three loyalty abilities which costs nothing to use and allows you to select a creature, spell or support).

Since the test rig most likely is the development environment, it contains upcoming changes, which is another reason for failing to recreate bugs.

Finally, since it takes an enormous amount of time from a bug is reported to when it is tested (I have personally seen 6 months from a bug I reported to requests for more information - fat chance that I can recall the details then), so there is a big chance that some bugs have been fixed accidentally in the meantime.

So all that is needed is more resources to upgrade QC and QA, which is most likely not coming anytime soon. 

Bubbles_CS

@Tremayne The test PW (literally named “Dev Planeswalker”) is real. I encountered it in-app and posted about it here (I was paired against it in legacy training grounds):

https://forums.d3go.com/discussion/82669/dev-planeswalker#latest

I use a variety of test environments in my work so I know that you have some for testing new code and some to mirror production for troubleshooting, but given the encounter I had with the test PW, I would have to guess that there’s no production mirror. Also, when a bug persists for many updates after a bug report can’t be reproduced, you have to assume that the issue wasn’t fixed in the active coding environment.

when a bug as reproducible as this one can’t be reproduced by dev, though, there is real, significant cause for concern:

https://forums.d3go.com/discussion/83943/free-booster-timer-issue-can-t-reproduce#latest

it doesn’t really matter what we guess about the dev setup. There’s a recurring issue and it is a blocker to troubleshooting, which is a critical component for any product.

Tremayne

@Bubbles_CS - you are right, I’m just speculating.

I was just trying to be friendly and chat a bit about your post with you, since I don’t expect you will get any kind of an answer from Oktagon.

My background as a test environment specialist has exposed me to a huge range of test environments (albeit on a mainframe centred platform).

Though testing in prod (the large “test environment” 😁) is not uncommon, it is a poor mans choice to employ this methodology over a longer period of time IMHO. So I hope you are wrong, when you claim Oktagon only has one environment, but on second thought it would explain so many issues with events and what not.

You are most probably right that persistent bugs are due to not fixing them, but it is a real possibility that the versioning control is just not stringently enough, so bugs are reintroduced again and again by different persons.

Bubbles_CS

A lack of version control would explain so much.

 Thanks for the discussion