| PLEX86 | ||
|
MS Office on Linux 14819
Lin¿nut No you won't. Why? Consider that someone will be using the software for so many hours a day. That will be the use regardless of whether it is a stable release or a fresh, out of the box release. For the former, the user is doing some useful work, presumably, and is really exercising the system overall. Each session that uses a new feature tests that feature and the rest of the session that uses old features is effectively regression testing the old features in the new release. MS Office on Linux 14821 billwg poked his little head through the XP firewall and said: True, but that time is short. So what? My testing is by... If the person is trying new builds, there is first of all a time loss involved with installing the new version. That either takes away from the in-use time or requires extra time, either way, it is time lost from testing. Then the new version may not be as thoroughly tested because the exercise of many functions does not occur each time the product is used, so whatever time was spent testing something in an old version, it has to be tested again in the new since it might have been changed. MS Office on Linux 14820 billwg poked his little head through the XP firewall and said: Okay. The time loss is minimal, believe me. Even a complex upgrade such as upgrading the GNU C runtime library, gcc, takes no time... All companies that have complex software products regularly establish "best tested" builds that the QA group really wrings out to see how the quality is going. Daily builds are for developers to see the integration of their latest efforts with everyone else's stuff.
|
||||||||