Quote:
Originally Posted by Cicatrize
Trueness. The other developer I work with and I rarely ever put anything out for beta testing unless we've tested it pretty thoroughly, and that's beta. On the rare occasion we do have an alpha, it's almost always unfinished, and is more of a demo of what's going to be available. Most of our alpha stuff is actually just GUI demo, and some parts of the code will actually throw errors. lol
There's nothing better than sending what YOU think is a finished beta product with no locatable bugs, then having the testing unit come back with like 15 bugs. hahah
Most of the time for us it's validation crap because people are kinda retarded and put stuff in fields that shouldn't go there.
|
omg i know what you mean. We've been working on a project that was due 2 months ago, and for whatever reason, 2 1/2 months or so ago our testing team said everything was a-ok. Then when it came down to like a week before our deliverable date, we started getting these lists of bugs sometimes containing more than 50 items at a time.
To make matters worse, the things they were reporting at first were the minor things (like a panel being not aligned with others, or a mispelled word) then as we got closer to launch, they started reporting errors on the major functions of the program. Then people are looking at US like WE made the mistake.
It's been a nightmare.