Hello all,
I'm posting to try and get a handle on what people are doing to evaluate new releases of ProEngineer.
What do you do?
Do you use trail files,
run scripts,
is it an automated / manual process
how long does the test run for
what determines a successful test
how mush effort is required..... $$$
do you have a testing procedure, how does it evolve as the software evolves, ie do you test new features etc,
is the same dataset used to test each release of proe.
anything else ?
I find it hard to 'lock down' a test procedure. Many things, such as the old, backward compatibility failures between releases do not help, getting approval to use an engineer for testing etc....
any help will be more than appreciated!!
I'm posting to try and get a handle on what people are doing to evaluate new releases of ProEngineer.
What do you do?
Do you use trail files,
run scripts,
is it an automated / manual process
how long does the test run for
what determines a successful test
how mush effort is required..... $$$
do you have a testing procedure, how does it evolve as the software evolves, ie do you test new features etc,
is the same dataset used to test each release of proe.
anything else ?
I find it hard to 'lock down' a test procedure. Many things, such as the old, backward compatibility failures between releases do not help, getting approval to use an engineer for testing etc....
any help will be more than appreciated!!