The Tesults web app is designed for desktop browsers. Sign up and configure your project on a laptop or desktop. Use the iOS app or Android app to view results on the go.

Team Member Roles

Expanding roles for better management of larger teams

blog-title-image

Team member roles are being expanded from three types to five. This will allow larger teams to manage Tesults projects more easily and efficiently from now on.

The old moderator and regular member roles will stay the same, while the administrator role gets split into three new roles. Here are the five new (and now current) roles:

1. Member

Most team members should be ordinary members. Members can view results for the project, triage assign failing test cases and receive notifications.

2. Moderator

Team members assigned as moderators can do everything a member can do. They can also submit manual test results, delete test runs, trigger notifications manually and change the results of test cases. Changing a result is useful in the case of a false negative or positive result.

3. Administrator

Administrators can do everything a moderator can do. They can also edit team members (promote other users up to administrator level), add, edit and delete targets, edit project information.

4. Officer

Officers can do everything an administrator can do. They can also change the project plan, edit and update payment information. They can promote other team members up to Officer level.

5. Owner

The project owner can do everything an officer can do. They can also delete a project and receive billing emails. There can only be one project owner. Project ownership can be transferred to another team member.

The creator of a project will automatically be assigned the owner role. Any team members that are added to the project will be assigned the Member role as default. The owner can assign any team members that should be able to access payment details or project plan configurations as officers. The owner can also assign team members to be administrators to carry out project configuration including target and team member editing. For editing test case results, adding manual test results, deleting test runs and managing test lists members should continue to be assigned as moderators.

Have questions or feedback? Please get in contact. We hope this new flexibility around team member roles will make your Tesults projects easier to manage.

-Tesults Team

Test automation reporting and failure intelligence

Consolidated test reporting for engineering teams. Store, track, and understand test results across every run and system.

Latest Posts

Why Cypress Tests Pass Locally but Fail in CI
Why Cypress Tests Pass Locally but Fail in CI
The environment differences that cause Cypress failures in CI, and how to tell a real bug from an environment flake
How to Track Test Pass Rate Over Time
How to Track Test Pass Rate Over Time
Why a single run cannot tell you if your test suite is getting healthier or worse, and how to track pass rate as a trend across runs so you can see the direction
How to Report WebdriverIO Test Results to a Dashboard
How to Report WebdriverIO Test Results to a Dashboard
Send WebdriverIO results somewhere durable and team-visible using the Tesults service, with the wdio.conf.js setup, enhanced reporting, and parallel run consolidation
How to Report Cypress Test Results to a Dashboard
How to Report Cypress Test Results to a Dashboard
Send Cypress results somewhere durable and team-visible using the Cypress Module API, with screenshots and videos attached and runs consolidated across CI
Why Playwright Tests Pass Locally but Fail in CI
Why Playwright Tests Pass Locally but Fail in CI
The real reasons Playwright tests go green on your machine and red in CI, how to debug each one, and how to tell a genuine failure from an environment flake
How to Detect and Handle Flaky Tests
How to Detect and Handle Flaky Tests
What makes a test flaky, how to detect flaky tests automatically instead of by memory, and how to handle them without disabling coverage
How to Report Vitest Test Results to a Dashboard
How to Report Vitest Test Results to a Dashboard
Send Vitest results somewhere durable and team-visible, with the setup details specific to Vitest, so multiple test jobs consolidate into one history you can act on
How to Report Go Test Results to a Dashboard
How to Report Go Test Results to a Dashboard
Go has no reporter plugin, so reporting go test results means parsing go test -json and uploading the cases yourself. Here is the whole pattern.
How to Report Jest Test Results to a Dashboard
How to Report Jest Test Results to a Dashboard
How to send Jest results somewhere they are kept, viewable by the team, and comparable across runs, without giving up the default reporter
How to View Playwright Test Results in CI
How to View Playwright Test Results in CI
How to get Playwright results out of the CI console and into a durable dashboard, including parallel shards, screenshots, and retained history
What Is a Test Results Dashboard and When Do You Need One
What Is a Test Results Dashboard and When Do You Need One
What a test results dashboard actually does, how it differs from your CI logs and your test framework report, and the point at which a team starts needing one
Diagnosing CI Failures Automatically With an AI Failure Diagnosis API
Diagnosing CI Failures Automatically With an AI Failure Diagnosis API
How to turn a red build into a root cause, a regression list, and a deploy gate without a human reading the logs