WOPI-Test doesn't works anymore?

Simone Nigro 5 Reputation points

Hi, I successfully implemented and got WOPI approved a few years ago. Nowadays the application works as expected, but when I open the WOPI test page, I see an error in the console and the test does not work.

Uncaught ReferenceError: g_TestGroups is not defined on wopivalidator.js

Does anyone know why this might be happening? If run test with the open source validator https://github.com/microsoft/wopi-validator-core It's ok

Update, I have also opened a github issue https://github.com/microsoft/wopi-validator-core/issues/146

0 comments No comments
Sign in to comment

2 answers

  1. Gabriel-N 19,035 Reputation points • Microsoft External Staff • Moderator

    Hello Simone Nigro

    For the question you raised, please first refer to the response provided by Q&A Assist.

    In addition, I’ve seen some reports with this exact error appearing around April 2026. Since Microsoft’s documentation still labels the hosted validator as “Operational” with no announcement of deprecation or retirement, this seems to be an unintended issue.

    For now, a possible workaround is to use the official open-source WOPI Validator (the wopi-validator-core tool on GitHub) to validate your implementation.

    You may also consider reaching out to Microsoft support and submitting feedback through the Feedback Portal so the product team can investigate further.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1. Simone Nigro 5 Reputation points

      Thanks for the clarification. At the moment I’m not sure how to proceed, because the hosted WOPI test page itself does not seem to be working correctly on my side due to the g_TestGroups is not defined error.

      The implementation appears to work correctly, and the tests pass when using the open-source validator (wopi-validator-core), but without a functioning hosted validator it’s difficult to verify whether there are any additional compatibility issues or if the problem is only with the test page itself.

    2. Gabriel-N 19,035 Reputation points • Microsoft External Staff • Moderator

      Hello Simone Nigro

      Thank you for your feedback, I understand your concern, and honestly I’m seeing the same confusion on my side as well.

      At the moment, since the open-source wopi-validator-core tool executes the same set of validation logic, it is generally considered a reliable fallback for validating your implementation. If all tests are passing there, I think it is an indication that your implementation is compliant.

      For the hosted validator specifically, I’m afraid there isn’t much we can do from our side to directly fix or bypass the issue if it is occurring within the Microsoft-hosted environment. As this is a user-to-user support forum, moderators like us don’t have access to backend tools or internal systems to investigate or resolve issues like this. Because of that, it would be best to report this to Microsoft CSPP support or submit feedback via the Feedback Portal so the product team can investigate further.

      May I kindly ask whether you have already contacted CSPP support, submitted a ticket through the Admin Center, or raised feedback via the Feedback Portal?

    3. Gabriel-N 19,035 Reputation points • Microsoft External Staff • Moderator

      Hello Simone Nigro

      Is there any update from you? If yes, please feel free to let me know.

    4. Simone Nigro 5 Reputation points

      Hello @Gabriel-N
      I have send a detailed mail at csppteam(at)microsoft.com

      Thanks!

    5. Gabriel-N 19,035 Reputation points • Microsoft External Staff • Moderator

      Hello @Simone Nigro

      Thanks for the update, it’s good to know that you have already contacted the CSPP team. Please keep us updated if you receive any further response from them, as it may also help others facing the same issue. Hope this issue will be addressed soon.

    Sign in to comment

  2. AI answer

    The WOPI Validator is currently operational and is the supported way to validate a WOPI implementation. The validator is exposed as a Microsoft 365 for the web application via the .wopitest extension and the WOPI discovery XML, and new tests are added regularly.

    When the validator page shows script errors or appears not to work, the usual causes are environmental or integration-related rather than the validator being retired:

    1. Ensure the latest validator is being used
      • Use the Test/Dogfood environment discovery URL to pick up the latest WOPI Validator definition:
        • Test/Dogfood discovery: https://ffc-onenote.officeapps.live.com/hosting/discovery
      • Confirm that the WopiTest app and its view and getinfo actions are present in discovery and that the host is using those URLs exactly as provided.
    2. Verify .wopitest integration
      • Confirm the host treats .wopitest files exactly like other Microsoft 365 documents:
        • Launch the same host page used for normal Microsoft 365 for the web sessions, but pointing at a .wopitest file.
        • Ensure the iframe is navigated to the view action URL from discovery with correct WOPIsrc and access token.
      • If the file extension or host page behavior changed since the original approval, update the integration so it matches the current guidance.
    3. Check WOPI domain allow list
      • The validator (like all WOPI actions) will not function unless the WOPI domain is on the WOPI domain allow list. If the domain, endpoints, or DNS changed since the original approval, ensure the current domain is still on the allow list.
    4. Use the open-source validator for additional diagnostics
      • The WOPI Validator is also available as an open-source tool at https://github.com/Microsoft/wopi-validator-core. Running it in a controlled environment can help isolate whether the issue is specific to the hosted validator or to the host’s integration.

    If the hosted validator still fails after confirming discovery, .wopitest handling, and allow-list status, use the open-source validator and the troubleshooting guidance to gather evidence (including console errors and network traces) before engaging Microsoft, as passing validator tests is a prerequisite for further investigation.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer