Change sample testing report URL (#42499)

mrdarrengriffin · web-flow · commit 34d1fb524aec · 2025-12-10T11:26:39.000Z
diff --git a/source/_posts/2025-12-09-wwha-2025-recap.markdown b/source/_posts/2025-12-09-wwha-2025-recap.markdown
@@ -66,7 +66,7 @@ This commitment to inclusivity is a big reason why we keep the annual fee for jo
 
 Testing hasn&rsquo;t always been perfect &ndash; we knew we needed to make improvements, and the community has been amazing in helping us find things we need to look at. Like everything we do, we learn as we go, we iterate, and we improve. Previously, everyone was testing in their own way, but now we&rsquo;ve standardized the way we test and give feedback to partners. This means testing is more consistent, exacting, and able to handle higher volumes &ndash; one of the reasons why we&rsquo;ve been able to increase the number of devices we&rsquo;ve certified so radically!
 
-A lot of devices that come across our desks don&rsquo;t pass certification, and it's often due to organizations not fully understanding the requirements of joining. While this can vary greatly depending on the device and protocol, it was clear we needed to be more transparent. So as well as publishing our [Works with Home Assistant Working Group Resolution](https://www.openhomefoundation.org/documents/), we&rsquo;re also publishing further testing information: this [sample testing report](https://drive.google.com/file/d/1FNrX3l_9wAtjtCjrHHhy-9dWs2fLJYhf/view) for a simple smart plug shows you the process we follow.
+A lot of devices that come across our desks don&rsquo;t pass certification, and it's often due to organizations not fully understanding the requirements of joining. While this can vary greatly depending on the device and protocol, it was clear we needed to be more transparent. So as well as publishing our [Works with Home Assistant Working Group Resolution](https://www.openhomefoundation.org/documents/), we&rsquo;re also publishing further testing information: this [sample testing report](https://drive.google.com/file/d/11jG9Al563XKK8N1XlPl3rzU73TUFbdyl/view) for a simple smart plug shows you the process we follow.
 
 ## Keeping Home Assistant on the bleeding edge
 

-Original file line number
+Diff line change
 Testing hasn’t always been perfect – we knew we needed to make improvements, and the community has been amazing in helping us find things we need to look at. Like everything we do, we learn as we go, we iterate, and we improve. Previously, everyone was testing in their own way, but now we’ve standardized the way we test and give feedback to partners. This means testing is more consistent, exacting, and able to handle higher volumes – one of the reasons why we’ve been able to increase the number of devices we’ve certified so radically!
 -A lot of devices that come across our desks don’t pass certification, and it's often due to organizations not fully understanding the requirements of joining. While this can vary greatly depending on the device and protocol, it was clear we needed to be more transparent. So as well as publishing our [Works with Home Assistant Working Group Resolution](https://www.openhomefoundation.org/documents/), we’re also publishing further testing information: this [sample testing report](https://drive.google.com/file/d/1FNrX3l_9wAtjtCjrHHhy-9dWs2fLJYhf/view) for a simple smart plug shows you the process we follow.
 +A lot of devices that come across our desks don’t pass certification, and it's often due to organizations not fully understanding the requirements of joining. While this can vary greatly depending on the device and protocol, it was clear we needed to be more transparent. So as well as publishing our [Works with Home Assistant Working Group Resolution](https://www.openhomefoundation.org/documents/), we’re also publishing further testing information: this [sample testing report](https://drive.google.com/file/d/11jG9Al563XKK8N1XlPl3rzU73TUFbdyl/view) for a simple smart plug shows you the process we follow.
 ## Keeping Home Assistant on the bleeding edge