![]() I think that was not the case last year (I remember that if I was lucky to get the wanted prize in the first few tries and I had more starts, I would hit the reset/re-shuffle button (which was below the buy starts button) and could try again. You have to keep opening presents (wasting stars) until you have opened all of them, or try to find the shuffle tile, in order to have the opportunity to reset the presents and start again. ![]() But in the event, once you open a few presents and get the prize you wanted (after hitting shuffle tile a few times or not), then if you still have more stars and want to try again to get another copy of the prize you are after, there is no way to reset the presents. Instead, the number of bugs in the app are being compounded month on month and have got worse even in the few months I have been playing.ĭon’t see that this has been mentioned before in this thread (apologies if it is and I missed it). Given that the app does need an update, bugs are a regrettable but natural chance element of that update and it should be given sensible scheduling to be tested and fixed. However, the way I would naturally approach the design might be wrong, and I have very little app programming experience. I remain a little confused as to why an update is even needed for an Event. The Event doesn’t need to be on the browser for a week later since browser updates have a much shorter time between fix and distribution. In testing terms, it makes far more sense to release the Event on the app first, to give the necessary time to fix bugs. yet I am unable to beta test the very platform which needs most time to circulate around. It is that I am here to beta test, bringing some professional experience with me and willing to apply it. It isn’t just that I am pissed off as a player on this world to not have a proper chance to play, though I am pissed off with that. If there are bugs to be found, why is it that only the bugs highlighted by the browser are considered important? Why is it that any bugs to be found on the app will likely not even have time to be fixed before the event goes live? Why is it that the way the Event is played on the browser is the only measure of how the server is performing, even though some of the accesses from the app are obviously quite different. ![]() If there are no bugs to be found, there is no need of beta testing and Inno should shut down the beta server, saving themselves time and expense, both of which could be put into better use if there were never any bugs. The remaining bugs should be those which are only evidenced by saturation testing in a simulated real environment - the beta testing stage. Slightly less obvious bugs are hopefully caught in alpha testing. Click to expand.If the bugs were obvious, they should be caught by code review.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |