Introduction to testing
Built-in test tools
The Thinkwise Platform provides built-in tools and integrations with external tooling to test your application during multiple phases of the DevOps lifecycle.
You can automate the built-in Unit tests and Smoke tests using the CI/CD tools mentioned in Build integrations. For functional testing you can add manual Test scenarios within the Software Factory. We recommend test automation for testing End-2-End functionality using best-of-class external tooling. The Process tests that could be used in combination with the Windows GUI are deprecated.
Additionally, you can use a wide range of third-party tools for various types of tests.
Third-party test integrations
Functional, regression, and API testing
It is not necessary to test standard functionality that is provided by the runtime components, like navigation, sorting, filtering, and CRUD functionality. Thinkwise ensures the quality of these components and tests them extensively. Only customer-specific business logic and interfaces require testing.
You can use the following tools for testing customer-specific business logic and interfaces:
- Playwright - recommended for automated UI/integration/end-to-end testing in combination with our Testwise package
- Cypress - automated UI/integration/e2e testing
- TestComplete
- Azure Test Plans - manual testing
- Selenium
- BrowserStack - testing on all browsers and mobile devices
You can use the following tools for testing the Thinkwise API:
Load, performance, and stress testing
Testing performance is generally done against the Indicium API.
You can use the following tools for testing performance:
For more information on setting up load tests for Thinkwise applications, see Load tests.
We do not recommend using Selenium-based tools for performance testing. See this article.