Testim Quick Start Guide
Testim Quick Start Guide
Getting started on the right foot can help ensure a more efficient and pleasurable experience. It can also
help you more clearly see the value of Testim while minimizing the frustrations of learning a new tool.
Signing-up is easy, just go to app.testim.io and follow the instructions. After you get into the Testim
application it will take you on a short walk through.
Clicking on the red record button will ask you to install the Chrome extension.
- Editor - Create new tests and edit existing tests in the visual editor.
- Test List - See all the tests, suites, labels, and shared steps you’ve created.
- Runs - View results of recent runs, see scheduled runs and run configurations.
Help resources
It’s a good practice to try the tool out on a predictable website while you figure out how to use it. We
recommend starting with a couple of simple tests, such as a login and logout test. Watch this short video to
learn how to create your first test.
After recording the test, you can continue to make changes to the test such as adding or removing steps,
inserting validations (assertions), adding conditions and more. Check out this video on editing your tests in
Testim.
After you create your test, you can run it locally to assess it by simply pressing the play button (triangle).
However, you may also want to schedule the test to run at a specific time or run it in your CI.
Scheduling
Set the time, frequency, test suites, labels, etc. that you want to run. See how to schedule your tests.
Results
There are multiple ways to see the results of your test runs whether executed on demand, on
schedule, or as part of a CI action. See test results.
Troubleshooting
Creating stable tests with a dynamic UI may require tweaks. It starts with understanding why your test failed.
Watch this video to see how to troubleshoot failed tests.
Locator issues
Locators sometimes identify the wrong element. Fortunately, we give you the tools and controls to
adjust the locators for tricky elements.
Synchronization issues
When your application under test (AUT) is performing at a different (usually slower) speed than the
testing tool, you might attempt to access an element that isn’t yet available. See how to synchronize
your test
Failure tagging
When you find the root cause of a failed test run, it’s a good idea to tag them with a failure reason
for future analysis.
Managing a test automation project involves more than writing tests and looking at pass/fail rates. You need
a more complete understanding of open tasks, trends and release readiness.
TestOps Dashboard
The dashboard is your quick look into everything your team or you need to get done. See tests by
status, recent failures, or activities. Filter by “assigned to me” to minimize the noise and focus on
your outstanding tasks.
Reports
See how your tests are performing over times. Filter by branch, suite, label, and alter the history to
fit your needs. See our enhanced reporting.
- Connecting to your CI or integrating to other tools for bug tracking or test management
- Managing project settings
- Managing users
- Branching and Merging, Pull Requests
- Adding custom code to a step