> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/upgrade/10.5.0/tests.md).

# Tests

## Clear browser cache

It's important to clear your browser cache before connecting to the upgraded WorkflowGen website. This will remove the CSS, JavaScript, and image files used in previous versions of WorkflowGen.

## Web app addresses

Use the following URLs with the `wfgen_admin` user account:

* **User Portal:** `http://[yoursite]/wfgen`
* **Administration Module:** `http://[yoursite]/wfgen/admin`

## Node.js-based web application checks

If the optional Node.js-based web applications are enabled, verify the corresponding endpoints after the upgrade.

Verify that IIS and every enabled Node.js child application use the intended Node.js 24.22.1 runtime. 

Test representative authenticated operations for authentication, GraphQL, incoming webhooks, and SCIM, and keep the MCP checks below. 

For GraphQL with PostgreSQL application authentication, verify a request that reads the WorkflowGen database. 

For incoming webhooks, use the configured authentication mode and confirm that its existing custom settings and file upload restrictions are retained. An endpoint responding alone is not proof that all authenticated operations work.

For MCP Server, verify:

* **Health endpoint:** `https://[yoursite]/wfgen/mcp/health`
* **OAuth protected resource metadata:** `https://[yoursite]/wfgen/mcp/.well-known/oauth-protected-resource`
* **OAuth authorization server metadata:** `https://[yoursite]/wfgen/mcp/.well-known/oauth-authorization-server`

If MCP OAuth is enabled, test a connection from a supported MCP client using `https://[yoursite]/wfgen/mcp`.

{% hint style="info" %}
This MCP client connection test applies only to WorkflowGen sites configured with OIDC or SAML authentication. Other WorkflowGen authentication modes are not supported as MCP browser login sources.
{% endhint %}

## Windows service and Change events checks

After restarting the upgraded Engine Service, verify that the WorkflowGen Change events source is available in the Windows Application log. The service attempts registration automatically. If registration fails because the service identity lacks permission, have an administrator register the source and repeat the diagnostic check; reinstalling all services is not a general upgrade requirement.

## Application and configuration checks

* After restarting the upgraded application and services, verify sign-in, an existing request and a representative request/action lifecycle, background processing, and directory synchronization. 
* Check the enabled Node applications, including an authenticated GraphQL/PostgreSQL operation where that configuration is used.
* Verify the selected PDF profile, custom menus/assets, saved search views and required searches. 
* Test full-text search after the required indexing has finished; test semantic/hybrid search only where vector storage and an embedding provider are configured.
* If you're switching Remote Approval to Graph, verify a controlled approval reply as well as the connection test. Inspect the Windows Application log and Change events diagnostics. Keep database, application and configuration rollback material together.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.workflowgen.com/upgrade/10.5.0/tests.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.