How Test Hub Fits Your Application
A simple mental model for using Test Hub to test customer journeys.
Test Hub follows the same simple cycle your team already uses when preparing a release: decide what matters, test it, understand the result, and act when needed.
Built on SolidX's Core Testing Framework
Test Hub runs your tests using SolidX's Core Testing Framework — the same metadata-driven engine that powers automated API and browser (Playwright) testing across SolidX. Test Hub adds the product experience on top: registering applications, authoring scenarios with the MCP AI assistant, running them, and reading results. To understand the underlying framework, see SolidX Core Testing Framework.
The mental model
| In Test Hub | What it means for your application |
|---|---|
| Application | The website, service, or area of your business that you want to test. |
| Customer journey | An important task someone must be able to complete, such as signing in or placing an order. |
| Test scenario | A saved test for one customer journey, created with the MCP AI assistant. For example: confirm that a customer can sign in. |
| Test run | The occasion when Test Hub runs one or more selected test scenarios. |
| Result | A clear record of which customer journeys passed and which failed. |
A typical release flow
- Choose the customer journeys that must work for the release.
- Describe those journeys to the MCP AI assistant so it can create the test scenarios.
- Run those tests before approving the release.
- Review the result: all clear, or identify the journey that failed.
- Share the result with the people who need to act.
- Keep the same tests running regularly so problems are found sooner next time.
Start small
Begin with the three to five journeys that would most affect customers or the business if they failed. You can add more as the application grows.
Example
For an online school-fee portal, the first tests might be:
- A parent can sign in.
- A parent can see the amount due.
- A parent can complete a payment.
- The school team can see that payment in the portal.
These tests give the product owner a fast, repeatable answer to whether the most important experience is ready for customers.