Setting Up TimetoTest for Your Team

Good testing works better when everyone shares the same context. TimetoTest gives your team one place to run UI checks, API checks, and code review checks, then review the evidence together.

1. Create your team

Open the Team page and select Create team. Give your team a clear name, such as “Product QA” or “Acme Engineering”.

Your team becomes the shared space for projects, test runs, reports, and collaboration.

2. Invite your teammates

From your team page, select Invite member. Enter your teammate’s email address and choose a role:

• Admin: manages members, invitations, and roles.

• Member: works with shared projects and test runs.

• Viewer: reviews team activity and results.

Your teammate must accept the email invitation before gaining access. If they do not have an account, the invitation flow guides them through account setup.

3. Create your first project

Create a project for the application or API you want to test. Add a project name and configure the relevant UI or API base URL.

Use a staging or local environment that your team can reset. If your checks need additional context, add requirements, specifications, documentation, credentials, or test data through the project setup flow.

4. Run your first check

Start with one focused user journey or API contract. Describe what should happen in plain language.

For example:

As a signed-in user, open /cart, add the first product, and verify that the cart shows the product name and price.

TimetoTest can discover the relevant interface, perform the actions, verify the result, and collect screenshots, tool activity, errors, and other evidence.

5. Review and share the result

Use the Agent view to follow progress. When the run finishes, review the report and evidence with your team.

A passing run is evidence for the tested path. It is not proof that every part of the product is defect-free. Use failed runs to create focused follow-up checks and improve your coverage.

6. Turn useful checks into team coverage

When a prompt proves useful, save it as a test case. Keep each test focused on one business outcome. Add exact roles, starting pages, test data, and pass or fail conditions.

Over time, your team builds a shared library of repeatable checks instead of relying on manual memory.

Code Review and Code Workspace Tests

Connect your codebase to TimetoTest to run repository-aware checks alongside your UI and API tests. TimetoTest supports GitHub, GitLab, and Bitbucket Cloud.

Connect your codebase

1. Open the project where you want to run the test.

2. Open Project integrations.

3. Authorize your GitHub, GitLab, or Bitbucket Cloud account.

4. Select and connect the repository.

5. Confirm that the project can access the required branches and pull requests.

6. Review repository permissions before enabling write actions.

Code Review tests

Use Code Review tests to inspect a pull request, merge request, or specific change set before merging.

Keep each review focused on one change. Ask TimetoTest to check for logic errors, broken behaviour, security risks, missing test coverage, and unintended side effects.

For example:

Review this pull request for logic regressions, security issues, broken edge cases, and missing test coverage. Report each finding with the file name, line number, severity, impact, and supporting evidence.

Select the connected repository and target pull request or merge request. When the review finishes, inspect the findings, changed files, and evidence with your team.

A passing review confirms that the selected change was checked. It does not prove that the entire codebase is defect-free.

Code Workspace tests

Use Code Workspace tests when you need TimetoTest to work with a connected repository and a selected branch.

Connect the repository first, then select the codebase and branch. Describe the task, expected result, scope, and tests that should be run.

For example:

On the feature/checkout branch, inspect the checkout flow, find why expired coupons are accepted, implement the smallest safe fix, run the relevant tests, and return the changed files and test results.

You can use Code Workspace tests to:

• Inspect an unfamiliar codebase.

• Investigate a bug.

• Trace a feature across multiple files.

• Implement a focused change.

• Run relevant checks after a code change.

• Review the resulting diff and test evidence.

Be clear about whether TimetoTest should only inspect the code or make changes. Keep the task limited to the required files and branch. Repository access, permissions, provider setup, and project configuration determine what TimetoTest can read or change.

Recommended code workflow

1. Connect the repository to the correct project.

2. Select one branch or pull request.

3. Write one focused task.

4. Review the proposed changes and evidence.

5. Run or inspect the relevant tests.

6. Approve and merge changes only after your team has reviewed the result.

Over time, save useful Code Review and Code Workspace prompts as reusable test cases. This gives your team a repeatable way to review changes, investigate bugs, and maintain code quality.

Team setup checklist

• Create your team.

• Invite teammates with the right roles.

• Create a project and configure its target URL.

• Add requirements or test data when needed.

• Connect your code repository.

• Run one focused UI, API, or code check.

• Review the evidence together.

• Save valuable prompts as reusable test cases.

Start testing together

Once your team, project, repository, and first check are ready, you have a repeatable foundation for UI testing, API testing, code review, and code workspace workflows.

Create your team, invite your collaborators, connect your codebase, and run your first evidence-backed check with TimetoTest.