Who uses StepTrails, and for what

In plain words

Here are real-life situations where StepTrails helps. Find the one that sounds like you.

"A customer says the website is broken" (support)

The problem. The customer cannot explain exactly what they did. You cannot reproduce it.

What you do. Follow the customer's steps with StepTrails turned on. When the problem shows up, stop recording.

What you get. A report with every step, the reason it failed and a picture. A developer can press play and watch it happen. You can also create the bug ticket in one command.

"I do the same checks every morning" (tester or website owner)

The problem. You log in, check the main pages and make sure the Pay button works. It is boring, and tired people miss things.

What you do. Record the checks once. Then play them back each morning, or set them to run on a schedule.

What you get. A short report every day. You only look at it when something fails.

"A bug came in and I cannot see it" (developer)

The problem. The report says "it crashes sometimes".

What you do. Ask for a StepTrails recording instead of a description. Play it back with the browser visible.

What you get. You see the same steps the user took. You can also turn the recording into a test file that keeps the bug from coming back.

"Is my new version safe to release?" (team lead)

The problem. After every change, someone has to check that nothing important broke.

What you do. Keep a recording for each important journey: sign-up, search, checkout. Run them all before a release.

What you get. A clear pass or fail for each journey, with a report you can share. If you also use test management, you can see which requirements are covered.

"How fast and how safe is my website?" (anyone who owns a site)

The problem. The site feels slow, or you worry about security, but you do not know where to look.

What you do. Play back a normal journey. StepTrails also measures each page and looks for common security weaknesses along the way.

What you get. Pages rated Good, Needs improvement or Poor, and a list of security findings that says how serious each one is and how to fix it. See Page speed and Security checks.

"I want to learn how testing works" (students and beginners)

The problem. Writing test code is hard to start with.

What you do. Record a flow on a practice website and download the test file. Open it and read it. Every line matches a step you did.

What you get. A real example to learn from, written by the tool from your own actions.

Not sure yet?

Start with What is StepTrails?, or go straight to Your first recording.