When is a remote phone worth checking?

Use a real-device session when a screen simulation leaves a question unanswered. A booking form that fits a narrow desktop window can still be hard to scroll or finish in mobile Safari.

BrowserStack Live lets you choose a supported device and browser, then use the site yourself. Check the exact combination first. For example, choose Safari on a supported iPhone or Chrome on a supported Android phone.

Choose a phone the audience actually needs to use. A short session that finds where a customer gets stuck can tell you more than opening the home page on a long list of devices.

How do you check the booking flow in BrowserStack Live?

Use one fake appointment. Write down the device and browser, what you did and whether the appointment appeared after you reopened it.

Open a safe test copy
Use a test app with a separate database, test sign-in settings and fake accounts. Keep payments and messages off or isolated. For a private site, set up an approved Local Testing connection limited to the test environment.
Choose the device and do the task
Open the selected browser and try the booking by tapping and scrolling the form. Save a fake slot, reopen the page and check that it is still there. Try a taken slot and check that you get another choice. If you need to confirm that the booking follows the account, sign in again in a fresh session and look for it there.
Keep enough evidence to repeat it
Record the device, browser and first step that goes wrong. Capture only permitted evidence. End the session and close any test connection when you finish.

When should you run a script on BrowserStack Automate?

Use Automate when you already have a repeatable check and need it to run on a supported hosted browser or device. Keep the script in your project.

The Playwright integration has a route to supported physical iOS devices. Check the exact Playwright version, device, browser and commands your script uses. The hosted phone run can have different support from the same test on your own computer.

A device profile in a hosted desktop browser is still emulation. If a real phone is the reason you are paying for a run, confirm the selection is a physical device before interpreting the result.

How do Live and Automate charge for different work?

Live plans differ by users, browser and device coverage, and included time. Automate plans differ by coverage and how many automated tests can run at the same time.

The Live Freelancer plan lists one user and 100 minutes of desktop and mobile testing. It excludes screenshots. If you need regular device coverage or evidence for a teammate, compare the fuller Live plans before choosing.

For Automate, start by deciding how long you can wait for the test suite. A parallel is one test session running at a time. Buying more lets supported sessions run together. Confirm the plan includes the physical devices you need.

Which test records should you keep yourself?

Keep the steps and the minimum evidence your team needs to repeat a failure. Do not rely on a remote session staying in the dashboard.

A remote browser can see the pages and test data you send to it. Depending on the product, plan and settings, session evidence can include recordings, network logs or console output. Restrict access and use a disposable account. Leave customer data, production passwords and real payment details out of the test.

Keep your automated scripts in your project. Save the device and browser details with any permitted evidence outside the session history, especially if your team needs the result after the retention window ends.