Testing Processes in Windchill PLM

[ptc-6026219]

Hi Guys,

Please give me an idea about the testing processes in Windchill PLM.

1. Where does the testing process start?

2. What are the factors to be considered?

3. Who are all involved in the testing process?

Please share a link if it answers all my questions.

Thanks in advance.

Regards,

Rajeshkumar

[AL_ANDERSON]

There are a lot of different models for software testing, and you have to find one you like, and then implement it.

In a very general sense, you want to be sure to include the following elements in your test plan.

1. Out of the box functionality for basic use cases (Search, Create/Update Part, etc.).
2. Workflows of any kind
3. Custom code of any kind
4. Access control based on what you expect to happen based on your access control plan. Once you have validated your access control plan, then you don't have to retest this on upgrades since upgrades won't mess this up like it often will with workflows and customizations.
5. Performance (click to result) for any slow or critical tasks
6. Load testing (use an automated tool to simulate a large concurrent load to see how your system performs under high concurrent use)
7. Process testing that validates your business process as it flows in and out of Windchill as a supporting application.

Al

[Nitin]

It actually depends more on the amount of customization you have in Windchill.

OOTB features neednot be tested for functionality testing since PTC spends considerable efforts in testing those. Based on customization, you then have to diverisfy into UI testing, Performance Testing, Functionality testing.

If you have third party applications integrated with Windchill, you will have to consider testing to and fro transactions. if you have considerable time and resources, you can think of unit code testing during development phase using jUnit.

If you are in starting phase, start identifying customization and write test cases for the same. Based on resource and time availabilty, decide where you can have automated testing and where manual testing is required.

-Nitin

[AL_ANDERSON]

"OOTB features neednot be tested for functionality testing since PTC spends considerable efforts in testing those."

PTC tests out of the box features on a variety of supported platforms, but they don't do so on our data on our platforms. For example, we use IE9 and Google Chrome Frame. We have experiences with file upload and download not working right for all interfaces on upgraded systems depending on the browser, so we test that out of the box functionality on every upgrade.

"Add to workspace" is another out of the box task that PTC tests, but we have had trouble with it on our large assemblies after upgrades in the past, so we test that too on our small, medium, and largest assemblies. We also performance test "Add to workspace" as well as other critical out of the box tasks that have been slow in past upgrades like "Create and Classify Part," so we can spot problems early, and work with PTC to optimize our system to make them as fast as possible.

So, while I agree that testing all out of the box functionality is a waste of time, I strongly believe that not testing any out of the box functionality will just delay finding errors and bottlenecks unnecessarily that you would catch faster if you identified critical out of the box functions under production-like conditions to verify that it works as you would expect.