Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Thilak Rathnayake (Thilak)
Macquarie Group
Senior Manager
Macquarie Group
AU
Thilak Member since 2014 9 posts
Macquarie Group
Posted: Sep 29, 2015
Last activity: Sep 30, 2015
Posted: 29 Sep 2015 21:48 EDT
Last activity: 30 Sep 2015 16:09 EDT
Closed

Automation Test Suits are broken after upgrade from V7.1.6 to V7.1.8

We have experienced automation Test Suits are broken after upgrade from V7.1.6 to V7.1.8.

This is basically due to object IDs are changed.

Is there a Pega recommended guideline (documentation) which developers and automation testers can use to minimize upgrade issues? Also, we need to leverage automation test suite to perform regression testing after upgrade.

Appreciate if any feedback.

Thanks,
Thilak

To see attachments, please log in.
Updates

Posted: 9 years ago
Posted: 30 Sep 2015 8:56 EDT
Jackson2 (RichardJackson2)

Hi Talik,

What are you using for your automation tests? I experienced similar problems with JMeter tests, and the fix was to use a regular expression extractor to get the harness IDs and pass them in as variables later in the thread groups. Perhaps someone will weigh in with the technical details of what changed, but I thought if you were using Jmeter this info might help.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice