cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X

Valadaiting your upgrade

Robert-Altman
7-Bedrock

Valadaiting your upgrade

Has anyone documented steps that would represent best practices for validating the integrity of their CAD data after upgrade to a newer release of Creo

Something more than performing the upgrade and just randomley opening files and visually looking to see if there were any issues related to the upgrade?

Thanks in advance for you time,

Robert


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
1 REPLY 1

Hello Robert,

Typically nowadays Creo models do not regenerate in a new release, so just opening them would not be much of a test.

I recommend a forced regeneration for a proper test instead (and if it fails try the same in the previous release - often enough the issue already existed, but never surfaced, because models didn't get fully regenerated for a long time)

Our QA department - together with other tests - uses automated tests by running trail file sequences or Toolkit applications.

Apart from obvious errors like model or actions failing (usually triggering error messages in the trail files that can be parsed), occasional screenshots help them detect differences comapred to previous versions (some of their tools do bit comparison with pictures shot during previous tests).

Of course whenever any discontinuity is detected by the automatism, a QA engineer has to re-check, as there are many things that can go wrong with automated tests and it does not always indicate an actual issue with the software.

But as long as the results are exactly the same as before, this will be a proof of consistency - probably more exact than the user could do it.

Of course at PTC we use the regression tests for every new datecode and they usually run without issues.

However, btween releases it is more likely the tests will fail due to changes to the UI, although there is no issue with the model data.

Regards,

Gunter

Top Tags