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.<\/p>\n
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\u00a0upgrade to 6.6 and your repositories will be upgraded without incident.<\/p>\n
Details: looking for the gory details? A change in the serialization format for exceptions thrown by the Selenium\/WebDriver library makes it impossible for\u00a0newer versions to be\u00a0read from\u00a0old replays and test results. So if\u00a0a 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.<\/p>\n
We apologize for the inconvenience. Fortunately, the workaround\u00a0is pretty easy \ud83d\ude42<\/p>\n
Chris Merrill, Chief Engineer.<\/p>\n","protected":false},"excerpt":{"rendered":"
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.
\nTLDR: 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 … Continue reading »<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,42],"tags":[49,255,253,251],"class_list":["post-5673","post","type-post","status-publish","format-standard","hentry","category-load-testing","category-load-tester-software","tag-load-tester","tag-repository","tag-upgrades","tag-upgrading"],"_links":{"self":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/5673","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/comments?post=5673"}],"version-history":[{"count":1,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/5673\/revisions"}],"predecessor-version":[{"id":5674,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/posts\/5673\/revisions\/5674"}],"wp:attachment":[{"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/media?parent=5673"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/categories?post=5673"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webperformance.com\/load-testing-tools\/blog\/wp-json\/wp\/v2\/tags?post=5673"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}