I am testing multiple apps because : Testing is what I do.

What takes the longest bugs or features? That depends on what feature or bug you are talking about.

There is one bug that will take about a year (if not 2) to fix, 6 months to finetune and certainly 6 months of testing. The bug everybody knows about : The unwanted welding/unwelding of vertex groups.=> And EVEYTHING related to this bug : Like the vertex group editor, then you fly right into the hair room, the setup-room, the fitting room and so on, til the very-very basic of "save or export the obj file". This "masterbug" as it is called touches each and every part of Poser so it will take time. LOTS of time.

Fixing a bug might be difficult or easy. Depends. Are both Windows and Mac involved? How deep do we go back in the code, and what features crossed our path in finding the bug?.

Adding a feature? Tja, is it something completely new like the measurement tool. Rather easy as it is a "stand alone feature".

Adding a node is rather easy after you have figured out the math.

Adding or correcting how the setup-room behaves brings you also to the fitting and the hair room, So? Not so simple.

Speaking for Poser? I have seen bugs repaired/fixed in less then a week while others like "the masterbug" have been open for years because , well, it goes back to the very-very early years of Poser and it's initial link to Max. (Unwelded vertex groups with double vertex at all welds).

Ach, it is more or less the same thing/workflow/timetable for all apps I test.

**See the disaster of the latest Windows 1809 Oktober release. **

Best of intentions, a million beta testers, and see the result at roll-out. My conclusion for this Windows thing, (and others apps as well) is simple => Wrong or bad choice of beta testers. It is a JOB you know. And for the Companies? ? ? LISTEN to your beta testers.