MistyLaraCarrara opened this issue on Aug 12, 2009 ยท 102 posts
bagginsbill posted Thu, 13 August 2009 at 8:20 AM
Aaah, EC, I just began to understand what two things you've connected.
The "development" of Alyson happened before testing began, just as the development of the application happened before testing began. By definition, the testers don't see a figure until it is nearly a finished product, just as with the software. The testers can influence some minor things, but they are generating so much information about crucial things that minor things do not get addressed.
In the case of Alyson, I meant that the only people seeing Alyson at a time when it would be reasonable to change her shape were SM employees, not Beta testers.
You used the word "Beta" tester, and I (perhaps wrongfully) assume that when people use that term, they know why they're using it, what it means. In the software industry, testing has many forms and happens throughout the development cycle. But Beta testing specifically involves actual customers and happens as the very last step before product release. Traditionally, though not in practice, the software is termed "frozen" during Beta. No new features are developed, only problems found by the testers can be solved. This is considered best practice. Beta cannot begin until development is largely finished.
By the time Beta test rolled around, the only things being fixed on Alyson were things like missing bend limits, poke through, missing morphs on clothing, etc. No feedback at that point was going to get the lips or chin or collarbone changed.
Furthermore, the testers were far more concerned with testing the software. Think about it - users can morph Alyson themselves, but they can't change the software if something is wrong or unappealing.
And sometimes, the fixers would accidentally break something else. I suspect the Face Room data for Alyson was an example. While tweaking some parameter, perhaps somebody accidentally changed another one.
That's why there is a thing called a regression test. In a regression test, you verify that while fixing bugs, you did not accidentally introduce new ones. You do this by testing everything you've tested before and you thought it worked right.
Regression testing is impossible with Poser content. There's no way to automate it, so everybody would have to do everything they ever did over again.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)