Skip to content
Fenwave
en
All use cases
QA & test engineers

Run the suite against any branch, from the browser

Pick component and branch, run, and keep the result attached to that branch.

Before Fenwave1 day waiting

“Can you run the integration suite on my branch? I do not have the CI permissions to trigger it manually”

What the wait costs

Tests run when someone with permission remembers, which means they run at the end — where failures are most expensive.

With Fenwave1 click

In Fenwave

Tools›Test Runner›New run

Capability

Test Runner & Stress Testing

Test Runner puts the trigger where the person who wants the answer already is. Choose a component and a branch, start the run, and read the summary, the per-test results and the full logs on the same page. The history is kept, so "did this pass before the refactor?" is a lookup rather than an argument.

How it works

  1. 01Select the component and the branch to run against.
  2. 02Start the run; progress and logs stream on screen.
  3. 03Read the results summary with per-test detail.
  4. 04Compare against previous runs in the history table.

Related use cases

QA & test engineers

Find the limit before the marketing campaign does

k6 load tests with thresholds that pass or fail a run, not charts to interpret.

until it does not30 minutesTest Runner & Stress Testing
QA & test engineers

Test a build that will still be there in an hour

Your own environment per branch, so nobody redeploys under you mid-campaign.

every sprinton demandEnvironment Manager
QA & test engineers

Reproduce the bug on the exact build the customer has

Deployment history tells you which commit is live where, so you test the right thing.

2 hours1 minuteDeployment Manager

See Fenwave on your own projects

Thirty minutes, on your repositories and your clusters. We will point out three requests your platform team would stop receiving as soon as next week.