Re: !!!HELP WITH BETA TESTING!!!

A little look into the life of a developer if an error is found:

1) The person that looks at the error will try to recreate the error by doing exactly what you told them you did when you got the error.

2) Rank the severity of the error (fix it immediately to it can wait).  Depending on the companyv (I am not entirely sure what 4Kids does), either the developer can rank it immediately, they need to send it to a supervisor for ranking, or send it to a committe that reviews it and ranks it.  They will take into consideration stuff like, "how long can the users live with this error," "if the error affects other coding or functionality," "how much time (and money) it will take to fix the error" and a whole lot of other stuff.

3) Error "ticket" gets assinged to a developer or team -- or, if it is something that was not originally thought about when creating the project, a new "requirement" has to be made to tell the developers what they want.

4) Error gets fixed.

5) Users are happy.

So depending on how big of an error it is, it could be a few days, or it could take weeks or months.  Lets hope that if anything we do find will be small ones (4Kids probably wishes that as well).

Before someone asks, no I am not a developer, but I do know a few.

LED