Software Testing / Software Quality
Since this is a relatively private forum, maybe we can have a frank discussion about software quality. This is an area where PTC is really falling down on the job. Maybe Creo Direct is great. Maybe Mathcad is pristine. But Creo and Windchill are rife with problems that any reasonable software testing regimen should catch before code is ever released to the public.
How can software be released when there are issues with saving or exporting a file? Example? Creo 2.0 M080 could not save or export a mechanism file. Oh, the message dialog box said the file saved... but, in fact, it does not. This is infinitely repeatable. Your only option, move to M090. Of course at M090 there are other problems. Saving the assembly used by your mechanism results in the file being dumped into your working directory (even if you're working within Windchill and are currently attached to an active workspace). How does this get through?!
So your next best bet is to move to M100... which is God-awful SLOW compared to M080 and M090.
So your next best bet is to move to M110... which cannot exit a sessionwithout complaining "Cannot exit. Background operations are occurring...". You must kill the xtop.exe process with Windows Task Manager to exit the program.
So your next best bet is to move to M120... or M130...
What. In. The. Actual. Hell. Is. Going. On.
How is this a defensible position? How can PTC ask customers to keep upgrading and upgrading and upgrading? How can customer support be so surly that their first line of defense is always to blame the customer? And the second line of defense is always to claim our problem is that we've not UPGRADED (again!).
It's one thing is we were running Wildfire 4.0 or 5.0 and complaining about bugs in the software. But when you're running the absolute latest Windchill 10.2 and the bleeding edge Creo 2.0 or 3.0 builds, how can it be necessary to continually upgrade to achieve even a basic level of stable software operation?
NASA seriously does not have the time or resources to dedicate to having people run around all day upgrading people! Not to mention, the software requires elevated privileges to install - which is increasingly causing problems that PTC sweeps under the rug. I won't even mention the system security issues in Windchill.
But before I scatter this mini rant too widely... let's refocus on software quality. There should be a team of testers and a test script. Someone should have to sign off on any changes made to the code. Simple things like interoperability between Creo and Windhcill should be a primary focus. But more than this, the absolute basics must be covered... like verifying that files are saved where they're supposed to be!
I feel like I've been a beta tester for this software for 25 years. It's really getting old. Major software vendors simply cannot crank out professional software without a strict, regimented, and thorough test plan. There's no way this is happening. Corners are being cut... this must be the case. If that's not true... then there are simply too few testers or they're signing off on code that wasn't actually tested. If you plop 1500 test scripts on a tester's desk and he's supposed to finish them all before code is released, what stops him from just signing off? If there's a deadline and he's going to catch grief from management for not completing his work on time, what prevents him from signing off and hoping that no one ever notices he never actually tested the code?
There is a problem somewhere... a big, big problem.... and it needs to be addressed.
If anyone has any feedback, comments... or even criticisms of my assertion that software quality is lacking, let's hear them. If we're not here to make a difference, what's the point, right?
