Klarent

The ‘zero-effort discovery’ feature allows teams to provide a website URL, PRD, Jira ticket, Figma link, document, or existing test. Klarent’s AI agent analyzes the input and identifies relevant test cases, including potential edge cases and overlooked user flows. Users can then accept or reject the suggested scenarios before turning them into tests. This enables teams to identify a wider range of test scenarios without having to define each one manually.

The solution’s ‘Test Management Platform’ organizes tests through projects, folders, and test suites. Projects separate applications or teams and keep their credentials and test configurations isolated. Within each project, a nested folder tree groups tests by features, modules, or team responsibilities. Once tests are organized, test suites group selected tests for smoke testing, regression, or compliance testing. Teams can run suites on demand or schedule them for repeated execution. They can then review run history, pass rates, failure trends, and test stability.

Klarent’s ‘Variables’ enable teams to assign values to individual tests, such as URLs, usernames, form inputs, headers, and assertion values. These variables can be added during test creation and inserted into any relevant step using the @ shortcut. Teams may also change variable values when running a test in different environments. Each variable remains limited to the test where it was created. This could help decrease the need to hardcode changing values into individual test steps.

‘Secrets’ store sensitive values such as passwords, API keys, and tokens as encrypted parameters within a project. Teams can define a secret once and use it across the project’s tests without placing the value directly in test steps, logs, or test results. The platform enables users to create these directly from the test creation flow or the Test Data settings panel. Keeping these credentials separate from test code could potentially lessen the risk of exposing sensitive values during test creation and execution.

The platform’s ‘assets’ functionality enables uploading files such as images, PDFs, and CSVs to a project and reusing them across multiple tests. Users can reference these files in upload or input steps with the @ symbol, so they do not need to upload the same file for each test. Teams may also replace or remove an asset without changing the existing text reference. This can make it easier to maintain tests that depend on shared files.