Skip to content
Semaloop Docs

Skills

One of the ways we improve our speed and efficiency as we test your app over a period of time is with skills.

A trace step labelled New Skill Learned

You can think of skills as repeatable routines that our agent has confidence in repeating on future test runs. The first time we run through your test suite, we’ll be learning lots of new skills, like how to perform a search, or how to complete onboarding. In subsequent runs, assuming that your UI remains roughly the same, we’ll perform the same skill again.

However, if things have shifted around, or we hit a hiccup when running an existing skill, we fall back to our recovery mode and try to find a new way to achieve that goal. This is what makes Semaloop agents resilient to non-deterministic UIs, or apps that change frequently.

You’ll often see in the test trace one of the following labels:

  • New Skill Learned: This is the first time we’ve hit a confidence level high enough to capture this skill.
  • Existing Skill: We executed the same set of steps as we used in the previous test run.
  • Existing Skill Failed: We failed to execute the existing skill, and we also didn’t hit a confidence threshold to save this new path as a new skill.

There’s nothing you need to do with skills, other than you’ll see them pop up from time to time, and will help ensure your tests are running smoothly.