Upgrading repositories from 6.5 to 6.6 - Web Performance

Upgrading repositories from 6.5 to 6.6

I’m more than a little proud that we have been able to keep our repository format backwards-compatible for the entire life of the product, with only a few minor bumps along the road. Unfortunately, that streak has come to an end. Thanks an oversight on my part in reviewing the compatibility of a 3rd-party library, some 6.5 repositories cannot be upgraded to 6.6 without some effort on your part.

TLDR: If you don’t use real-browser testcases, you get a pass – just upgrade as usual. Otherwise, before installing 6.6, open your repositories in 6.5 and delete all replays and load test results for real-browser testcases that contain errors. Then you may upgrade to 6.6 and your repositories will be upgraded without incident.

Details: looking for the gory details? A change in the serialization format for exceptions thrown by the Selenium/WebDriver library makes it impossible for newer versions to be read from old replays and test results. So if a replay or load test result stored in the repository has an error that originated in WebDriver (specifically, a WebDriverException and subclasses), we can’t read it with 6.6.

We apologize for the inconvenience. Fortunately, the workaround is pretty easy 🙂

Chris Merrill, Chief Engineer.

Add Your Comment

You must be logged in to post a comment.


Copyright © 2024 Web Performance, Inc.

A Durham web design company


(1) 919-845-7601 9AM-5PM EST

Just complete this form and we will get back to you as soon as possible with a quote. Please note: Technical support questions should be posted to our online support system.

About You
How Many Concurrent Users