Quote:
Originally Posted by Sven Niscadae
I think the other part of why Test seems whacked up is that it's not a pure certification environment. By that I mean the conditions aren't the same on Test that they are on Open (server specs, load, etc)
|
Sven has so far been the only one to pin point the main problem. Test and Live are two totally different environments. I'm a tester and I applaud all the testers out there who take the time to actually test the new builds and file reports and I'm just as frustrated as anyone else, but the bottom line is some of the issues that are found and reported can't be fully resolved in the current testing enviroment we have.
All of the reports being sent in are great and I'm sure they're being looked at. The problem is that bug reports can't supply one very important piece of information. That information being "how does this build react under a full stress load?". Knowing what bugs have been found is great but until they know how the build is going to react on a busy or full server, they can't really completely fix the issues.
They tried to solve the problem by opening up test to more people, so far that hasn't worked out. On the 2 servers we have available for testing, I've yet to see either of them reach "Ideal" status no matter what time of day I go on let alone reach the "Full" mark. Unless that changes the developers can't get all the data they need to solve these problems before a build is released. And if they can't get that data from the test servers they really have no choice but to release them to live so that they can see how the build behaves under stress.
-gets down off soap box, goes drinks rum-