- Joined
- Mar 29, 2013
- Location
- United Kingdom
What baffles me is how the software malfunctions and comes up these bugs after being certified. After 4 to 5 years??
Surely they must have mucked about with the code again?... @trancemonkey - is this common and what can be the cause...?
Nate
Its important to know how compliance testing works. To my knowledge (which I am happy for people to correct me on if I am wrong) when a game is tested, the test lab will determine what are "critical files" vs non-non-critical files. Critical files are (but not necessarily limited to), anything that could affect the payout of the game (i.e maths and most files for the server side of the game for example) Non-critical files could be anything to do with the front end (client). If non-critical files are changed, the testing is likely to be less stringent than if critical files are changed. If critical files are changed in any way, this nearly always requires a full retest of the game, which is not cheap.
Changing maths or back-end software (critical) files us therefore not done lightly.
It's most likely that the fault is in the client, and given how many different web clients there are and all other different kinds of issues that can cause clients to go wrong.
Sometimes issues can be caused by things such as a change in Google chrome which causes unexpected behaviour in a game where maybe some function is deprecated or changed by Google.
When you are also at the whim of browser companies not changing stuff, things can and do go wrong.
This is why all the important stuff is done on a server somewhere






